For more details and user comments, view the versions of this application
|Version||Description||Latest Rating||Latest Wine version tested||Test results||Comments|
|Current||The Latest update of Dungeons and Dragons Online.||Platinum||5.4||18||92|
Download http://content.turbine.com/sites/clientdl/ddo/ddolive.exe and run it in a clean wineprefix. Let the installer do its thing and start the launcher.
Once the Launcher starts, The Akamai Netsession license agreement will pop up, and then it might minimize itself. Just bring it back up, scroll to the bottom and accept it. The rest is just waiting for DDO to install itself. The launcher might crash a time or 2 (it didn't for me). If it does, just restart it.
Enjoy the game. :)
At this point you should be able to sign in and play the game. But its normal for some issues to arise. Here are some tweaks/fixes you can try.
First things first: Make sure you have 32-bit dependencies installed.
To run the game, you need a number of 32-bit Libraries installed. Mesa and Samba are definitely required, and OpenAL may also be required depending on your setup. Additionally, for the in-game store to work, you need GnuTLS. Other libraries may also be needed/wanted. If in doubt, check wine's dependencies and install 32-bit versions of as many as you can, including "optional" dependencies.
This is the #1 problem I've run into when helping people get DDO working on Linux, so don't skip it!
Once you've checked your dependencies: Try running the game in a clean WINEPREFIX
If you have an old install of DDO that's been around for a major wine version or 2, you've probably got some cruft in your old WINEPREFIX that's slowing you down. You can fix this by either reinstalling DDO in a new, clean WINEPREFIX or by copying your game directory out of your current WINEPREFIX (it'll probably be at "$WINEPREFIX/drive_c/Program Files/Turbine/Dungeons and Dragons Online"), after which you can delete your old WINEPREFIX, and run TurbineLauncher.exe in a new, clean one.
If, after trying the above, you're still having problems, here are some older tips that may help:
The launcher hangs when attempting to download loading screens:
First things first, simply doing a wineserver -k and re-running the launcher often gets the launcher past this. If this is happening to you, however, it's likely to keep happening, so keep reading.
As a more permanent fix, you could try running DNDLauncher.exe with the -skiprawdownload option, which should cause the launcher to skip this step entirely. You'll want to download the splash screens at least once, tho, or make/download some custom ones, if you do this.
Another alternative is to use an alternate launcher. 2 of these exist:
"AwsomiumProcess has encountered…"
This error is common among the Wine games. Seems to pertain to the fonts somehow. In many cases the error can be closed & ignored. The game continues to work fine. But once you start getting the error, you will get it every time you run the game. The fix is to run:
$ winetricks corefonts tahoma
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
This problem (if it occurs) seems to kick in when you try to switch to windowed mode or change video resolutions. It usually has to do with Pulseaudio. Make sure that if you have Pulseaudio installed that you also installed its alsa-compatibility package (pulseaudio-alsa on Arch, USE="alsa" for Pulseaudio on gentoo/funtoo, or check your distro's package manager for it). Once that's done, make sure wine's using its alsa driver. Failing that, see if your wine has a PulseAudio driver and use that instead.
Set the correct video memory size in the Registry.
Wine doesn't usually input your video memory size correctly. To take advantage of your video memory you can set the amount yourself with winetricks.
1gb = 1024 (change to your video memory size in MiB).
Note: winetricks only supports specific video memory sizes (512, 1024, and 2048). If your card has a memory size that isn't supported by your version of winetricks, you can set it manually. See http://wiki.winehq.org/UsefulRegistryKeys for how to do this.
$ winetricks videomemorysize=1024
Set Direct Draw Renderer to OpenGL
Setting this option can improve the game performance. Or at least it seems to work in my case.
$ winetricks ddr=opengl
(note: this should be the default, but just to be sure...)
Set OffscreenRenderingMode to pbuffer
Open regedit with:
$ wine regedit
Fine the key: HKEY_CURRENT_USER\Software\Wine\Direct3D
And a new string value named "OffscreenRenderingMode" and set it to "pbuffer"
Install PhysX (Nvidia only)
Nvidia users can improve the performance of game physics by installing PhysX from Nvidia. Winetricks can handle this.
$ winetricks physx
Note: This requires the nVidia OpenCL drivers to be installed, including the 32-bit ones for your system. If they're not installed, DDO will crash with PhysX installed, so be sure to have them installed.
And the best fix of all
Run the game in a clean WINEPREFIX. I can't stress that enough. You shouldn't need any winetricks, fonts, etc to be installed, the game just works. If you followed any old instructions (mine included) just copy your game directory out of your current WINEPREFIX (it'll probably be at "$WINEPREFIX/drive_c/Program Files/Turbine/Dungeons and Dragons Online"), delete your old WINEPREFIX, and run TurbineLauncher.exe or DDOLauncher.exe (whichever you have) in a new, clean one.
Tweaking the game:
Setting the video memory size usually fixes most performance issues. However there is a list of things you can do to try to kick the performance up an extra notch. Of course these are just suggestions. They are all optional.
Disable desktop 3D effects (In Unity switch to 2D session)
The 3D desktop features can cause some performance issues in the game. Logging out and changing your Unity session, or disabling 3D desktop effects can greatly increase game performance.
Choose a "Graphics Quality" in Options->Graphics
It's common for the auto detection to misdetect the card since there is a wine api in the middle of everything. Select this manually to get the quality you want. (I chose "very high" for my 1gb Nvidia card)
Increase "Texture Cache Size" in Options->Adv. Graphics
You can increase this to improve the game performance by increasing the amount of system memory used for graphics resources. This can decrease load times and in turn increase game performance.
Enable "Triple Buffering" in Options->Adv. Graphics
For video cards with extra memory you can use this setting to slightly increase rendering performance.
Disable "Player Mesh Combining" in Options->Adv. Graphics
This feature not only uses up more system memory, but also video memory. Saving a little video memory can always help game performance.
Disable "Distant Imposters" in Options->Adv. Graphics
This option simply allows trees and other objects to render over distant scenery. Can be disabled to increase game performance.
If you use the Turbine Launcher, and don't have the game installed on an SSD, enable preloading of game files (or client_gamelogic.dat?) in the launcher's options.
This preloads the client_gamelogic.dat file into memory, drastically decreasing initial login/load time, at the cost of needing about 300M of extra memory when launching the game (this is a fix/workaround for the first-login red-latency-disconnect bug).
If the Turbine Launcher hangs on startup...
If you're getting this, make sure you're using a current version of wine and that you're using a clean wineprefix. If it still happens, run wineserver -k and re-run the launcher. If it keeps happening, you can fix it permanently by using the following command to start the game:
Note that that's DNDLauncher, not TurbineClientLauncher. As far as I can tell, TurbineClientLauncher is now just a secondary loader for DNDLauncher (so that players with ancient installs don't have to update their shortcuts) and doesn't pass (all) arguments to DNDLauncher properly. Also, unless you want the "grey grid" loading screens you may have seen with PyLotRO years ago, you should probably run the launcher at least once to get to the login prompt without -skiprawdownload to get loading screens.