You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe it's clear that swapchain images are retrieved in the D3D12_BARRIER_LAYOUT_COMMON layout, given that with legacy resources, I believe they started in the equivalently mapped D3D12_RESOURCE_STATE_COMMON, but for engineers learning DX12 starting from enhanced barriers in the future without legacy resource state experience, it may be worth mentioning swapchain images in the EB spec for completeness. Thanks!
The text was updated successfully, but these errors were encountered:
jeremyong
changed the title
Clarify swapchain image initial barrier layout
Clarify swapchain image initial EB layout
Jul 14, 2023
Thanks! The change looks good. On the subject of presentation and the swapchain, I suppose there is perhaps some implicit synchronization happening after command list execution and IDXGISwapchain::Present also? It's something I've been used to with DirectX APIs, but I'll note the lack of any explicit barrier needed prior to presentation (compare to Vulkan where there is this notion of an "external" dependency).
I believe it's clear that swapchain images are retrieved in the
D3D12_BARRIER_LAYOUT_COMMON
layout, given that with legacy resources, I believe they started in the equivalently mappedD3D12_RESOURCE_STATE_COMMON
, but for engineers learning DX12 starting from enhanced barriers in the future without legacy resource state experience, it may be worth mentioning swapchain images in the EB spec for completeness. Thanks!The text was updated successfully, but these errors were encountered: