Multiplane overlay resource creation
When multiplane overlays are used, these requirements apply to allocations that are created within Microsoft DirectX apps.
DirectX 11 resource creation
When the CreateResource(D3D11) function is called:
- The D3D10_DDI_BIND_PRESENT and D3D10_DDI_RESOURCE_MISC_SHARED constant values are set in the BindFlags member of the D3D11DDIARG_CREATERESOURCE structure, indicating that the allocation can be scanned out.
- It's possible that other bit-field flags in Flags will also be set, such as:
- D3D10_DDI_BIND_SHADER_RESOURCE
- D3D10_DDI_BIND_RENDER_TARGET
- D3D11_DDI_BIND_UNORDERED_ACCESS
- D3D11_DDI_BIND_DECODER
- D3D11_1DDI_RESOURCE_MISC_RESTRICTED_CONTENT
- D3D11_1DDI_RESOURCE_MISC_RESTRICT_SHARED_RESOURCE_DRIVER
- When the DXGI_DDI_PRIMARY_DESC structure is passed in the CreateResource(D3D11) call:
- DXGI_DDI_PRIMARY_DESC has an appropriate value for the VidPnSourceId member.
- DXGI_DDI_PRIMARY_DESC.ModeDesc matches the current mode.
- For multiplane overlay resources, the driver must not set the DXGI_DDI_PRIMARY_DRIVER_FLAG_NO_SCANOUT flag value in the DriverFlags member of DXGI_DDI_PRIMARY_DESC.
DirectX 9 resource creation
When the CreateResource2 function is called:
- The Primary and SharedResource bit-field flags in the Flags member of the D3DDDIARG_CREATERESOURCE2 structure are set.
- It's possible that other bit-field flags in Flags will also be set, such as:
- RenderTarget
- Texture
- DecodeRenderTarget
- RestrictedContent
- RestrictSharedAccess
- The VidPnSourceId member of the D3DDDIARG_CREATERESOURCE2 structure is properly initialized.
- The RefreshRate member of the D3DDDIARG_CREATERESOURCE2 structure contains zero.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for