Everything works fine, except catacombs models. With classic models, the game runs great (better than Windows, in my experience). Before running the game, you should run 'winecfg' and disable vertex and pixel shaders in the Graphics tab. This will cause the game to run using classic models. Without doing this, your game client will crash once it reaches the character selection screen.
Note that it may be possible to enable Catacombs models with either:
What does not
Catacombs models (see above)
What was not tested
Nothing that I know of.
- You can skip the patcher (assuming your client is the newest version) by directly running login.dll ("wine login.dll") - You can run as many DAoC clients as you wish by using a different WINEPREFIX for each. E.g., ("WINEPREFIX=~/.wine wine login.dll" and then "WINEPREFIX=~/.wine2 wine login.dll", etc.). Note that this may be against the EULA since Mythic limits the number of active game clients to two on Windows.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Linux Mint 17 "Qiana" x86_64||Aug 26 2014||1.7.24||Yes||Yes||Garbage||an anonymous user|
|Show||Linux Mint 14 "Nadia" x86_64||Feb 18 2013||1.4.1||Yes||Yes||Bronze||an anonymous user|
|Show||openSUSE 12.1 x86_64||Feb 19 2012||1.4-rc4||Yes||Yes||Bronze||Feldspar|
|Show||Mac OS X 10.6 "Snow Leopard"||Feb 05 2011||1.3.12||No, but has workaround||Yes||Silver||MikaN|
|Current||Ubuntu 10.04 "Lucid" amd64 (+ variants like Kubuntu)||Oct 23 2010||1.3.5||Yes||Yes||Gold||an anonymous user|
|Bug #||Description||Status||Resolution||Other apps affected|
|3548||.lnk file is created on the desktop together with the program icon...||NEW||View|
|39057||Support for Indexed Vertex Blending||STAGED||View|
|40646||Game Launcher fails with "Error occurred during a cryptographic operation".||UNCONFIRMED||View|
|40801||DAoC: Software vertex blending crash||UNCONFIRMED||View|
Using FBO as the ORM crashes with fglrx drivers
This is not a Wine bug, it is a fglrx bug. Please do not open a bug for this, it will just be closed.
See the fglrx bug for more details, or check the HOWTO for this app for a workaround.