<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - ARB_shading_language_include is not implemented" href="https://bugs.freedesktop.org/show_bug.cgi?id=95215#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - ARB_shading_language_include is not implemented" href="https://bugs.freedesktop.org/show_bug.cgi?id=95215">bug 95215</a> from <a class="email" href="mailto:jamey@minilop.net" title="Jamey Sharp <jamey@minilop.net>"> Jamey Sharp</a> <pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=95215#c3">comment #3</a>) > (In reply to Jamey Sharp from <a href="show_bug.cgi?id=95215#c2">comment #2</a>) > > (In reply to Ilia Mirkin from <a href="show_bug.cgi?id=95215#c1">comment #1</a>) > > > Sounds like the game is buggy and needs fixing - I presume it runs fine on > > > Catalyst drivers, which also don't support the ext. > > > > Hmm. Is apitrace mis-leading us here? > > More likely the game is buggy. Note that glXGetProcAddress("bla") != null. > See <a href="https://dri.freedesktop.org/wiki/glXGetProcAddressNeverReturnsNULL/">https://dri.freedesktop.org/wiki/glXGetProcAddressNeverReturnsNULL/</a> OK, but __glewNamedStringARB *is* null when run on Mesa, so I guess GLEW's semantics are different from glXGetProcAddress. Sure, there is a game bug here: GLEW's documentation says that the game should check if GLEW_ARB_shading_language_include is true, and doesn't say you can check for a non-null function pointer instead. That doesn't change the fact that tracing apparently changes the game's behavior, which is obnoxious and leads to mis-diagnosed bug reports. Unless you're saying that tracing is actually not changing the game's behavior?</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>