rooty/dxvk
1
0
Fork 0
mirror of https://github.com/doitsujin/dxvk.git synced 2025-02-23 10:54:14 +01:00
Code Issues Projects Releases Wiki Activity

[dxvk] Don't use secondary command buffers for certain render passes

Browse Source 
If we can't use any store/resolve op optimizations on a render pass, there
is no reason to pay for the overhead of secondary command buffers.
This commit is contained in:
Philip Rebohle 2025-02-10 21:34:34 +01:00
parent beaf6dd2a6
commit 94b5cfc3d8
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
src/dxvk/dxvk_context.cpp
View File

@ -5250,7 +5250,15 @@ namespace dxvk {
renderingInheritance.stencilAttachmentFormat = depthStencilFormat;
}
if (m_device->perfHints().preferRenderPassOps) {
// On drivers that don't natively support secondary command buffers, only
// use them to enable MSAA resolve attachments. Also ignore color-only
// render passes here since we almost certainly need the output anyway.
bool useSecondaryCmdBuffer = m_device->perfHints().preferRenderPassOps;
if (useSecondaryCmdBuffer && (m_device->perfHints().preferPrimaryCmdBufs || !depthStencilAspects))
useSecondaryCmdBuffer = renderingInheritance.rasterizationSamples > VK_SAMPLE_COUNT_1_BIT;
if (useSecondaryCmdBuffer) {
// Begin secondary command buffer on tiling GPUs so that subsequent
// resolve, discard and clear commands can modify render pass ops.
m_flags.set(DxvkContextFlag::GpRenderPassSecondaryCmd);