http://bugs.winehq.org/show_bug.cgi?id=9717
--- Comment #27 from Norbert Lataille nonal@freesurf.fr 2007-12-14 12:08:09 ---
This workaround is great and soleved the main issue particularly in Gothic3 and Crysis.
This is interesting news... these 2 graphic corruption may have the same underlying bug.
The speed is acceptable @ high details. On low it is also good. But the problem isn't fixed completely. I'll attach a screen shot later.
Yes, I was expecting it. This is clearly not a fix for the cause, just a hack to help making the game playable while the bug is being investigated.
On the perf front, I found 1/2 things in the oprofile report I would like to test in order to improve rendering performance. But it does not seem this game is providing a native FPS counter, it will be hard to test.
It seems that most of my slowdowns are due to hard drive loading phases. I am wondering why this game needs to load that many entities while I am just spinning on myself. Worth a look...
In Gothic3 there are more issues to get this running. There seems to be a memory issue (when Gothic3 takes about 1.4GB of memory in high details - after playing time < 5 min): err:d3d:CreateIndexBufferVBO Failed to initialize the index buffer with error GL_OUT_OF_MEMORY (0x505)
May be easy to look at (is this related to a memory leak ? I noticed that Heap management routines are called A LOT !!!) On my side I always end up with an exception.