<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290" href="https://bugs.freedesktop.org/show_bug.cgi?id=64508#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Text rendered using QuesoGLC is unreadable/missing on Radeon HD 6290" href="https://bugs.freedesktop.org/show_bug.cgi?id=64508">bug 64508</a> from <a class="email" href="mailto:ptpzz@yandex.ru" title="Vadim Girlin <ptpzz@yandex.ru>"> Vadim Girlin</a> <pre>Created <a href="attachment.cgi?id=79220" name="attach_79220" title="qapitrace screenshot">attachment 79220</a> <a href="attachment.cgi?id=79220&action=edit" title="qapitrace screenshot">[details]</a> qapitrace screenshot As far as I can see it's a bug in the QuesoGLC. I'm attaching the screenshot of qapitrace with gl trace for the test9.2 and the event filter "glBind|glTexIma|glTexSub|glNew|glEndList|glCall|glGen" applied to show relevant calls. Mesa reports the errors on the glTexSubImage2D calls because the texture is not initialized yet (e.g. using glTexImage2D). Note that the test compiles the display list first and uses glTexImage2D to initialize the texture, but compiled display list is never called, instead the app basically repeats the same sequence of calls without calling glTexImage2D first. As far as I understand, mesa reports the errors correctly, and it's in fact the bug in QuesoGLC. By the way, there is another bug related to the issues with warzone 2100: <a href="http://sourceforge.net/tracker/index.php?func=detail&aid=1830052&group_id=53918&atid=472059">http://sourceforge.net/tracker/index.php?func=detail&aid=1830052&group_id=53918&atid=472059</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>