Immediate and Deferred Rendering

Direct3D 11 supports two types of rendering: immediate and deferred. Both are implemented by using the ID3D11DeviceContext interface.

Immediate Rendering

Immediate rendering refers to calling rendering APIs or commands from a device, which queues the commands in a buffer for execution on the GPU. Use an immediate context to render, set pipeline state, and play back a command list.

Create an immediate context using D3D11CreateDevice or D3D11CreateDeviceAndSwapChain.

Deferred Rendering

Deferred rendering records graphics commands in a command buffer so that they can be played back at some other time. Use a deferred context to record commands (rendering as well as state setting) to a command list. Deferred rendering is a new concept in Direct3D 11; deferred rendering is designed to support rendering on one thread while recording commands for rendering on additional threads. This parallel, multithread strategy allows you to break up complex scenes into concurrent tasks. For more information about rendering complex scenes, see Multiple-Pass Rendering.

Create a deferred context using ID3D11Device::CreateDeferredContext.

Direct3D generates rendering overhead when it queues up commands in the command buffer. In contrast, a command list executes much more efficiently during playback. To use a command list, record rendering commands with a deferred context and play them back using an immediate context.

You can generate only a single command list in a single-threaded fashion. However, you can create and use multiple deferred contexts simultaneously, each in a separate thread. Then, you can use those multiple deferred contexts to simultaneously create multiple command lists.

You cannot play back two or more command lists simultaneously on the immediate context.

To determine if a device context is an immediate or a deferred context, call ID3D11DeviceContext::GetType.

The ID3D11DeviceContext::Map method is only supported in a deferred context for dynamic resources (D3D11_USAGE_DYNAMIC) where the first call within the command list is D3D11_MAP_WRITE_DISCARD. D3D11_MAP_WRITE_NO_OVERWRITE is supported on subsequent calls if available for the given type of resource.

Queries in a deferred context are limited to data generation and predicated drawing. You cannot call ID3D11DeviceContext::GetData on a deferred context to get data about a query; you can only call GetData on the immediate context to get data about a query. You can set a rendering predicate (a type of query) by calling D3D11DeviceContext::SetPredication to use query results on the GPU. You can generate query data through calls to ID3D11DeviceContext::Begin and ID3D11DeviceContext::End. However, the query data will not be available until you call ID3D11DeviceContext::ExecuteCommandList on the immediate context to submit the deferred context command list. The query data is then processed by the GPU.

Related topics

Multithreading

 

 

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.