https://bugs.freedesktop.org/show_bug.cgi?id=28800 --- Comment #7 from Chris Rankin <rankincj@xxxxxxxxxxxxxx> 2010-07-12 01:15:18 PDT --- (In reply to comment #6) > There is nothing I can do about a crash in WoW and not in the driver, though I > believe WoW without S3TC has not been tested by Blizzard QA because there are > no Windows drivers that do not advertise S3TC. The WoWWiki documents WoW as *needing* S3TC textures: http://www.wowwiki.com/BLP_files The crash is almost certainly to do with WoW using one of the S3TC extensions without checking whether the driver supports it first. > I don't think there is an equivalent to force_s3tc_enable in Gallium, Then I'll raise that as a separate bug, because WoW is going to need the S3TC extensions to be advertised, and some people might not be able to use the IP-encumbered libtxc_dxtn library. > and I think the presence of libtxc_dxtn has nothing to do with the texture > corruption issue. I'm not so sure about that. The remaining texture corruption only happens in certain *locations*. It has nothing to do with NPCs appearing on screen. More interestingly, none of these locations is in "The Burning Crusade" expansion, where DXT5 compression was apparently used for the first time. (See link above.) The final interesting observation was that when I uninstalled libtxc_dxtn and tried playing WoW with r300g, the expected texture corruption was not present for those few seconds before the game crashed. This is another reason why I am interested in a force_s3tc_enable for Gallium: to see whether the corruption reappears if I can avoid the crash. (Failing that, at least to eliminate a blob of unmaintained code as the cause of the problem.) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
