"Playing the game on Linux, although not officially supported, will not get you banned – cheating will." -- Bashiok
Important info for test results posters
Thank you very much for wishing to spend some time on improving AppDB.
I have to warn you that general AppDB policies forbid (a) accepting test results for patched Wine versions and (b) forbid accepting results obtained from PoL-driven Wine installations, only "vanilla" unpatched Wine or Wine that had came by default with your distro are considered to be valid. I'm really sorry for that, but it is the way it currently is.
For more details feel free to read recent (as of 16th of May, 2012) discussion on wine-devel mailing list.
Aside from the requirements above your test results should comply with some simple rules to be accepted:
Please, test an application under fresh clean wineprefix;
Include exact specs of the computer you had tested an app on (CPU, GPU, amount of RAM and VRAM) in the "Extra Comments" section of the report;
Specify versions of essential software components, most notably: is your system 32bit or 64bit, what is the version of the GPU display driver you use and what is the version of the OS kernel;
Include detailed information on the native dll overrides you had to use in order to get the game working. If you had installed dlls yourself - include complete information on the sources of dlls and the exact steps you took to install them.
Thank you in advance!
HOWTO: Run Diablo III on a 64-bit machine
On systems with more than 4 GB of memory Diablo III sees an unusual amount of memory (from its perspective) due to differences in the memory layout on Windows and Linux. As a result of this, many aspects of the application will fail to function properly (including the Auction House, chatting, authenticate, and closing the game). To resolve this problem you need to run the game in particular way to tell Linux to use a Windows-like memory address space:
after that the volume was really low and it appears that pulse volumes bars per application. so just clicking on the sound Icon, tools icon and going to Applications tab allowed me to adjust the volume of the game.
tested on Alllen and Heath Zed 10FX USB sound card.
thanks to this wonderful community we've got the game working great! :)
keep up the good work!
Information and bugs
Linux gentoo amd64, with nvidia-drivers official - NVIDIA Corporation GF119 [GeForce GT 520] - 800x600 resolution
Linux gentoo amd64, with nvidia-drivers official - NVIDIA Corporation GK104 [GeForce GTX 680] (rev a1) - 1280x800
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Black/White screen Battle.net launcher
by Artem on Monday March 23rd 2015, 14:27
I have tried every possible existing solution from every forum for last week.
The easiest way for me was:
1. Install Diablo 3 in virtualbox/vmware virtual machine
2. Copy Diablo III folder to your .wine/drive_c
3. Run Diablo without 'Launcher' (-launch option for Diablo III.exe)
by Guy Fleming on Monday August 25th 2014, 20:06
I am currently cleaning up the Diablo 3 game site. So if you see a verison removed that shouldn't be removed, simply re add the results, please provide if your using override dlls, archset, and OS. I do not care what version of wine you use. Email me as well when re adding.
setarch i386 -3 no longer required?
by William on Thursday February 27th 2014, 0:24
I just ran D3 for about 35-40 minutes without using the "setarch i386 -3" trick. I am running a 64bit OS with 6GB of RAM, and I know that I used to require this trick. It has been about 3-4 months since I played, so I have updated wine and other things (running wine-1.7.0 right now).
1. Run winecfg. (If you have multiple prefixes, make sure it is the correct prefix) (If using PoL click on Diablo III and click "Configure")
2. In the 'Libraries' tab, type dbghelp into the 'New override for # library' box. (It's not otherwise listed)
3. Click 'Add', then 'Yes' when it asks if you are sure.
4. Click on 'dbghelp' in the 'Existing_overrides' list.
5. Click 'Edit'.
6. Set to 'disabled'.
7. Click 'OK', then 'OK'.
Diablo 3 and open-source amd drivers
by thathatman on Saturday September 28th 2013, 10:50
I wanted to report that diablo 3 is playable with the amd open-source drivers. It is slightly smoother than fglrx. I do experience graphical glitches in the form of red water.
This is with the playonlinux version of wine on ubuntu 13.04.
rubber banding and flickering fix
by Netsrotti on Saturday August 31st 2013, 2:41
I found that setting StrictDrawOrdering string to enabled in regedit solved the rubberbanding and graphics flickering bug in act3 and when opening too many menues. I'm using latest nvidia binary beta driver.
Found the regkey at wiki.winehq.org/UsefulRegistryKeys
Can only do 2-3 things, then game hangs "out of sync"
by Hauke on Wednesday July 31st 2013, 8:30
First my specs:
- Kubuntu 13.04 with disabled desktop-effects
- installed Diablo3 in a bottle (with Win32 set and Winver=WinXP) from ground up, but problem also occurs when i start my Windows-installed-Diablo3 with wine.
So the good thing is, i can start Diablo3 and everything seemingly works normally, good fps in menu, i can login with my character etc. I can also enter a game and play normally. Also starting an auction works.
But as soon as i do about two to three things in the menu (for example enter the auction house or switch a hero, or leave a game) the game is non-functional. Auctions cannot be started (although the button is clicked, i then wait for about 30 seconds to get the error). Yet the menu looks normal, it's animated etc. Only not usable.
I can - for example - log in, click "resume game" and play for a while. But as soon as i leave the game, and selecting "change quest" does not do anything, and clicking "resume game" brings up Error 316704
It feels like my gameclient and the server get "out of sync", i still can do stuff, but it has no effect on the game.
I then have to kill Diablo from outside the game (since clicking "Exit Diablo3" does not do anything) and restart wine to do more than one or two things.
Do you guys have any advice what could be the reason for this?
Anyone got banned in the last few months?
by vexorian on Saturday June 29th 2013, 17:01
Playing steam games natively reminded me of how much of a compromise it is to have to boot to windows just to play this game. I decided I will not do it anymore. The game itself isn't really worth such annoyances. So I am back to using WINE to play this game. If I get banned, so be it. A good excuse to stop playing this game and avoid buying the expansion.
I noticed there are apparently not any reports of WINE users getting banned ever since the time I got unbanned. I wonder if this is still happening?
by Johan Johnsson on Thursday May 23rd 2013, 11:20
Just wanted to share a problem I had on Manjaro Linux 0.8.5 with Diablo 3.
After my installation when I fired up the game I got an dialog telling me that there was a patch I needed and I could only click accept, then the game quits to the launcher that was telling me that the game was up to date. Fired up the game again to be met with the same dialog.
After much search I found the answer somewhere that a package named "lib32-ldap" worked for someone. So I started to search my package manager for similar file and found a package named "lib32-libldap" and installed it.
And that fixed the problem, now I can play. Hope this is for any use for someone!