<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - (radeonsi) Some lighting issues in games, textures goes black" href="https://bugs.freedesktop.org/show_bug.cgi?id=77785#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - (radeonsi) Some lighting issues in games, textures goes black" href="https://bugs.freedesktop.org/show_bug.cgi?id=77785">bug 77785</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to <a href="show_bug.cgi?id=77785#c14">comment #14</a>) > It is XRGB, MESA_FORMAT_B8G8R8X8_UNORM but need to checked it out in real > situations... a think intel disable support for this "memory saver" format > in screen, but radeon in classic and gallium leave it enabled :). MESA_FORMAT_B8G8R8X8_UNORM has nothing to do with memory saving (it's the same as MESA_FORMAT_B8G8R8A8_UNORM as far as memory layout is concerned), it just means that the contents of the 'alpha' channel in memory are ignored. > Does that format need to be supported anymore? Yes. We need to find out where and how this format ends up being used incorrectly. Note that this might be in Wine / in the apps themselves. Anyway, your comments #17 and #18 mean that the PTTM/ATH and AirStrike3D issues are probably not one and the same bug and need to be tracked separately. The AirStrike3D and SuperTuxKart issues might be related, but it's better to assume they're separate as well for now, to avoid cluttering up a single report with unrelated issues.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>