<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [radv] DOOM 2016 + wine. Green screen everywhere (but can be started)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99467#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [radv] DOOM 2016 + wine. Green screen everywhere (but can be started)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99467">bug 99467</a> from <a class="email" href="mailto:funfunctor@folklore1984.net" title="Edward O'Callaghan <funfunctor@folklore1984.net>"> Edward O'Callaghan</a> <pre>(In reply to Grazvydas Ignotas from <a href="show_bug.cgi?id=99467#c2">comment #2</a>) > Supposedly it's because the game is doing something illegal: > <a href="https://lists.freedesktop.org/archives/mesa-dev/2016-December/138955.html">https://lists.freedesktop.org/archives/mesa-dev/2016-December/138955.html</a> > > However because all the binary drivers handle it, and Doom (which I'd call > Vulkan "killer app") relies on it, I'd say it's in the "de facto" Vulkan > standard now and it'd be better if mesa handled it. I suspect others will > disagree though... Handling broken behavior is exactly how the vendor GL drivers got into a mess so do you want that to happen to Vulkan also? Why not try to contact the game vendor with a detailed report how they can patch their shader code.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>