When using DirectX renderer by setting Plugin=RenderSystem_Direct3D9 in bin/release/plugins.cfg, the start screen appears! That's more than previous versions of wine reached.
What does not
Loading stops when the console shows the following message:
WARNING: the mesh 'char_assil.mesh' includes vertices with more than 4 bone assignments. The lowest weighted assignments beyond this limit have been removed, so your animation may look slightly different. To eliminate this, reduce the number of bone assignments per vertex on your mesh to 4.
That's also the point until cedega comes.
Using OpenGL as renderer, the game's internal console pops up a message:
Error #: 9
Description: Vertex Buffer: Out of memory.
You may choose to continue, but get:
wine: Unhandled page fault on read access to 0x0000006c at address 0x7f298edd (thread 0009), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: page fault on read access to 0x0000006c, invalid program stack in 32-bit code (0x7f298edd).
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Mandriva 2010.2||Dec 16 2010||1.3.9||Yes||Yes||Bronze||Maik Wagner|
|Show||openSUSE 11.0||Jul 05 2008||1.1.0||Yes||Yes||Garbage||an anonymous user|
|Show||Debian GNU/Linux 4.x "Etch" x86_64||Mar 09 2008||0.9.57.||Yes||No||Garbage||an anonymous user|
|Show||Ubuntu 7.04 "Feisty" amd64 (+ variants like Kubuntu)||Jun 16 2007||0.9.38.||Yes||No||Garbage||Jeremy Coleman|
|Show||Ubuntu 6.10 "Edgy" i386 (+ variants like Kubuntu)||May 11 2007||0.9.36.||Yes||Yes||Gold||an anonymous user|
ÂÂÂÂUse wine-0.9.31 .. 0.9.43 to play this game with the default Direct3D9 renderer because of several regressions. These old versions should work except the item icons in the inventory may not be drawn correctly (bug #21354).
The maintainer would appreciate if you would find out whether one of these old veÂrsions works better than the others.
You can use much more recent versions of Wine (such as 1.1.34/36) if you change bin/release/plugins.cfg to use the GL renderer instead. The speech output issue (bug #21209) may still affect your machine.Â