<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - vkQuake flickering geometry under Intel" href="https://bugs.freedesktop.org/show_bug.cgi?id=109630#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - vkQuake flickering geometry under Intel" href="https://bugs.freedesktop.org/show_bug.cgi?id=109630">bug 109630</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>A few more notes: 1. Flagging dirty push constants on every draw makes the flicker go away. 2. VkQuake uses actual Vulkan push constants which is a bit weird. Witcher 3 via DXVK probably doesn't though so if they're related, it may not be push constants. 3. Denis said it may have something to do with compute (if you disable compute dispatch in the driver, the flickering goes away). This made me wonder if it had something to do with switching between 3D and compute. Flushing push constants after PIPELINE_SELECT does nothing. :-( 4. Disabling UBO pushing by commenting out brw_nir_analyze_ubo_ranges() in anv_pipeline.c does nothing. 5. Flagging dirty descriptors also makes the flicker go away. Dirty push constants always cause dirty descriptors but not the other way around so maybe it's actually something with binding tables? I'm not really sure where to go next with this one. It could also, I guess, be blorp related possibly though blorp usually causes pretty complete state flushing.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>