Initial support for D3D11 #1267
Conversation
|
Author dgraves not on autobuild list. Waiting for curator authorization before starting CI build. |
|
When adding D3D11 support to gfxrecon-info, the multiple passes that had been performed for gathering info were merged into a single pass, which may address an item described in the recently created #1256. The gfxrecon-info output was slightly modified to move the swapchain info from a position in the middle of the D3D12 info to a position just after the D3D12 info, with the label renamed from "D3D12 swapchain info" to "DXGI swapchain info". For a file containing both D3D11 and D3D12 data, this would result in the D3D11 info being printed, followed by the D3D12 info, and then the DXGI info. If this change to the output is an issue, the swapchain info can be moved back to its original position with its original label and can then be duplicated with the D3D11 info. |
|
Author dgraves not on autobuild list. Waiting for curator authorization before starting CI build. |
|
CI gfxreconstruct build queued with queue ID 167769. |
|
CI gfxreconstruct build # 4005 running. |
|
CI gfxreconstruct build # 4005 failed. |
|
@dgraves |
Adds initial support for the Direct3D11 API. Capture and replay are stable, but trimming is not currently supported.
The existing D3D code generators were updated to generate D3D11 code along with the existing D3D12 and DXGI related code, which results in most of the D3D11 code being appended to the same files containing the D3D12 and DXGI code. I thought it would be better to let the project developers determine how to best reorganize and rename the existing files, rather than attempt to do it as part of this submission.