http://bugs.winehq.org/show_bug.cgi?id=6505
------- Additional Comments From the3dfxdude@gmail.com 2006-02-11 10:59 ------- Alexander, you really need to approach this bug differently. You should see this as a support request for you. You aren't helping anyone else by doing what you are doing. Alan is now asking for more information, and it all is pretty elementary because he doesn't understand mostly anything about it. Just like in my emails to you, and my original response, you need to fix the summary of this report and provide better information. You still have not indicated at all whether this is only a d3d problem. I asked you to do this three times now. Don't blow *us* off. I still don't know if this is only *one* problem described here either.
The purpose of the WINEDEBUG=+d3d is to gather more information. No you don't have to spend time to decipher it. I'm not saying you are supposed to learn how to hack wine either. If you are able to get a log, just post it like I asked. I still take it you haven't read the guide of the link I posted. It talks about debug channels and controlling debug output. Yes, it will slow down the game, and you'll have to suffer through it and learn how to control it enough to gather some information. Considering the nature of the bug, it will be difficult to gather information, but we depend on you to provide enough because you are the reporter. This bug will continue to remain how it is until you start responding to requests.