<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly" href="https://bugs.freedesktop.org/show_bug.cgi?id=101739#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - An issue with alpha-to-coverage handling is causing Arma 3 64-bit Linux port to render trees incorrectly" href="https://bugs.freedesktop.org/show_bug.cgi?id=101739">bug 101739</a> from <a class="email" href="mailto:krystian.galaj@vpltd.com" title="Krystian Gałaj <krystian.galaj@vpltd.com>"> Krystian Gałaj</a> <pre>(In reply to Gregor Münch from <a href="show_bug.cgi?id=101739#c10">comment #10</a>) > Some comments from a VP dev: > <a href="https://www.gamingonlinux.com/articles/the-linux-beta-of-arma-3-has-been">https://www.gamingonlinux.com/articles/the-linux-beta-of-arma-3-has-been</a>- > updated-to-180-compatible-with-windows-again-for-a-time.11349/ > comment_id=118838 > > Seems to be that it's not clear if the bug is on Mesa or VPs side. Maybe > some Mesa dev could comment. I am not sure what we could do on VP side to work around the bug. It happens in a single execution of fragment shader on a multisampled color buffer and depth buffer. The same execution is writing a color value, and it's supposed to write a depth value into the corresponding sample of depth buffer. I don't know of any additional keywords in GLSL that we could specify to make sure this is the case. If anyone knows about something we're specifying wrong, please advise. As for rendering techniques used, we are only converting the rendering technique used by the original Arma 3 developer team from Direct3D API to OpenGL. So one way of working around the problem would be to ask them to do LOD switching in another way in future release - and then we could port that new version. But since it's not happening on the same graphics cards on Windows or Mac, only on Linux, it isn't likely this rework would be given any high priority. And we are good at API knowledge and conversion between them, but inventing another technique to swap in for existing technique in not our game requires slightly different approach, and, above all, good knowledge of the entire complicated rendering engine used in the game, so as not to break anything. I don't think that working around the problem is a good thing to mention in a bug ticket... this thing might be happening in other games, maybe not so high profile, so it would make sense to fix it in driver. It can be done, if it's working on the same cards using Windows drivers...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>