Creates a deferred context, which can record command lists.
HRESULT CreateDeferredContext1( UINT ContextFlags, [out, optional] ID3D11DeviceContext1 **ppDeferredContext );
Reserved for future use. Pass 0.
- ppDeferredContext [out, optional]
Upon completion of the method, the passed pointer to an ID3D11DeviceContext1 interface pointer is initialized.
Returns S_OK if successful; otherwise, returns one of the following:
- Returns DXGI_ERROR_DEVICE_REMOVED if the graphics adapter has been physically removed from the computer or a driver upgrade for the graphics adapter has occurred. If this error occurs, you should destroy and re-create the device.
- Returns DXGI_ERROR_INVALID_CALL if the CreateDeferredContext1 method cannot be called from the current context. For example, if the device was created with the D3D11_CREATE_DEVICE_SINGLETHREADED value, CreateDeferredContext1 returns DXGI_ERROR_INVALID_CALL.
- Returns E_INVALIDARG if the ContextFlags parameter is invalid.
- Returns E_OUTOFMEMORY if the application has exhausted available memory.
A deferred context is a thread-safe context that you can use to record graphics commands on a thread other than the main rendering thread. By using a deferred context, you can record graphics commands into a command list that is encapsulated by the ID3D11CommandList interface. After you record all scene items, you can then submit them to the main render thread for final rendering. In this manner, you can perform rendering tasks concurrently across multiple threads and potentially improve performance in multi-core CPU scenarios.
You can create multiple deferred contexts.
For more information about deferred contexts, see Immediate and Deferred Rendering.
Windows Phone 8: This API is supported.
Minimum supported client
|Windows 8 and Platform Update for Windows 7 [desktop apps | Windows Store apps]|
Minimum supported server
|Windows Server 2012 and Platform Update for Windows Server 2008 R2 [desktop apps | Windows Store apps]|