http://bugs.winehq.org/show_bug.cgi?id=10833
Stefan Dösinger stefandoesinger@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefandoesinger@gmx.at
--- Comment #3 from Stefan Dösinger stefandoesinger@gmx.at 2008-01-08 17:48:55 --- Driver bugs can surface with all strange changes. I once had a driver bug show up with changes in code that was never executed(-> uninitialized variable in the driver). You don't have to change a driver to trigger a driver bug.
If you're running the game in OpenGL mode, the chance of a Wine bug is rather rare, except if the game doesn't initialize GL at all. Beyond initialization, we're just 1:1 forwarding the calls. There isn't much to do wrong there, and even less we can do to work around driver bugs.
You say you're using the Intel driver, which is part of Mesa. In this driver I have seen many memory corruptions and other problems.