http://bugs.winehq.org/show_bug.cgi?id=8236
Stefan Dösinger stefandoesinger@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefandoesinger@gmx.at
--- Comment #2 from Stefan Dösinger stefandoesinger@gmx.at 2007-12-31 07:26:25 --- I don't think that this is a d3d bug. Apparently the game already sends incorrect draw calls to d3d, and the problem occurs in the game logic(the incorrect attack speed and attacking dead enemies suggest that).
Direct3D and DirectDraw don't do animations. They only think in "draw a triangle here" or "clear this part of the screen" actions. Animations have to be maintained by the applications or other libraries(e.g. quartz).
That doesn't necessarily mean that the bug is not in d3d. A bad return value from a d3d call, or capability flags that confuse the game might break the game logic. I think this is unlikely though. The best way to tell is to compile the d3d libs for Windows and run the game on Windows with Wine's D3D libs. If the bug occurs in that setup, it is a d3d bug. If it doesn't, it is a bug in some other part of Wine.
-
wine-bugs＠winehq.org