<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Vulkan overlay layer - async compute not supported, making overlay disappear in Doom" href="https://bugs.freedesktop.org/show_bug.cgi?id=111401#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Vulkan overlay layer - async compute not supported, making overlay disappear in Doom" href="https://bugs.freedesktop.org/show_bug.cgi?id=111401">bug 111401</a> from <a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> Lionel Landwerlin</a> <pre>(In reply to tempel.julian from <a href="show_bug.cgi?id=111401#c3">comment #3</a>) > I think I should have mentioned that I use the Mesa ACO fork. As far as I know the ACO work is mostly compiler related, so it shouldn't affect the overlay. I honestly don't know what's going wrong there. We properly insert a dependency to ensure the image isn't shown until the overlay is finished drawing. >From the driver's point of view the overlay should be just like any other application drawing. Unless if there is an issue in the application that concurrently draws with the overlay, overriding it. Have you tried to position the overlay in different corners of the window to see if it has any effect? Does it disappear for good or is it showing once every other frame?</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>