Bug reports about Graphics
by Tigerclaw | 10/02/2008 18:34:21![]() If you see any kind of distorted or incorrect rendering, please write a good bug report here. A good bug report contains these details: a) which OS environment (Windows XP, Windows Vista, MacOS X (10.x.x) ) b) what hardware you are running on (machine model, especially GPU model) (also any details about what revision of GPU drivers you have installed) c) conditions under which it happens d) if it persists after manually disabling "M2UseShaders" in config.wtf SET M2UseShaders "0" d) if it persists after manually disabling "pixelshaders" in config.wtf SET pixelshaders "0" e) if running on Windows, if you are running the game in DirectX or OpenGL mode. Including all of this information in your opening post can save a lot of time on our end. [ Post edited by Tigerclaw ] |
by Cprompt | 15/02/2008 21:55:59![]() For those of you who are seeing the streaking polygons, can you try setting M2BatchParticles to 0 (either from the console or in config.wtf). Make sure to set M2UseShaders back to 1 if you set it to 0 to fix this issue. See if that doesn't address the issue for you. Please post here if it works. |
by Cprompt | 15/02/2008 22:49:19![]()
d) If the line isn't already in the file, you can simply add it, exactly like what you have there in quotes. |
by Cprompt | 15/02/2008 23:41:58![]()
Can you confirm that M2BatchParticles was the cause of the fishing line problems? Setting M2BatchParticles to 1 from the console will set it back to the default value. If the fishing line draw error persists, then the two issues are unrelated. |
by Cprompt | 15/02/2008 23:54:20![]()
Sounds like a bug to be sure, but sounds like it is unrelated to M2BatchParticles. Thanks for confirming it. |
by Cprompt | 16/02/2008 00:07:30![]()
We found the fishing line problem. It will be fixed in the next rev on the PTR. |
by Tigerclaw | 16/02/2008 03:59:40![]() Thanks for all of the detailed reports. We have already fixed a few of these issues for the next PTR update, some of them are still in mid-debugging. Hopefully we can have all of these resolved in the next week or so. |
by Tigerclaw | 23/02/2008 00:57:38![]() Just a note on the various performance and graphics bugs on the Mac client - we're fully aware of the issue and are working steadily on fixes, however some of the issues are deep rooted in some new tech being used for this release. As many have found, disabling the use of vertex shaders by adding this text to config.wtf may allow you to dodge the known issues in the current PTR builds on the Mac: SET M2UseShaders "0" Thanks for all of the reports and we hope to get an updated build out in coming days with some significant improvements. |
by Hortus | 26/02/2008 20:07:23![]()
Could you please provide more information about your system? A DXDiag (for Windows) report would be best: Important Note: Please reboot your system prior to creating the dxdiag and files.
|
by Hortus | 27/02/2008 01:14:15![]()
At the very minimum I'll need the video card information. |
by Tigerclaw | 27/02/2008 23:15:31![]() There has been a lot of progress in resolving this type of issue in our internal builds. The most recent changes did not make it in time for the latest public PTR revision, but should be in hand for the rev after that. |
by Tigerclaw | 28/02/2008 00:18:43![]() Those bugs have been reproduced here and (as far as we can see so far) fixed. |
by Tigerclaw | 06/03/2008 01:57:13![]()
The issue in the screenshots there may be resolved in the next build. After the next build is made available we should probably start a new thread to focus only on issues that remain in the later builds. Oh, and please post HW/ OS specs always. |
by Tigerclaw | 12/03/2008 22:56:00![]() Locking this thread and starting a new one for later builds. |
Hot: Grab one of our RSS feeds to stay updated with what's happening with your class!




Recent Blizzard Announcements

