WineHQ
Diablo III 1.0.*



Category: Main > Games > Role Playing Games > Diablo III > 1.0.*

NameDiablo III
Version1.0.*
License Retail
URLhttp://www.diablo3.com
Votes 32
RatingPlatinum
Wine Version1.5.26
Free Download Official game site.
D3 In Game #01
View/Submit Screenshot
Maintainers of this version:
Description
Game version that had been officially released on the 15th of May, 2012.
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)

What works
Note from AppDB maintainer: recent discussion of AppDB policies lead to a fact that this report is being considered to be invalid and is scheduled to be removed unless original poster would update it with the results of the game running under "vanilla" (unpatched) Wine. Sorry for that :-(.


* Downloader / Launcher
* In-Game Videos
* Gameplay 100%
* Menu System

I played for about 4 hours straight without any issues. I was able to change from fullscreen mode to window mode flawlessly (this is especially useful for using 3rd party chat/voice clients).


What does not
Everything I tested works without issue


What was not tested
Auction house - its unavailable until the 23rd.


Additional Comments

Computer Specs: 
CPU: Core i5
GPU: Geforce 560GTX
VRAM: 1GB
RAM: 8GB

Ubuntu 11.04 64-bit
kernel 2.6.38-15-generic
GPU display driver: 270.41.06

Note, I am using the latest version of wine from the git repositories (1.5.4).

The following patches need to be applied:
AcceptEX (http://bugs.winehq.org/attachment.cgi?id=39494)
GraphicsReset (http://bugs.winehq.org/attachment.cgi?id=39565)

Once the patches are included in the next release of wine, this should go platinum!
Test Results
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
ShowLinux Mint 14 "Nadia" x86_64Mar 18 20131.5.26 Yes Yes Platinum Brilguaz 
ShowUbuntu 12.04 "Precise" x86_64 (+ variants like Kubuntu)Mar 02 20131.5.24 N/A Yes Bronze Alexey 
ShowArch Linux x86_64Feb 16 20131.5.23 Yes Yes Platinum Papon Jonathan 
ShowUbuntu 13.04 "Raring" x86_64 (+ variants like Kubuntu)Jan 28 20131.5.22 Yes Yes Platinum vivid 
ShowGentoo LinuxJan 22 20131.5.21 Yes Yes Platinum Peter Pender 

Known bugs
Bug # Description Status Resolution Other apps affected
7991 Test Drive: Unlimited messed up graphics REOPENED View
11674 Dual-core unsupported in WoW and SC2 NEW View
30849 Diablo 3: Hangs on "Authenticating Credentials" NEW View
30920 Diablo 3: Random freezes UNCONFIRMED View
30963 Diablo III (downloader): Menu bar entries are keeping the background color UNCONFIRMED View
30964 Diablo III (downloader): Font is flickering in the "Connection Info" menu UNCONFIRMED View
30967 Diablo III: Resolution problems without virtual desktop UNCONFIRMED View
31072 Diablo III: Sound is very quiet UNCONFIRMED View
31262 Diablo III in game mouse cursor Out of sync, hangs in place. UNCONFIRMED View
31839 Mouse jumps to the upper left corner of the screen UNCONFIRMED View
32083 Diablo III: Missing logo on startup NEW View
32084 Diablo III: Crash on changing from fullscreen mode to window mode UNCONFIRMED View
32212 Mouse cursor not released from Blizzard based games UNCONFIRMED View
32844 Diablo III: character rotation in hero screen not possible while in-game NEW View
33111 Graphical Artifacts in Diablo 3 on AMD Graphics UNCONFIRMED View
33413 Diablo III: Intermittent non-responsive UI elements NEW View

 
Some Wine Diablo III users have reported suspended Battle.net accounts

Some Wine Diablo III users have reported that their accounts have been permanently suspended

This issue was originally reported on the forums and various others have reported similar problems (see http://us.battle.net/d3/en/forum/topic/5978861022 for more details).  However, many users have not had these problems and Blizzard has officially replied that using Wine should not get you banned:

"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!

 
Getting Diablo III to run best under Wine

General info

As of Wine 1.5.6 Wine is able to both install and run Diablo III.  However, if you are running an older version of Wine (such as the 'stable' 1.4.x branch), then you will need to either upgrade to a newer version of Wine or go through some extra steps each time a patch comes out (see the Historical Information section below).

FAQ

Q: I have a recent version of Wine (>= 1.5.6) and when I try to install the game the installer seems to be stuck at "0%".
A: Make sure you set your Wine prefix to emulate at least "Win XP". There were reports that best results are achived with version set to "Windows 7" or "Vista".

Q: I'm using a recent version of Wine (>= 1.5.6) and trying to install the game from DVD. Installer seems to be having problems with some files missing.
A: Mount your DVD with "-o unhide" mount option, it should help.

Q: When I start up the game and try to log in into battle.net I always get "error 3007".
A: You're on recent release of Ubuntu (or on any other distro affected by the ptrace bug, Bug #30410) or running a 64-bit OS. If you think you're affected by the ptrace bug then you can try executing the following in a terminal before starting Diablo III:
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
If you are running a 64-bit OS then you need to set the game to only use 3 GB of memory, to do this you'll need to modify the launcher to include "setarch i386 -3 " before calling Wine or launch the game from the game's folder in the terminal, like so:
setarch i386 -3 wine Diablo\ III.exe

Q: When I play the game I've got bright red graphical glitches at the places that are expected to be rendered full-black.
A: You had enabled forcing anisotropic filtering and/or texture sharpening in the GPU drivers settings utility. Make sure to turn it off into "let an app control it" state and your problem should be fixed.

Q: I'm using Intel GPU from recent series (HD 2000/3000/4000+). When I try to start the game it fails telling that my GPU lacks required features.
A: Make sure that you're on recent-enough distro (2012+) which contain fresh-enough Mesa (8,1+) and kernel (3.1+). Then make sure to install S3TC texture compression support lib (it might be illegal to do in some countries; how to install it is out of the scope of this FAQ - google for it) and start the game up from terminal like this: "force_s3tc_enable=true wine "

Q: I'm experiencing game crashes/hangs at certain places of the game world (like "Cathedral", e.t.c.).
A: Make sure to update your GPU driver. This problem is known to affect older versions of open source driver for ATI/AMD cards, and older versions of closed-source nVIDIA GPU linux driver. There might be other drivers out there suffering from the same problem we're unaware of, so updating driver won't hurt in any case.

Q: I've got "The application encountered an unexpected error." dialog box right after I start up the game.
A: This is most likely due to using builtin Wine's vcrun2008 DLLs instead of native. Try to install VC++ 2008 Runtime into your prefix, it should help. One of the ways to do it is to use "winetricks" script like that: "winetricks vcrun2008".

Q: I'm on Ubuntu and use Unity desktop environment. When I start the game it loads into a shrunk fullscreen where the Unity bar and universal task bar are still visible.
A: This is the incompatibility between compiz and many other applications which are considered by compiz to use "legacy fullscreen approach". You can workaround it by switching into using Unity 2D or by installing "Compiz Config Settings Manager" application and use "Legacy Fullscreen" support option found in "Workarounds" section.

Q: I'm using video card equipped with ATI/AMD GPU/APU and when I start up the game all I've got is a "black screen" or a "black window".
A: Most likely you had hit a bug in the video card driver. Your best bet would be try to update it to the most recent version. In case you are already using latest driver release (or in case it's hard for you to update video card driver for some reason) you might have some luck workarounding this problem by applying a small registry change to your prefix. What you would want to do is to set "AlwaysOffscreen" key to "enabled" under "HKCU/Software/Wine/Direct3D". You could easily do it with recent enough winetricks by executing "winetricks ao=enabled" for your Diablo III Wine prefix.

Q: I'm using video card equipped with ATI/AMD GPU/APU and the game runs fine but I've got some rendering glitches like "large semi-transparent polygons" or "strange triangle-shaped glitches near light sources".
A: It had been reported that due to some unknown reasons (bugs in driver? Wine doing something wrong?) for people using ATI/AMD GPUs it is required to switch Wine's DirectDraw renderer from using OpenGL into using GDI backend. This could be dobe by applying a small registry trick to your prefix. What you would want to do is to set "DirectDrawRenderer" key to "gdi" under "HKCU/Software/Wine/Direct3D". You could easily do it with winetricks by executing "winetricks ddr=gdi" for your Diablo III Wine prefix. Also switching the game to run in "Windowed Fullscreen" mode instead of simple "Fullscreen" might help.

Q: When I play Diablo III I've got extremely low or unstable FPS. My system is equipped with multi-core CPU (dual core or more).
A: This problem also happen on native OS but there it manifests itself as a micro-stutter (rapid FPS jitter). Under Wine for some people it gets much worse and could easily render the game into nearly unplayable state. If you happen to suffer from this problem you could try changing so called "CPU affinity" for main Diablo III process to only use one or two cores of your multicore CPU. How to do it depends on the linux distro you use. In any case first step would be to start up the game and then Alt+TAB from it and run your favorite terminal emulator. Possible commands to use are: (a) "taskset -cp 0 `pidof Diablo\ III.exe`" or (b) "schedtool -a 0 `pidof Diablo\ III.exe`". Using "0-1" or "0,2" in place of "0" might give better results, depending on the phase of the moon and the amount of luck you have.
Another way to achieve the same effect it is use Wine's "Task Manager". To do it execute "taskmgr" inside the Diablo III Wine prefix prior starting up the game and then Alt+TAB into it from game and use its built-in functionality to change CPU affinity of the "Diablo III.exe" process. You could do it by right-clicking on "Diablo III.exe" list entry at the "Processes" tab, selecting "Set affinity..." and de-checking all assigned CPUs except for "CPU 0". Don't forget to press "OK" button before Alt+TABing back into the game. For some cases it might be better to assign two cores for Diablo III main process, like "CPU 0" and "CPU 1" for "real multicore" CPUs (all multi-core CPUs by AMD up to but excluding AMD FX and later series; Intel multicore CPUs without HyperThreading support) or "CPU 0" and "CPU 2" for "SMT-faked multicore" CPUs (AMD FX and later; all HT-enabled Intel CPUs which are really multicore - i.e. Pentium 4 CPU which seems to be "dual core" isn't really "dual core" thus it doesn't fit into this category). Try experimenting with CPU affinity a little so you could find the value that suits your system best. To check FPS inside the game you could press Ctrl+R on keyboard. FPS counter would be displayed at the top left corner of the game window.

Historical Information

Using an old version of Wine to play Diablo III

To play on older versions of Wine (<1.5.6) you either need to upgrade Wine, patch Wine to support AcceptEx, or copy a working Diablo III install from another PC and run the game with the "-launch" command-line parameter. The process looks like this:

  • Copy a working Diablo III install (either from a recent Wine version or a Windows PC).
  • Open up a terminal and navigate into the folder with the installed game files (it is one where "Diablo III.exe" is located), for example:
    cd ~/".wine/drive_c/Program Files/Diablo III/"
  • Execute the command to run Diablo III without using the launcher:
    wine Diablo\ III.exe -launch
  • Repeat this process whenever a new patch comes out.

Patching an old version of Wine to play Diablo III

As of Wine 1.5.6 the patches submitted by Erich were committed and the launcher no longer requires them.  If you are using a previous version of Wine, 1.5.5 or earlier, please read below. 

To get the D3 installer and launcher to work flawlessly under Wine 1.5.5 and earlier, recompiling Wine with patches listed below is needed. You could do it yourself, or you could use pre-built binaries from third parties (in case you're risky enough to not mind security threat it imposes).  For the moment of the writing of this howto there's known PPA for Ubuntu-like distros which had been reported to provide a version of Wine binaries that had been patched to behave well with D3 installed/launcher. It could be found here: https://launchpad.net/~cheako/+archive/packages4diabloiii. Keep in mind that AppDB maintainers have no idea about what is "inside" that PPA and carry no responsibility about its contents.

Gentoo users might want for follow the FAQ provided by another AppDB user, Thomas Meister. He had shared his approach on how to patch and recompile Wine to be compatible with D3 for gentoo linux here: http://forums.gentoo.org/viewtopic-t-923504.html?sid=b35688bfdb6635072be8ef64a9025a99.

For brave souls who feel experienced enough to patch and compile Wine themselves (it's not that hard, really!), here are the links on the patchsets that are recommended to use:

"AcceptEx fix" patchset by Erich Hoover, "third" version (compatible and tested with Wine 1.5.5):

  1. [1/4] http://source.winehq.org/patches/data/86603
  2. [2/4] http://source.winehq.org/patches/data/86604
  3. [3/4] http://source.winehq.org/patches/data/86605
  4. [4/4] http://source.winehq.org/patches/data/86606

"AcceptEx fix" patchset by Erich Hoover, "second" version (compatible and tested with Wine 1.5.4):

  1. Part 1/3
  2. Part 2/3
  3. Part 3/3

"AcceptEx fix" patchset by Erich Hoover, "older" version (compatible with Wine 1.5.2 and a number or earlier versions, have known problems with 64bit arch; use this one only in case "new" version don't work work you):

  1. http://source.winehq.org/patches/data/86102 - [PATCH 1/4] server: Add completion information to async IO callback (try 2, resend).
  2. http://source.winehq.org/patches/data/86103 - [PATCH 2/4] server: Update stored completion information even after an async IO is queued (resend).
  3. http://source.winehq.org/patches/data/86104 - [PATCH 3/4] ws2_32,ntdll: Update async IO callbacks to include completion information (try 2, resend).
  4. http://source.winehq.org/patches/data/86105 - [PATCH 4/4] ws2_32: Use completion information to send AcceptEx completions (try 2, resend).

Note: after applying any of "AcceptEx" patchsets be sure to run "./tools/make_requests" from the top level of the Wine source directory.

Fix for the D3D error on game video setting change/restart

If you are using an old version of Wine (<1.5.7) and are experiencing an issue where you see the dialog "An error occurred reseting D3D. Click OK to retry" then this patch (taken from Bug #28201) should fix your problem:

  1. modified for 1.4+

 

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Patch Required!
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!

Best Regards!

[post new] [reply to this]

Once More UBUNTU is Broken
by Cory on Tuesday April 23rd 2013, 19:31
i was having a hard time getting D3 to work today on Ubuntu 12.10 was hanging up really bad so i ran echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope to turn off ptrace and the game runs now :(

[post new] [reply to this]

Diablo 3 performance on wine is greater, than on Windows
by Alexey on Saturday February 23rd 2013, 12:26
It is a strange thing, but I have greater performance of Diablo 3 in Linux(Ubuntu 12.04)\wine on my laptop with Radeon HD7600M, than on Windows 7.

On linux i have about 10-40 fps, when on windows only 5-20 fps on same graphical settings. Maybe wine do not render some graphics?

[post new] [reply to this]


by Alexey on Saturday February 23rd 2013, 12:21
I have the same problem with graphical artifacts on Radeon HD (fglrx 13.1) and wine. Tried all solutions listed above - nothing helped.

Tried Crossover demo - works ok, but I'm not ready to pay about $60 just to play diablo on linux, while the game itself costs only about $30 in my country.

Is there any other solution (maybe some kind of patches for wine for better radeon support) or anything else?

[post new] [reply to this]

Debugging Tests
by Doug Jacobsen on Monday December 3rd 2012, 20:40
I figured I would start a new thread as that one was getting long.

If anyone else wants to do the tests with me. I can try to give you any details that would be helpful for setting it up. But it would be useful to have multiple testers.

[post new] [reply to this]

Good experience
by Martin Juhl on Friday November 23rd 2012, 7:34
Hi all

Just wanted to share some good experience, and I hope that this info will help some of you..

I just reinstalled my primary gaming machine from Windows 7 to Kubuntu.. Have had two seperate machines (1 windows and 1 linux) for years, but since the release of the Steam beta, I'm now convinced that I can use Linux on the primary one...

Primary computer:
Dell Precision 490
2x Quad 2.66 GHz Xeon processors
16 GB Ram
nVidia GTX 560 TI


I installed Diablo 3 by creating a wine bottle with:

WINEPREFIX= WINEARCH=win32 winecfg

then installed:

WINEPREFIX= WINEARCH=win32 winetricks vcrun2008

and Diablo:

WINEPREFIX= WINEARCH=win32 wine

After waiting for the installer to download and install, the game started fine, but after entering a game, I noticed that the performance was horrible.. about 10 fps...

I fooled around with all kinds of wine and nvidia tweak settings, as well as taskset for locking the game to one physical CPU... this only gave me a few extra frames...

I then noticed that when disabling window effects in KDE (Shift+Alt+F12), I got a HUGE performance boost...

Now I'm running at about 40-70 fps, with all effects maxed...

On windows I have had alot of problems with microstuttering on Diablo, but I seems to have completely vanished on Kubuntu...

Happy gaming everyone...

[post new] [reply to this]

Did anyone get unbanned?
by ergo on Monday November 19th 2012, 10:25
(execept for vexorian)

www.cinemablend.com/games/Blizzard-Re-Review-Banned-Diablo-3-Linux-Accounts-Request-49431.html

[post new] [reply to this]

To clarify
by vexorian on Thursday November 15th 2012, 16:08
[I myself cannot verify any of this. But what is important to conclude is that my information is not going to help anyone in this thread getting unbanned, unfortunately.]

I mean, that regardless of what really happened, if Blizzard's version of the story is that Linux was not involved in my ban, then bringing up my case or story is probably not going to help in other people's cases.

[post new] [reply to this]

ok
by vexorian on Wednesday November 14th 2012, 14:27
I can't promise you that you will be contacted, but I passed this contact info.

[post new] [reply to this]

Changing keyboard layout to type in russian
by Yaroslav on Saturday November 10th 2012, 6:22
For russian to work in chat your locale should be set to russian too! I had en_US.UTF08 and russian was displayed as '??????? ??? ?????'.

so my script to run Diablo looks like this:
cd "/home/files/games/Diablo III/"
export LC_ALL=ru_RU.UTF-8
setarch i386 -3 -L -B -R wine "Diablo III.exe" --locale enGB --launch & pid=$!
taskset -cp 0 $pid && fg

[post new] [reply to this]

PlayonLinux Community
by furion85 on Saturday November 10th 2012, 2:59
A group of banned players gathered at www.playonlinux.com community.
We are trying to collect data of our systems and are in process of preparing open letter with our official stand on the problem. Everyone is welcome to participate in our effort, regardless of whether you used PoL or not to run the game.
Please fill out our template :www.playonlinux.com/en/topic-9679-Diablo_3_Ban_Information_Template.html and join discussion at
www.playonlinux.com/en/comments-1068.html and IRC channel #playonlinux at webchat.freenode.net/

Sincerely,
sonori

[post new] [reply to this]

Also banned from diablo 3
by Christian Broman on Tuesday November 6th 2012, 6:26
Im also one of them who got banned around november 2:nd for using linux.

This is my setup:
Linux name 3.5.0-18-generic #29-Ubuntu SMP Fri Oct 19 10:26:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 12.10 64bit
PoL v.4.1.8
PoL with wine-version called 1.5.5-DiabloIII_v3 64bit

[post new] [reply to this]

Banned
by Doug Jacobsen on Saturday November 3rd 2012, 10:16
I actually was just a victim of getting banned for what appears to be using linux.

Although bashiok says you can't be banned for using linux I don't know what else could have been the problem.

For the record too, I use play on linux, and the current version of wine I have set to play D3 with is 15.10. I don't know which version they banned me for using though because they give you almost no details.

I've submitted a ticket, and hopefully they will understand this is a false positive, but based on bashiok's post and the email they sent it appears they don't believe in false positives.

If anyone else has gone through a similar situation, any help would be appreciated as they don't tell you what kind of information you could provide to help them understand you weren't cheating/hacking/using bots.

Also, in case anyone is not clear on this, I have not used any hacks playing diablo 3.

I can't post on the blizzard forums without buying another copy of the game because my account is banned though, so I'm not sure what to do.

[post new] [reply to this]

  • RE: Banned by Doug Jacobsen on Sunday November 4th 2012, 8:47
    • RE: Banned by ergo on Sunday November 4th 2012, 9:39
      • RE: Banned by Doug Jacobsen on Sunday November 4th 2012, 9:43
        • RE: Banned by Doug Jacobsen on Monday November 5th 2012, 10:02
          • RE: Banned by Doug Jacobsen on Monday November 5th 2012, 13:22
            • RE: Banned by ergo on Monday November 5th 2012, 13:48
              • RE: Banned by Doug Jacobsen on Monday November 5th 2012, 13:51
Got Banned today
by ergo on Friday November 2nd 2012, 9:09
I've been using PoL on Ubuntu 12.10x64...it's abolutely ridiculous...

Greetings,

A user of this account has recently been involved in actions deemed inappropriate for Diablo III. The action taken on this account was made after a thorough investigation of the situation as a whole, so we can confirm that the evidence presented was correct, and that the subsequent action taken was appropriate in accordance with the Terms of Use (eu.blizzard.com/en-gb/company/legal/).

It is with regret that we have to take this type of action. However, it is in the best interest of the Diablo III community as a whole, and for the integrity of the game, that we have cancelled your access to the Diablo III servers. Our decision in this matter stands, and will not be overturned.
Please note it is our policy never to reveal details regarding account investigations, beyond the information given in the original notice mail, for privacy and security reasons.

If you wish to review our current Rules and Policies, they can be found at:

eu.battle.net/support/en/article/diablo-iii-policies
eu.battle.net/support/en/article/diablo-iii-account-penalties-policy

Any open bids or auctions at the time of the account’s closure have been cancelled. Your open bids will be refunded to your original method of payment. Please allow 5-10 days for processing depending on the availability of your financial institution. Any bids or auctions completed prior to the account’s closure will not be refunded or reversed.

Any heroes or items associated with the account are no longer accessible. The only way to continue playing Diablo III is to purchase a new licence. If you add a new Diablo III licence, the new account will overwrite your old account and any prior heroes or items will be permanently erased.

We understand that these policies may seem harsh, but they are in place to ensure that every player is able to fully enjoy their time spent on Battle.net.

Thank you for respecting our position.

Best regards,
Game Master Zhafarion

[post new] [reply to this]

If you are an active player and were not banned
by vexorian on Friday October 26th 2012, 7:52
I have a request. If you were active playing under WINE in the last few weeks and were not banned last Tuesday. What can you tell me about your setup? Distribution, kernel architecture, amount of RAM, desktop environment, WINE version (or PoL?). Etc.

[post new] [reply to this]

Recommended to use the work around in this forum report
by vexorian on Sunday October 21st 2012, 10:21
If you are on 64 bits and have more than 3Gb of RAM, then it is very recommended that you use the work around posted in the comments of this bug report: bugs.winehq.org/show_bug.cgi?id=30849

setarch i386 -3 wine .../Diablo 3.exe

It fixes many glitches I and other were experiencing. But more important. It appears that those glitches are caused by warden closing due to some RAM management issue. Running the game without warden could be the reason WINE users were getting banned.

(A couple of comments bellow I posted that the glitches were fixed after 1.05, but they came back around a day later. I suspect that blizzard just didn't turn Warden on immediately after the patch was released).

[post new] [reply to this]

Unity 2D and 3D slows or fps drops to 0
by S3P on Friday October 19th 2012, 11:25
Ubuntu 12.04

Unity (3D) - should be 28-35 fps (like win) but got variable from 6-25 FPS (changing fast ale the time) and it looks like 9 fps.

Unity 2D - Should be 30 fps (like win) but got 19 FPS and it looks like 19! ...but after 10-60 sec game goes to 0 FPS (it takes 40 sec to click on menu and exit diablo, very slow, it happens often when i click "Menu" in diablo 3)

I tried different Nvidia drivers but not all of them.
Tried PoL with wine .5 .6vdiablo .12 and options opengl, gdi, enable disable, and all possible combinations.

All fps in town.

[post new] [reply to this]

Patch 1.0.5 and Taskset Workaround
by Damien Clark on Thursday October 18th 2012, 5:03
After installing Patch 1.0.5 I noticed my performance was majorly degraded. After some research and such it seems Blizzard has worked on the "Stuttering" Problem.

For me, at least, removing the Taskset workaround (was part of my d3 startup script) has fixed the issue, with performance back to pre-patch levels, and with the bonus of not needing the workaround.

[post new] [reply to this]

Vast improvements after applying patch 1.05
by vexorian on Wednesday October 17th 2012, 0:40
I had plenty of issues before today (Game itself worked fine, but interface between the game had a habit of losing the connection to battle.net without any message and since then ignoring all requests. So trivial things like using the action house were difficult because eventually you would get disconnected. It was even hard to change hero (you needed a lot of luck for the game not to have a silent disconnect before you finish navigating the interface to change hero).

Today patch 1.05 was released and all those issues are gone. The game seems more stable. It used to take very long to log out or exit, but not anymore.

[post new] [reply to this]

For people trying the Public Test Realm (PTR)
by Sancho on Monday September 24th 2012, 7:49
I had an issue when I wanted to check out the PTR and launched the game with the "Diablo III.exe". I have described this here: tinyurl.com/cr3ftye

Short version: You have to add the command line parameter "OnlineService.PTR=true" for the region to be set correctly when not using the launcher!

[post new] [reply to this]

0%
by Landrovan on Saturday September 15th 2012, 17:36
To anyone who is still stuck with the 0% update problem.
I was having it while installing the game. I then go in the Options menu, in Downloader Preference and uncheck "use Peer-to-Peer". Then the download start correctly.

[post new] [reply to this]

Starter Edition
by Josko on Saturday September 15th 2012, 8:43
Hello, fellow wine users. I'm using:

- Arch x86_64
- 3.5.3 kernel
- 304.43 nVidia
- wine 1.5.12 (also tried 1.5.13 and 1.5.5 with AcceptEx) with a clean prefix/winetricks'd to get vcrun2008

but I can't get the Starter Edition to download and install using that installer from Battle.net.

Tried using enUS and enGB but it's always seemingly stuck at 0% (once got to 1% after 2 hours) and a lot of JSON-like output:

pastebin.com/b5dAbbpn

Seeing no one have this problem... what am I missing?

[post new] [reply to this]

Add vcrun for launcher
by damien on Wednesday August 29th 2012, 12:54
For the launcher, it works fine with the vcrun2008 (updates and play). Just install it with winetricks.

[post new] [reply to this]

disable amd cool and quiet
by damien on Monday August 27th 2012, 10:11
Hi,
When I disabled Amd Cool and Quiet feature (I've got a Athlon II , in BIOS, my framerate pass

[post new] [reply to this]

About the sound issue
by vexorian on Sunday August 26th 2012, 22:29
Until today, I was running 32 bit ubuntu 12.04 with pae kernel. Today I installed a 64 12.04, and installed WINE again.

The game sound was working well in the 32 bit ubuntu setup. And WINE setup was almost vanilla (only workaoround I used was do -launch).

[post new] [reply to this]

Banner achievement rewards not locked (Possible reason for ban?)
by vexorian on Monday August 20th 2012, 10:29
So, I wanted to try out starter edition. I copied what was downloaded from another computer to mine. Since my backup windows install has definitely not enough space, I took the risk of running in WINE.

Someone who has been played the same install that was copied was watching, and noticed that when I selected to choose banner style, he noticed that I the banner rewards were completely not locked in the diablo 3 instance I was running.

Banner style things are supposed to be locked until you get specific achievements.

Then I entered using my account in the windows install, and the rewards were locked.

So, in fact if running in WINE makes the client unaware of that the patterns are locked, this is a bug that, if blizzard detects you tried to use a reward that you didn't really earn, I think that it could in theory alert blizzard that you are cheating. Many users that try diablo 3 for the first time may not be aware that these banner patterns were not supposed to be unlocked.

I wonder if other people running diablo 3 in WINE have seen these rewards locked.

[post new] [reply to this]

Linux bans?
by Dheart on Monday August 6th 2012, 3:28
Hey,

What's the situation on the linux bans? It's been quiet for a while now... I'm thinking of buying the game, but if I am only going to get my cd key banned, i'd rather not.

Has anyone been playing the game recently on linux?

[post new] [reply to this]


by Night Nord on Wednesday August 1st 2012, 5:39
Does anyone has issues with mesa radeon (r600g) drivers? It crashing (with in-game crash dialog) me while trying to start/resume game (but show menu and logs in without a problem).

Mesa ~8* something (dunno exactly due to 32bit wine and 64bit OS. 64bit mesa is 8.1 devel).

[post new] [reply to this]

  • RE: by Antoine Vasseur on Wednesday August 1st 2012, 8:17

by Antoine Vasseur on Sunday July 29th 2012, 17:40
You seem to be out of luck for the moment.
Maybe you should try to tcpdump the communication between your client and battle.net just to see if there is at least any data transmitting or if it's only client-side.

[post new] [reply to this]

can't log in due to error 3
by Stefan on Sunday July 29th 2012, 8:20
Hi, I always get error number 3 whenever I log in. According to the blizzard knowledge base this error means my computer can't retrieve the updated eula/tou (us.battle.net/support/en/article/error-3).
I'm running archlinux64, Kernel 3.4.6
Brief summary of what I did:
- installed Diablo3 into a clean new wineprefix with the installer I downloaded from battle.net (worked fine)
- installed lib32-openssl and lib32-libldap to get around the "diablo is up to date, diablo needs an update, diablo is up to date..." issue
- tried to log in and got error 3
- searched the internet but only found reports on users getting other error numbers beginning with 3 (such as error 37, 3003, 3006)
- ran diablo with setarch i386 -3 (still I only get error 3)
- installed vcrun2008 into my Diablo3 prefix using winetricks (still I only get error 3)
- tried what the blizzard knowledge base supposed to do on this error (removed various cache files and directories from the battlenet software, tried to log into other region servers to trigger getting the eula/tou again, and so on. see link at the top of this post for more information)
- copied a working and up to date Diablo3 installation from a windows machine on my computer (still I only get error 3)
- I also tried different language packs, they all give me error 3
- installed Diablo3 again in fresh wine prefixes using the installer but having set wine to different windows versions (WinXP, Vista, Win7)
- tried everything I just mentioned in every one of these Diablo3 installations

Let me know if you need more information and what information you need.

[post new] [reply to this]

Running with the r600g mesa driver
by Andrei on Tuesday July 24th 2012, 14:51
Hi guys,

I have a graphics card with Radeon HD 3650 chipset that only scores about 10 FPS with latest code from git and all the tricks to improve performance I am aware of (pcie_gen2, ColorTiling2D, SwapbuffersWait).

1. Is there any other trick that helps perfomance? Maybe something specific to wine?

2. Does any of you get a playable FPS with a different graphics card and open source drivers (I know fglrx should give better performance, but I'd rather not go that way).

[post new] [reply to this]

Running on i3 graphics
by Manu on Wednesday July 18th 2012, 15:35
Hi,

I've got D3 running fine on my desktop pc (with nvidia) and just got a notebook which I want to run D3 on - just on minimum details etc.
So I installed it and tried it - it worked more or less out of the box.
Thought I had to use two "fixes" and run it with setarch (I have to do that on my desktop too) and the forced s3tc.
So the game is starting up and running - sadly It's very dark and e.g. the health bar (and the other, whatever it is) are shown empty - even thought they are full.
In addition to that it's pretty slow - but that may be caused by the performance of the graphic card itself.
I haven't tested it on windows, so this may be normal - but based upon the minimal specs it should be enough to run at minimal settings (I even used a wine desktop with 800x600) which can't realy be called playable.

[post new] [reply to this]

Possible explanation for the Linux bans
by Dave on Monday July 16th 2012, 8:24
Per the Q&A above, I used the following command line to execute Diablo 3:
WINEPREFIX=~/games/windows/diablo3 \
schedtool -I -e \
setarch i386 -3 -L -B -R \
wine C:\Program Files\Diablo III\Diablo III.exe' -launch -locale enUS

Could schedtool and setarch constitute the use of "Unapproved Third Party Software?"

[post new] [reply to this]

Remove the false warning "YOUR ACCOUNT MAY BE SUSPENDED"
by Txema on Saturday July 14th 2012, 13:37
That warning is false, please remove it.

Those who were banned were cheaters, and that doesn't have anything to do with WINE. I've been playing since the game was released and haven't had any problem.

[post new] [reply to this]

WineHQ Warnings about D3 Account Suspensions
by woefulwabbit on Tuesday July 10th 2012, 6:38
I've noticed the big red warnings on this page that "Diablo III users may have their accounts permanently suspended."

I think this is highly inappropriate since the account bans were isolated incidents unrelated to Linux or Wine. The 3-4 reported cases of being banned is miniscule compared to the number of players that continue to play Diablo 3 on Linux + Wine without being banned.

Please remove the fear-mongering. Thanks

[post new] [reply to this]

Diablo III refresh rate
by Guti on Sunday July 8th 2012, 11:40
Hey, I got a problem with refresh rate. I can't set refresh rate to match my desktop refresh rate which is 75khz, Diablo keeps changing it back to 60 (I edit D3Prefs.txt) :/ Any ideas? Diablo is running in virtual desktop in fullscreen.

[post new] [reply to this]

Crashing after launcher
by Vid on Friday July 6th 2012, 17:04
Here's my problem, the game is crashing for me as soon as I click the PLAY button on the launcher. The splash screen appears, but shows nothing except borders (no image or anything) and shortly the game crashes.

I have the game running from a new 32bit prefix with vcrun2008 installed, here are my logs:

WINEDEBUG pastie.org/4212496
terminal output when I start the game pastebin.com/mp88RVbm

I'm on archlinux, my wine version is 1.5.8-1, my graphics card is nvidia gt230m with 302.17 drivers.

[post new] [reply to this]

Diablo 3 crashes
by Tom Wijsman on Friday July 6th 2012, 12:22
After the GetLogicalProcessorInformation lines, I get the following:

fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:dbghelp:elf_search_auxv can't find symbol in module
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xb77e5742

When launching the launcher I can see it is up-to-date.

I'm launching the game with:

taskset -c 1 setarch i386 -3 wine "Diablo III\Diablo III.exe" -launch &

[post new] [reply to this]

System Crash
by Ferg on Thursday July 5th 2012, 10:27
System:
arch linux, nvidia gtx470, core i7 950.

Problem:
When i turn on "Texture Sharpening" in "Nvidia Settings" game work great, but have red graphical glitches - ferg.in/storage/IyEmLodt/
But when i turn off "Texture Sharpening" glitches gone and game start to freeze system in a few minutes after creating/joining game - ferg.in/storage/sJ7Ti9Q1/ And i still able to login via ssh, kill X, and restart xfce.

I tried different versions of nvidia drivers and x server. But it did not help. I also test my video card in a different programs (furmark, 3dmark, heaven benchmark, etc) and games but card works great in them.

[post new] [reply to this]

Diablo random crash
by kllim on Tuesday July 3rd 2012, 14:11
I've recently after the last 1.0.3 patch got some strange crashes. The game crashes at moments, sometimes after 5 minutes others I can play for hours.

The errors I get when the crash is happening:
pasteit.com/18150
And this error (maybe this one doesn't matter):
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.

My system:
Arch Linux x64
Custom wine 1.5.6 with patches
Nvidia 302.17-1
Tried both on NTFS formatet disk and EXT4.

Anyone experiencing the same issues?

[post new] [reply to this]

Crash when switching to windowed fullscreen
by Christian Widmer on Tuesday July 3rd 2012, 3:07
With wine 1.5.7 (the ubuntu-wine version for Ubuntu 12.04) the game crashes for me when switching from fullscreen to windowed fullscreen. After restarting the game, however, the option is correctly set to windowed fullscreen. Does anyone else experience this?

Here is the tail of the command line output: pastie.org/4191719

[post new] [reply to this]

D3 wont run with wine 1.5.7
by Josh Raymond on Friday June 29th 2012, 0:37
I was using D3 just fine with Wine 1.5.6, having a good time and what-not, on my Fedora 16 with linux kernel 3.3.6, I recently upgraded my OS to Fedora 17 using kernel 3.4.3, wine version 1.5.7(self-compiled)
Now everytime I startup D3, the launcher loads and patches everything just fine, but when I click play (or try to launch wine Diablo III.exe -launch directly) the game sits for a few second then errors out with a dialog box saying "An unexpected error has occured" I'm recompiling a 1.5.6 wine to try now but I would really like to know what caused this.

[post new] [reply to this]

taskset
by Rob Watson on Monday June 25th 2012, 19:49
for those of you who are having continuing problems with error 3007 or other such authentication issues AND are running with a multicore/processor system please try :
taskset -c X wine /path/to/diablo3/executable

Where X is one of your processor cores. At first this fix did not work for me using 'taskset -c 0 ...' but once I tried using 1,2,3, etc. for X instead of 0, things worked, magically.

[post new] [reply to this]

Problems with Timeouts in Auction House / main Screen
by DR on Sunday June 24th 2012, 11:50
Hi,

I am having problems with connection losses on the Main screen of the game and in the auction house.

I actually can play single player just fine.
I log in and start the game. I can play as long as i wish.

But some connection to the server seems to get lost after 2-3 minutes every time.

When i return to the title screen I can't get into single player or into the auction house anymore until I restart the game.

When launching D3 i can get into the auction house for aprox 2-3 minutes. after that all actions time out. I can't start a single player game anymore until restart.

Basicly i can do everything just fine for 2-3 minutes. After that my connections time out.

Single player isn't affected if it's started within the 2-3 minute timeframe.

[post new] [reply to this]

Banned?
by william on Friday June 22nd 2012, 8:48
Well I've had Diablo running on my FreeBSD machine now for a couple of weeks and have a level 53 Wizard.

I just got notice while trying to log in last night that I was banned, and when I checked my email, I hadn't received anything from Blizzard.

After I opened a support ticket with them, a short while later, this is what I received in email:

Account Action: Account Closure
Offense: Unapproved Third Party Software
A third party program is any file or program that is used in addition to the game to gain an unfair advantage. These programs may increase movement speed or teleport heroes from one place to another beyond what is allowed by game design. It also includes any programs that obtain information from the game that is not normally available to the regular player or that transmit or modify any of the game files.

I don't run any programs as described above.

I kite, I die, and then I repair. But hey it's fun.

Anyone else having a similar issue?

[post new] [reply to this]

  • RE: Banned? by Erich Hoover on Friday June 22nd 2012, 10:04
  • RE: Banned? by Mitch on Friday June 22nd 2012, 10:31
    • RE: Banned? by Marcus Meng on Friday June 22nd 2012, 13:08
  • RE: Banned? by sblanz on Friday June 22nd 2012, 16:45
    • RE: Banned? by sblanz on Monday June 25th 2012, 13:07
  • RE: Banned? by william on Saturday June 23rd 2012, 16:19
    • RE: Banned? by Marcus Meng on Saturday June 23rd 2012, 23:50
      • RE: Banned? by Marcus Meng on Sunday June 24th 2012, 12:01
      • RE: Banned? by Mitch on Monday June 25th 2012, 8:05
        • RE: Banned? by Marcus Meng on Monday June 25th 2012, 13:16
      • RE: Banned? by sblanz on Monday June 25th 2012, 13:10
        • RE: Banned? by william on Monday June 25th 2012, 14:57
          • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 4:21
            • RE: Banned? by Marcus Meng on Tuesday July 3rd 2012, 12:50
              • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 12:56
                • RE: Banned? by Marcus Meng on Tuesday July 3rd 2012, 13:01
                  • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 13:07
                    • RE: Banned? by Marcus Meng on Tuesday July 3rd 2012, 13:15
                      • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 13:18
                • RE: Banned? by william on Tuesday July 3rd 2012, 13:12
                  • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 13:21
                    • RE: Banned? by william on Tuesday July 3rd 2012, 13:26
                    • RE: Banned? by Matthias on Monday July 16th 2012, 2:53
                      • RE: Banned? by W. Usher on Monday July 16th 2012, 2:59
                        • RE: Banned? by Matthias on Monday July 16th 2012, 3:38
  • RE: Banned? by Randy on Sunday June 24th 2012, 19:44
  • RE: Banned? by William on Tuesday July 3rd 2012, 2:55
    • RE: Banned? by W. Usher on Tuesday July 3rd 2012, 3:04
  • RE: Banned? by cyanpill on Wednesday July 4th 2012, 0:42
I got rid of micro-stuttering
by alex on Friday June 22nd 2012, 8:33
Some of you may suffer from the ubiquitous micro-stuttering (not the major hdd-stuttering!) described here:
us.battle.net/d3/en/forum/topic/5270834509?page=1

I managed to greatly reduce the effect on my GTX 560 TI. Unfortunately, as i did multiple changes at once i cannot trace the important step but nevertheless wanted to share my experience:

What i did:
- updated the official nvidia driver from 295.40 to 302.17
- disabled my second monitor in the nvidia control panel and started the game (however, switching it on again makes no difference now)
- turned vsync on. Until today it hardly made any difference whether it was on or off. Today it runs only smooth with vsync activated.

There are still some stutters now and then but much less than before (about 2 times a second).

[post new] [reply to this]

DVD install?
by hyp3rdr1v3 on Tuesday June 19th 2012, 14:14
Total noob question, but is it possible to install d3 with the dvd? I'm not sure what I'm missing, I've tried wine but under install a game diablo 3 is not available. Clearly I'm doing something wrong..

[post new] [reply to this]

Wine64 on Ubuntu64
by Jeff on Friday June 15th 2012, 20:13
I was only able to compile wine64 on ubuntu 12.04 (see: bugs.launchpad.net/ubuntu/+source/wine1.4/+bug/944321) and not the 32bit support, is there a way to get diablo3 to run this way?

[post new] [reply to this]

Script for Launching Diablo 3
by Rob on Friday June 15th 2012, 1:45
I wrote this quick script for launching Diablo 3 and then setting it to use only the first core on my machine, I thought it might be useful to someone else.

Make sure that you change the setarch string to reflect your patched wine path.

the log1 and log2 redirects aren't necessary, they're just there for debugging.

Hope this helps somebody!


*** code ***

#! bin/bash

#Script to launch Diablo 3 with the correct affinity and wine prefix

setarch i386 -3 ~/wine-git/wine /home/rob/.wine/drive_c/Program\ Files/Diablo\ III/Diablo\ III -launch &
pid=$!
taskset -cp 0 $pid 1> log1.log 2> log2.log && fg

*** code ***

[post new] [reply to this]

Bug #24890 is not applicable
by Erich Hoover on Thursday June 14th 2012, 7:57
I don't know who attached Bug #24890 to this, but the Diablo III launcher does not generate the LWA_COLORKEY FIXME message. There's clearly a transparency issue with the launcher, but Bug #24890 is not the problem.

[post new] [reply to this]

setarch i386 -3 DOES NOT WORK in 32-bit user space
by NL on Wednesday June 13th 2012, 16:52
I am running 32-bit user space with wine 1.5.5

[post new] [reply to this]

Wineserver taking CPU load
by Blue112 on Tuesday June 12th 2012, 10:05
Hello here.

I can run Diablo with no problem in any mode (windowed, fullscreen in virtual desk) with more than 100 FPS. So it runs well.
Diablo III.exe is taking 102% of my CPU, but since it's a quad, it's ok.

Actually, it runs well well a few minutes (about 2). Then, wineserver takes 48% of my CPU and Diablo about 108%, and then the game just slow down to ~20FPS (actually it jitters from 10 to 30 FPS). It's kinda unplayable.

I'm running with the very lastest version of wine compiled from git (wine-1.5.6-32-g00fb537) but the problems happens with 1.5.4 too.

I've tried to Kill wineserver but it just makes the game crash :p

Do you know something I can do to fix that problem ?

[post new] [reply to this]


by Joshua on Tuesday June 12th 2012, 8:24
Cool so there is a new patch today

[post new] [reply to this]

A new patch
by Murph on Tuesday June 12th 2012, 8:19
When I try to play, I get told that there's a new patch.

But when I click OK it goes to the launcher which says game is up to date and no patch is downloaded.

[post new] [reply to this]

Problem with chat
by MonoBOY on Monday June 11th 2012, 8:03
Everything works fine, but after changing locations ceases to operate gaming chat. In what may be the reason?

[post new] [reply to this]

game only playable in virtual desktop
by Josh Stratton on Sunday June 10th 2012, 18:42
I've gotten wine working, but it is only playable inside a virtual desktop. If I run it outside a virtual desktop, I can't even get past the login screen and the music stutters.

Inside the virtual desktop, I only get around 10-12 fps. I've found as infernix has that if I run wine with the backbuffer as the render target instead of fbo, it greatly increases framerate (up to 30-35), but I get the same visual error (his screenshot below).

tinypic.com/view.php?pic=ay7wcz&s=6

Why would the game only function in a virtual desktop? What's different about it?

[post new] [reply to this]

ntdll:NtLockFile I/O completion on lock not implemented yet
by Matthew Grecar on Sunday June 10th 2012, 0:24
I compiled the new 1.5.6 version with hopes it would fix the problems I've been having trying to run Diablo, based on the latest report I saw for it. Different problem, but it doesn't seem to have worked.

I can run the launcher, which now seems to work great, but the problem is when I hit Play, or run 'Diablo III.exe -launch', it starts going but rapidly hits the 'ntdll:NtLockFile I/O completion on lock not implemented yet' error and crashes. It seems like it is trying to start displaying a splash screen, because I see a square shaped area over my terminal session that seems to not be redrawn as text below it scrolls past.

I've installed winetricks vcrun2008 as directed, and I compiled my kernel (3.3.7) with akmods-nvidia and that seems to show I'm using the nvidia driver (295.53).

Any ideas on how to diagnose what's wrong or where to go next?

[post new] [reply to this]

Bug when using SLI and Nvidia
by Jean on Saturday June 9th 2012, 8:20
Hey,

normally I'd write a bug report and I guess I'll do soon. However: If you try to run Diablo 3 in Wine (regardless of playonlinux, patched wine, normal wine) there seems to be a bug with a message "couldn't write memory". First I thought this is related to too much memory or 32bit/64bit so I removed the 12 GB ram from my box (running with 2 gb only) and tried it in 32 bit - The error is still there. However, as soon as I disabled SLI diablo 3 works.

So if anyone experiences that the game can't be started (launcher starts fine, when pressing play an unexpected error pops up, without launcher i.e. using -launch the same happens) and that person is using SLI with two nvidia cards - Try disabling SLI and see if that solves the problem.

In my setup I've got an amd quadcore + 2x nvidia 9800 GT in SLI + 12 GB memory.

Hope this helps.

[post new] [reply to this]

Random Crash While In-Game
by o.O on Saturday June 9th 2012, 2:00
All,

I've experimented with Ubuntu instance from 10.x to 12.x, and now I'm on 11.10 (all 64-bit). I've followed comments on this forum, PoL forum, and the bnet forums, and finally got to the point where I had D3 installed and past the authentication issue (with a token), and it would crash randomly before, during, or 30 min after authentication (while playing). Some seem to think it's a Warden issue, but my experience with compiling Wine, using PoL, and reverting to Win7, it seems like my problems stemmed from an old driver issue in Ubuntu 11.10. I uninstalled the system proprietary ATI drivers, downloaded the latest Catalyst (12.4) drivers from the ATI website, built them, and installed them..... so far so good. No random crashes or force reboots...

Root issue: I think it's related to old drivers overheating the video card. I don't have any details to go on other than some obscure post somewhere else having a similar problem prompting me to install the ATI proprietary drivers.

Sorry!

[post new] [reply to this]

Low FPS
by storm on Friday June 8th 2012, 18:40
I got unstable FPS, it is really annoying cause it get worse when it is players in my group. I have tried every single core combination and my GPU driver is up to date. I got Gainward GeForce GTX570 and an i5 3,3 ghz. so is it anything I can to to get more and stable FPS? :)

[post new] [reply to this]

How to fix everything.
by Harrison T on Friday June 8th 2012, 1:29
I was stuck on loading hero screen. I fixed it. Spread the word.
Done in 64 bit Ubuntu 12.04.

I used playonlinux and installed Diablo III the normal way. Then...

wget launchpad.net/~jcollins/+archive/jaminppa/+build/1482994/+files/getlibs_2.06-0ubuntu1%7Eppa2_all.deb

sudo dpkg -i getlibs_2.06-0ubuntu1~ppa2_all.deb

getlibs -p gnome-keyring:i386
(Type a capitol Y when it ask's Y/n. It's odd and rejects the lowercase)

Make a directory named pkcs11 in /usr/lib/i386-linux-gnu

sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/gnome-k… /usr/lib/i386-linux-gnu/pkcs11/gnome-key…

Also, use this to prevent hangup on "Authenticating Credidentials"
echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope

Credit to this: askubuntu.com/questions/127848/wine-cant-find-gnome-keyring-pkcs11-so


And that's it!!! Happy playing guys!!! Spread the word!

[post new] [reply to this]

Right
by Bohdan V. on Friday June 8th 2012, 0:56
It works too.

[post new] [reply to this]

  • RE: Right by Prot on Saturday June 9th 2012, 3:49
Diablo III Localization
by Prot on Friday June 8th 2012, 0:50
Someone have a play already russian localization of D3 ?
It works too?

[post new] [reply to this]

Think this will fix the log in issue
by storm on Thursday June 7th 2012, 19:12
try this command: setarch i386 -3 wine "/path/to/Diablo III.exe" -launch

The same issue where on Wow some time ago. it is a memory bug..

(PS: This worked for allot of people :)

[post new] [reply to this]

System Freeze @ Login
by 8bitpalace on Thursday June 7th 2012, 17:18
Got a brand spanking, annoying, consistent problem since last patch yesterday. Whenever I try to log in in Diablo III my system freezes, but the ingame music keeps on going. I know many people have already written posts about this problem, but there's yet no solution to it.

I only managed to login and play for about ~ 20 minutes before the game crashed (never encountered this before) when reinstalling the game through POL using wine version 1.5.5-DiabloIII_v3 and a clean wineprefix. When I, after another hardreset, tried to login my system froze and did so for about 3-4 more attempts.

This problem came with the new patch. I've had very few system freezes at login before and have been able to play for a 8 to 12 hour streak without hangups.

[post new] [reply to this]

leoric ghosts freezing
by Bohdan V. on Thursday June 7th 2012, 15:41
I have sucesfully installed wine-diablo (aur.archlinux.org/packages.php?ID=58739&comments=all) and started the game with that command line:

force_s3tc_enable=true wine explorer /desktop=3,1280x768 Diablo\ III.exe -opengl


But i have regular game freezing on location after killing leoric king`s ghost. Screenshot:

viter.in/files/diablo3.jpg

glxinfo (integrated hd 3000):
pastebin.com/f8uz9t7j

uname:
Linux localhost 3.4.1-1-ARCH #1 SMP PREEMPT Tue Jun 5 09:05:01 CEST 2012 x86_64 GNU/Linux

wine:
wine-1.5.5

[post new] [reply to this]

ATi && Authenticating/Hero List Fixes
by neptoess on Thursday June 7th 2012, 10:22
Hi guys. I posted fixes for ATi problems and the authenticating stuff on PlayOnLinux's Forums. I'll copy/paste them here:

Alright, a little background. Here's my hardware:
MSI GT725-075US:
-C2D P9500 (2.53 GHz Dual-Core)
-4 GB RAM
-ATi Mobility HD 4850

Software:
-Fedora 17 XFCE Spin x86_64
-XFCE 4.10
-Xorg 1.11.4
-Catalyst 12.4

Anyone who wants to know how to get 12.4 working under Fedora 17 can check my wiki entry on cchtml.

Here's how I got it working:
-Install via PlayOnLinux
--This installed fine, but then crashed upon clicking Play
--I solved this by:
---Opening a terminal
---export WINEPREFIX=$HOME/.PlayOnLinux/wineprefix/DiabloIII
---winetricks --no-isolate vcrun2008
--To fix graphical glitches in the game:
---Set DirectDrawRenderer to gdi under PlayOnLinux's Configure->Display
---I also use Fullscreen, NOT Fullscreen Windowed
---If I see graphical glitches on the login screen, I change to windowed fullscreen but click cancel when it asks if I want to keep the settings
-After the latest patch, I couldn't get past authenticating credentials
--Open a terminal
--setarch i386 -3 playonlinux
--To make it simpler, I just edited my DiabloIII.desktop file and prepended
setarch i386 -3 to the Exec= line

Everything works perfectly now!

[post new] [reply to this]

News
by obsidian on Thursday June 7th 2012, 7:55
I can't go past the "login", it stucks EVERYTIME i click on it, i'm using echo bla bla bla command. That's weird till yesterday i could play flawlessly :/

[post new] [reply to this]

  • RE: News by Chris on Thursday June 7th 2012, 23:25
    • RE: News by obsidian on Friday June 8th 2012, 6:01
new bug fixed
by Torsten Andersson on Thursday June 7th 2012, 7:27
A new bug which caused diablo3 to be stuck on Retrieving hero list is solved by running setarch i386 -3 -L -B -R wine ~/path/to/Diablo\ III.exe
I found it on us.battle.net/d3/en/forum/topic/5271607015?page=17

[post new] [reply to this]

Random Crashes
by obsidian on Thursday June 7th 2012, 7:05
Someone else other than me, is experiencing random crashes after the last patch of today?

AMD ATI mobility radeon hd 4650
intel core duo
Linux Mint Maya 13

[post new] [reply to this]

The application encountered an unexpected error.
by jack on Wednesday June 6th 2012, 20:38
I'm trying to get D3 to launch on ubuntu 11.04 with wine-1.5.5. I'm getting the "The application encountered an unexpected error." error when I attempt to launch the game.

I have already installed vcrun2008 as suggested, as well as installing to a clean wineprefix.

Here is the output from wine.

----------------------
kelsey@kelsey-pc:~$ wine ~/.wine/drive_c/Program\ Files/Diablo\ III/Diablo\ III.exe -launch
fixme:process:GetLogicalProcessorInformation (0x32f348,0x32f948): stub
fixme:process:GetLogicalProcessorInformation (0x32f604,0x32fc04): stub
fixme:process:GetLogicalProcessorInformation (0x224bfd8,0x224c5d8): stub
fixme:process:GetLogicalProcessorInformation (0x224bfd8,0x224c5d8): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:process:GetLogicalProcessorInformation (0x234e3cc,0x234e9cc): stub
fixme:process:GetLogicalProcessorInformation (0x32ef10,0x32f510): stub
fixme:process:GetLogicalProcessorInformation (0x32f008,0x32f608): stub
fixme:process:GetLogicalProcessorInformation (0x32f008,0x32f608): stub
fixme:msvcp90:locale__Init stub
fixme:msvcp90:locale__Getgloballocale stub
fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
----------------------

[post new] [reply to this]

a few tips.
by robin hansson on Tuesday June 5th 2012, 13:39
hi. i previously posted here about screen tearing issues.
a big thanks to Alexey Loukianov for suggesting the gl_sync environment options.
now i've put this in the bottom of /etc/environment
__GL_SYNC_TO_VBLANK=1
__GL_SYNC_DISPLAY_DEVICE=DFP-1

after that i rebooted just to make sure.
then i fired up diablo and the tearing was gone!

however the game was a bit laggy compared to running it on windows.
a friend suggested i'd try limiting the diablo process to using just one cpu core using taskset.
so when you've got the game up n running. log in via ssh or something and run this:
taskset -cp 0 `pidof Diablo\ III.exe`

and now the game runs perfectly fluid!
it's amazing how much of a difference it made.

just thought i should share this to my fellow diabloers. :)

[post new] [reply to this]

Randomly closing during gameplay
by Adam on Tuesday June 5th 2012, 13:08
This is strange as I had been playing without any real problems until yesterday. I wonder if a system update has broken something. I am seeing two main problems now. When I can log in and play at all, within a few minutes the game either closes abruptly with no error message, or says I have been "removed from the game" and puts me back to the character screen.

When the latter occurs, if I try to make a new game I get an error and if I try to log out and log back in, I get a black screen and have to kill process.

On trying to log in after starting D3 again, I am getting stuck on retrieving hero list. If I hit cancel, the game freezes and I have to kill process again.

More often I just get the random game closing with no explanation, making the game essentially unplayable.

I've since tried reinstalling my graphics driver, completely rebuilding wine (both 1.5.5 and 1.5.4 with their respective patches), and reinstalling Diablo 3 itself. None of these seem to have any effect. I have tried various resolutions and windowed/fullscreen/fullscreen windowed combinations.

I am using Ubuntu 11.10 and running wine with "allow the window manager to decorate the windows" turned off, "allow the window manager to control the windows" turned on, and "emulate a virtual desktop" turned on. All the graphics settings in both D3 and amdcccle are turned all the way down to combat low fps. My graphics card is Radeon 5870 with the proprietary 12.4 catalyst driver. Again, this was working fine before and these are all new problems as of last night.

[post new] [reply to this]

New error cropping up?
by andrew m on Tuesday June 5th 2012, 1:33
I noticed several Wine users on the Battle.net forum reporting a message "You have been removed from the game" within several minutes of starting a game. Subsequent attempts to create a game receive error 316704 until Diablo III.exe and Agent.exe are restarted. They have to be killed manually after the bug occurs.

It may have started for Wine users tonight (June 3). We have not confirmed that this does not happen on Windows, but I thought I would check if people here are starting to have the issue. I'm asking on Battle.net if Windows users are affected.

Are others here receiving this message? Or can anyone confirm that the game is still working fine for them?

I'm beginning to wonder if it is some sort of anti-hacking hotfix they rolled out. One user reported being able to play on EU servers, but not US servers.

Battle.net thread:
us.battle.net/d3/en/forum/topic/5271607015

[post new] [reply to this]

Windows 7 vs. Wine game performance comparison for the same workstation
by Alexey Loukianov on Sunday June 3rd 2012, 22:10
As I've got Windows 7 space license to use and even got this OS installed on one of my HDDs (up till today I hadn't booted into it for about a year or so) I decided to check how does the game perform on my workstation when run under the native OS instead of Wine.

System specs are: AMD FX 8210 CPU, 8GB RAM, GeForce GTX 550 Ti 1GB VRAM, target gaming resolution - 1920x1200.

Under Wine I've been having around 60 FPS for "static" in-game places (i.e. when there are no large packs of mobs displayed on the screen) with noticeable stutters at the moments when game engine had been fetching some data into the memory (i.e. on HDD accesses) and FPS dropdowns to around 20-30 coupled with noticeable stutters when there were large packs of mobs attacking my character (skeletons prior to fight with Leorik; Act 3 snow tundra fields). My general impression about game performance under Wine was "runs pretty well but it would be great if there were less stutters and FPS was a bit better".

Same workstation and even same HDD with Diablo III installation (it is ext3 volume that had been accessed on Win 7 through ext2fsd driver) performs noticeably better under native OS. Stutters on content load are still there and as HDD I used as a storage place for D3 installation is a pretty fast and modern 10k RPM model I suppose that the only way to mitigate these stutters is to use fast SSD and I bet that there would be slight stutters from time to time even with it. FPS is in generally slightly better - around 80 for places where it was 60 under Wine, and there are no significant stutters/slowdowns on encountering mobs packs. To summarize: FPS under native OS is much more stable when compared with one under Wine. I suspect that it is either linux OpenGL or wined3d who suffocate and serve as a tight spot when there are a lot of vertexes to process.

It should be noted that there are ways to temporarily drop FPS down to pretty low levels no matter the OS, most probably due to not-so-fast-performing game physics engine. Same FPS drop to around 15-20 could be achieved both on Win 7 and under Wine when the game character demolish a lot of destructible objects at once (barbarian's "leap" on a big pack of barrels/amphors or any other destructible things).

[post new] [reply to this]

screen tearing
by robin hansson on Sunday June 3rd 2012, 19:28
hi.
i'm running diablo 3 using the 1.5.5 diablo III v2 on ubuntu precise with an nvidia graphics card.
the game runs great except for screen tearing.
i've tried setting vsync both on and off in nvidia-settings and in diablo 3 but the screen tearing is still there. it's in fact a bit worse when you turn vsync on in diablo 3.
anyone else getting this?

[post new] [reply to this]

Possible fix for ALSA/PulseAudio sound chopyness
by Daniel on Wednesday May 30th 2012, 23:42
When I start up diablo 3, all the sounds are either garbled or the sound cuts out after about 2 minutes (for the entire system).

I found this fix online...

rm -r ~/.pulse ~/.asound* ~/.pulse-cookie

I put it in my ~/.profile file and in the script I use to start diablo 3, and I haven't had problems sense!

I'm guessing pulseaudio gets it's settings from a bad global file. Any clues on how to fix the actual problem?

Pass it on!

[post new] [reply to this]

Sound problems
by Pedro de Lara on Monday May 28th 2012, 15:55
I have managed to install the game without issues by patching wine 1.5.5 with the 5 patches however I am having some stuttering audio issues.

If I switch it to Alsa and it seems to help most of the time however I'd like to keep running on pulse if possible.

The audio is stuttering, like if it was playing slow or having a bad echo problem.

Anybody had the same issue who can maybe shed some light?

Also I don't know if it is my laptop or wine but my FPS goes to the ground if I play anything other than fullscreen, everything on low and lowest possible resolution which kind of sucks.

[post new] [reply to this]

Problem with hangs the updater of installation
by obsidian on Friday May 25th 2012, 7:44
I got it worked on my OpenSUSE 12.1 by copying the "battle.net" directory from a windows user to my wine station. Just do that.
Make Diablo 3 launch, when the launcher/updater hangs, then close wine with processes, than, copy Battle.net directory from a windows friend, familiar, it should be situated in user/username/applicationdata, that is hidden in windows, copy it in your user/public/applicationdata folder that diablo 3 creates in your wine prefix. Then launch the game/updater again and it should work, at least it worked for me.

[post new] [reply to this]

gallium
by diego on Friday May 25th 2012, 1:32
has anyone tried the new driver gallium?

[post new] [reply to this]

  • RE: gallium by Alexey Loukianov on Friday May 25th 2012, 6:01
  • RE: gallium by obsidian on Friday May 25th 2012, 7:34
  • RE: gallium by Patrick O. on Friday May 25th 2012, 22:38
    • RE: gallium by Mike Mestnik on Tuesday May 29th 2012, 21:08
      • RE: gallium by Patrick O. on Tuesday May 29th 2012, 23:40
        • RE: gallium by Mike Mestnik on Wednesday May 30th 2012, 10:37

by lyon on Wednesday May 23rd 2012, 3:39
youtu.be/HH3TQUz1PhI
Other videos from wine gameplay are there as well.

Debian Squeeze
nVidia blob 295.20
Kernel 2.6.38
Wine 1.5.0 + patches
GLC for recording

[post new] [reply to this]

Black Screen on startup
by Microwave on Tuesday May 22nd 2012, 9:40
Music plays,and a window launches,but is black. Running archlinux 64bit with patched wine 1.5.4.

NVIDIA 7800GT running 295.53 drivers.

Getting tons of fixme:d3d:resource_check_usage Unhandled usage flags 0x8
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
and

Any help would be appreciated

[post new] [reply to this]

echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope system freeze
by meLon on Monday May 21st 2012, 20:01
I am unable to login to Diablo III.

My system freezes (leaving only my mouse and Diablo music active) whenever logging in with the 3007 solution posted above:

echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope


CTRL+ALT+DEL and CTRL+ALT+F{1..12} do nothing.

12.04 Ubuntu x64 3.2.0-24-generic


AMD FX(tm)-8150 Eight-Core Processor

01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cayman PRO [Radeon HD 6950] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Device 3121
Flags: bus master, fast devsel, latency 0, IRQ 73
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at fea20000 (64-bit, non-prefetchable) [size=128K]
I/O ports at e000 [size=256]
Expansion ROM at fea00000 [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: fglrx_pci
Kernel modules: fglrx_updates, fglrx, radeon

[post new] [reply to this]

Texture issues and other artifacts
by infernix on Monday May 21st 2012, 13:48
So I'm running with fglrx 12.4, Radeon 7850, Debian Sid and 1.5.4 with the latest AcceptEx and reset patches.

I get some weird graphics with textures, and some artifacts: i.imgur.com/KhOhw.jpg

The artifacts (top left, and the weapon) aren't permanent, they seem to come and go while moving. But the textures are permanently like that; it seems transparency isn't working.

Anyone else seeing this? Is there a way to fix this?

[post new] [reply to this]

Installer and Downloader works in 1.5.4 on my siduction!
by Richard Schieder on Sunday May 20th 2012, 17:57
Installer and Downloader works in 1.5.4 on my siduction distribution (www.siduction.org). It runs flawlessly with my downloaded Version!

[post new] [reply to this]

Not starting after debian testing update xorg
by dyna on Sunday May 20th 2012, 13:38
After updating debian testing with xorg updates, the game no longer starts for me.

The updates causing the problem seem to be: xserver-common / xserver-xorg-core. Downgrading them from 1.12.1-2 to 1.11.4-1 fixes the issue.

[post new] [reply to this]

Resolve installer crashing with memory access at 0xFFFFFFFF
by J on Sunday May 20th 2012, 12:08
With the patches provided above, I was able to get the installer running. However, there was no sound and it always crashed at 1% with an invalid memory read at 0xFFFFFFFF, with the traceback pointing at DirectSound.

Arch x86_64 wine 1.5.4 from git + AcceptEx patches.

I used winetricks to install the native DirectSound ('winetricks dsound') and then installation worked as expected with music (although the music did stutter a bit).

Hope this helps someone else.

[post new] [reply to this]

Low FPS and red water or red instead of black.
by Mike Mestnik on Sunday May 20th 2012, 5:09
OpenGL trace FROM wine:
c566453.r53.cf2.rackcdn.com/slow.trace.xz
www.youtube.com/watch?v=TRsYPTqh_LQ

D3D9x trace TO MS Windows(2k8 server):
c566453.r53.cf2.rackcdn.com/Diablo_III.trace.xz
No video, notes 1. the water looks great. 2. The FPS is ?vary? high.

The idea is the discover IF Diablo3 uses multiple rendering methods, if the calls made are different as to account for hardware(video card) deficiencies.

Could some one compare these to see if they might have been created using the same drawing/rendering commands?

If they were then this might indicate that the Linux video drivers are missing something that the windows drivers have. If not then that indicates that D3 is probing wine and getting an incorrect response. In this case we need to trace D3 to discover what this probe is and then decide what the correct response should be. Who knows what will happen next, hopefully wine will be updated to always give the correct response.

Thank you.

[post new] [reply to this]

General Slowness/Walking Speed.
by Mike Mestnik on Sunday May 20th 2012, 1:11
I've been working on this, as I've determined it's vary closely tied to frame rate.

us.battle.net/d3/en/forum/topic/5150106576
www.youtube.com/watch?v=qvZX9F1jNZQ

I'm not confident this is a wine bug.

[post new] [reply to this]

Not getting past authenticating credentials
by Charles Myers on Saturday May 19th 2012, 18:48
Hello. Over the past few days, I managed to get Diablo 3 installed and running fine with PlayOnLinux and a version of WINE that (presumably) has all the aforementioned patches (it's called something like 1.5.4-DiabloIII in the list). Everything ran fine, as far as I was concerned (except for massive lag and slowness due to my current machine, as you'll see in the specs below).

Last night, I updated Ubuntu to the latest release and ever since I have not been able to get past authentication of my login info. I know it's checking my information because it returns an error when I put in the wrong password. The program doesn't hang (the login screen animation still plays) and I can cancel at any time. I have also tried vanilla 1.5.4, to no avail.

My specs are below:

HP Pavilion p2 64-bit p2-1110
AMD X2 E-450 (1.65 GHz 512 KB L2 cache )
3gb RAM
AMD Radeon HD 6320 (on-board)
Xubuntu 12.04
Kernel v3.2.0-24-generic
PlayOnLinux

Let me know what other information I'll need to provide. Thank you in advance.

PS: Yes, Diablo 3 runs on this ;p

[post new] [reply to this]

To Moderator:
by Josh Raymond on Saturday May 19th 2012, 16:20
The only thing I had to do inorder to get the installer/updater/launcher to work without patching is just follow the steps for the workaround blizzard offers incase you have the same problem with the NORMAL windows launcher. The problem was for me, on unpatched wine, that the installer and launcher would get stuck at "checking for updates" or "updating setup files" to correct this, you go to $WINEPREFIX/drive_c/users/Public/Application Data and delete the Battle.net folder. OR run the Agent.exe contained in WINEPREFIX/drive_c/users/Public/Application Data/Battle.net/Agent.954 and it will run just fine. I had to do the same exact thing when installing it on a native windows boot, so its the same problem. That however is not a WINE glitch, or WINE workaround, it's a apotty programming problem on Blizzards part.

As for the ATI cards, I cant be 100% sure because it was not ME that collected the data on ATI cards, I refuse to use one, however my friend loves them, he said there were no major(or even minor) glitches worth recording, using the ATI 12.04 graphics driver. Using 12.03 he has some minor graphical isues.

Also I would like to add that Alt-tabbing DOES work for me, however, if you open a webpage from within the game (like if you click the More Info buttons in the Auction House UI) and open a web page it works fine, until you try and return to the game, I had to restart the game to be able to play again, however I'm not certain if this is a WINE or a Blizzard issue as I don't have access to my WindowsXP-x64 boot at the moment.


My intention is not to devieve or trick the AppDB users, this information is (to the best of my knowledge) as accurate as it can be.

[post new] [reply to this]

Installer issue: BLZPTS00007 , FreeBSD 9.0, (Patched wine)
by william on Saturday May 19th 2012, 16:07
I'm getting the exact same errors as described by alphachi, also described in
this post to the winehq forums:

forum.winehq.org/viewtopic.php?t=15659&start=0&postdays=0&postorder=asc&

I am also running Freebsd and have ran the patches 1-3 ,then ran
tools/make_requests, on a newly uncompressed copy of 1.5.4 wine.

If i delete /drive_c/users/Public/Application Data/Blizzard.Net/*.* , after running the installer it does pull a new copy of them, then restarts and hangs eventually giving the BLZPTS00007 "Agent could not be started...wait a minute and try again" alerts.

Hopefully this helps let me know if i can provide more information.

[post new] [reply to this]

fullscreen not working
by Matthias Brunisholz on Saturday May 19th 2012, 14:30
I have patched wine 1.5.4 source and the installation is going well but when i launch the game i can't choose the full screen mode on my desktop. I can only play on the windowed mode...

With another installation on my laptop i can play in fullscreen.

With the two computers i have nvidia drivers but on the desktop i have a dual screen.

The two computers are on archlinux 64bits with a 32bits wine version.

Thank you very much

[post new] [reply to this]

Diablo III 1.x on FreeBSD 9 Release amd64
by alphachi on Saturday May 19th 2012, 10:56
Hardware: Intel core i5-760, Nvidia GeforceMX 460 1G, Asus P7H55M-Plus, Kingston 4Gx2
OS: FreeBSD 9.0 Release amd64
Software: Wine 1.5.4 & 1.4.1

We have all patches of Wine 1.5.4 or 1.4.1 for Diablo III 1.x, but these messages circle to error BLZPTS00007 when running the game:
...
err:wininet:open_http_connection create_netconn failed: 12029
fixme:process:GetLogicalProcessorInformation (0xcef008,0xcef004): stub
fixme:process:GetLogicalProcessorInformation (0xcef008,0xcef004): stub
...

BLZPTS00007 is us.battle.net/support/en/article/BLZPTS00007.

We think the Agent.exe is not compatible with Wine on FreeBSD.

Thanks for David Naylor!

[post new] [reply to this]

Graphical glitch on every glowing part
by Mikael Öhman on Saturday May 19th 2012, 5:55
I see this glitch everywhere:
imgur.com/PtW0N
every glow seems to have missing parts. Also affects grass and water.

Anyone knows if this is fixable?

GPU: AMD HD6770 (fglrx driver 12.4)

Packages:
Kernel 3.2
Catalyst 12.4
Wine 1.5.4 + resetfix
vcrun2008 installed

[post new] [reply to this]

A note on dyes
by Snowie on Friday May 18th 2012, 19:01
While I can successfully launch the game on 1.5.4 using wine "Diablo III.exe" -launch, characters with dyed armor seem to flash between the default colors and the dyed colors. Anyone else experiencing this?

[post new] [reply to this]

Wine won't load native msvcr90
by Romain "Artefact2" D. on Friday May 18th 2012, 17:23
Game won't load for me, I keep getting the "The application encountered an unexpected error." error dialog.

I'm using Wine 1.5.4 on ArchLinux x64.

I installed the game with the patched wine and it installed without issues, but this problem is also present in vanilla wine.

I ran "winetricks vcrun2008", and the override is right there in winecfg, yet when I start the game, I have:

paste.artefact2.com/p/11edf0c (ran with +loaddll)

Which is odd considering I have the "native,builtin" override for msvcr90. I think it's worth mentioning the installer may have put its own copy of the library in the game directory itself, as I have msvcp90.dll, msvcr90.dll and Microsoft.VC90.CRT.manifest in my D3 directory.

If I set the override to native only, I get these errors paste.artefact2.com/p/35ed936 suggesting it's not finding the native library.

Any suggestions? It seems to work fine for everyone else, so I must be doing something wrong. Thanks!

[post new] [reply to this]

Speed?
by Murph on Friday May 18th 2012, 11:47
Does anyone else notice in coop games they seem to run slower than everyone else? (And I don't mean just due to a % run faster item in game). Sometimes it seems rather noticeable.

Also, the sewers in act 3 seem to run really slow for me.

[post new] [reply to this]

  • RE: Speed? by Josh Raymond on Saturday May 19th 2012, 2:23
  • RE: Speed? by Jason Wood on Saturday May 19th 2012, 13:12
    • RE: Speed? by Jason Wood on Saturday May 19th 2012, 13:18
    • RE: Speed? by Jason Wood on Thursday May 24th 2012, 14:36
      • RE: Speed? by Alexey Loukianov on Friday May 25th 2012, 3:20
        • RE: Speed? by Mikael Öhman on Tuesday May 29th 2012, 20:05
  • RE: Speed? by spiralofhope on Monday May 21st 2012, 5:18
    • RE: Speed? by spiralofhope on Monday May 21st 2012, 17:04
    • RE: Speed? by spiralofhope on Monday May 21st 2012, 19:27
      • RE: Speed? by Alexey Loukianov on Monday May 21st 2012, 19:50
  • RE: Speed? by Jenny on Saturday May 26th 2012, 12:38
Copying Diablo 3 from Windows installation
by Tom on Friday May 18th 2012, 9:08
Tried patching but always brought up an error when the downloader opened. I have a working windows installation, which files are required to be copied over?

[post new] [reply to this]

Graphics Error
by Ovidiu on Thursday May 17th 2012, 17:15
System:
Ubuntu 12.04
Radeon HD 6770
installed Catalyst 12.04 from AMD site.

Problem:
When clicking "Start Game" from D3 menu it hangs and i get this error:
Dialog Title: Graphics Error:
Message:
Coudn't initialize graphics even on default settings.
Please shut down any other 3D apps and try again.

I tried several video options in game with the same result.
Do you know how to solve this issue?
Thanks for feedback.

[post new] [reply to this]

Works great
by Rob Watson on Thursday May 17th 2012, 12:45
If you download and apply the patches in the sticky and use 1.5.4 or git as your source this game will run just as good if not better than WoW or SC2!

[post new] [reply to this]

Working with PoL
by Ken V on Thursday May 17th 2012, 10:19
Unfortunately I can't post my test results since I used PlayOnLinux but for those of you who just want it to work:

This is using Ubuntu 12.04 64 bit with nVidia drivers.

Download the Windows installer from BattleNet.

Next, installed PlayOnLinux from their PPA. By default, they run with Wine 1.4 which will get installed, but when installing Diablo III, they automatically install a patched version of 1.5.3 using the patches mentioned elsewhere here. Steps are for the PPA:

wget -q "deb.playonlinux.com/public.gpg" -O- | sudo apt-key add -
sudo wget deb.playonlinux.com/playonlinux_precise.list -O /etc/apt/sources.list.d/playonlinux.list
sudo apt-get update
sudo apt-get install playonlinux

See their website for more info.

The installer also needs firewall ports open for 1119, and 6881-6999. I installed Diablo 3 using PlayOnLinux selecting Diablo 3 and pointing at the installer downloaded earlier. The installer worked fine but when trying to play, it would hang at Authenticating Credentials and then kick me out with a 3007 error. I fixed this with this recommendation also on the PlayOnLinux site:

echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope

After that, everything worked great.

[post new] [reply to this]

Unable to patch
by Josh Raymond on Thursday May 17th 2012, 9:38
I'm able to compile 1.5.4 from source completly on it's own, however, after applying the 4 patches, it gives me the following error after using "make"
sync.c: In function ‘invoke_apc’:
sync.c:871:69: error: ‘const struct ’ has no member named ‘chandle’
sync.c:872:44: error: ‘const struct ’ has no member named ‘ckey’
make[1]: *** [sync.o] Error 1
make[1]: Leaving directory `/home/josh/Downloads/WINE/wine-1.5.4/dlls/ntdll'
make: *** [dlls/ntdll] Error 2

I don't know why this is happening, like i said, with no patches, wine compiles and installs beautifully. With patches, wont make it back make

[post new] [reply to this]

Performance problems while mouse over objects
by ReCon on Thursday May 17th 2012, 8:29
I found out, that the FPS is going down, when I move my mouse cursor over an object. This FPS issue is available as long as my mouse is standing over that object and this object gets highlighted.

Somebody also get this problem?

Also, I have to use only one core (with taskset -p1 PID for example) to get a flawlessly game experience. Does anybody know, how I can get WINE running on multiple cores, without a choppy FPS? If I set the process to the taskset -pf again (means, use all Cores), the FPS goes heavily down. But if I just use one core, the game runs much better as far, as you don't have to fight versus a bigger group of enemies.

[post new] [reply to this]

No extra dlls needed
by Lee Trager on Thursday May 17th 2012, 2:15
With the patches applied I did not need to install any extra dll's(vs2008 as is suggested).

[post new] [reply to this]

patches fail when building on 64bit
by Lee Trager on Wednesday May 16th 2012, 22:15
Just an FYI the patches cause wine to fail to build 64-bit wine. Since most windows programs including D3 are 32-bit only you should be fine only building the 32-bit version.

[post new] [reply to this]

Diablo 3 - AMD HD 6850, Debian Testing - Slow Performance
by Andy on Wednesday May 16th 2012, 20:24
Hi,

I am using a self compiled version of Wine 1.5.4 including Graphics Reset, AcceptEx and 3 other patches by Erich. I installed MS VC++ 8, IE8, gecko120 (as the default geckosetup is not possible and running it manually with msiexec will fail with "storage create not supported"), dotnet20 and DirectX9 in the Diablo 3 prefix (yes, I am using a special D3 prefix).

As OS I am running Debian Testing x64 (Kernel 3.2.0.0-2) with 8 GB RAM, AMD Phenom II 955 processor, a AMD HD 6850 GPU and a display resolution of 1920x1080 pixel. I tried this with fglrx 12.03 and 12.04 (newest). Running HoN for Linux (native) is fine, D3 under Windows as well.

Diablo 3 itself is running fine but with too few fps. I would say I have about 20 fps (standing still, doing nothing with luck the meter hits 30 - sometimes) on low graphics settings. It does not change that much when I change graphics quality although I can't tell you any specifics as the fps meter is not very accurate. The processor is used to 100% which means that 25% of my quad core processor is occupied. However I checked and verified that D3 can use more than that 100% so the problem should not be related with my processor.

I tried OffscreenRenderingMode=backbuffer but then I can't read the menu, videosizememory=1024 and setting glsl=disabled (use arb shaders) makes D3 launcher deny any startup with "[...] HD 6800 series - unsupported graphics card detected".

Can you confirm the issue being related to AMD graphics cards? Did you have any more suggestions?

Regards,

Andy

[post new] [reply to this]

Mouse cursor stops moving eventually
by Scott on Wednesday May 16th 2012, 20:17
After about 5-10 minutes of gameplay, the mouse stops moving. The mouse is still usable (that is, you can still move around and attach and such), but the cursur itself doesn't budge from its current location. It still animates when you mouse over a questgiver and such, though.

When this happens, the following error is spammed repeatedly:

err:d3d_surface:surface_load Not supported on scratch surfaces.

Using Wine 1.5.4 under Arch Linux x64, WINEARCH=win32, vcrun2005 installed with winetricks, GeForce 560m GPU with 295.49 drivers.

[post new] [reply to this]

"Missing" dlls?
by Nick on Wednesday May 16th 2012, 17:53
I'm running Arch x86_64, and I installed the patched wine from AUR. I also installed winhttp and vcrun2008 like previous posters have stated. The downloader and the launcher work fine, but when I try to run the game I get this:

[ user@computer ~]$ wine /home/user/.wine/dosdevices/c:/Program\ Files/Diablo\ III/Diablo\ III/Diablo\ III.exe -launch
err:virtual:map_file_into_view failed to set 00000007 protection on file map, noexec filesystem?
err:module:import_dll Loading library ijl15.dll (which is needed by L"C:\\Program Files\\Diablo III\\Diablo III\\Diablo III.exe") failed (error c000007b).
err:virtual:map_file_into_view failed to set 00000007 protection on file map, noexec filesystem?
err:module:import_dll Loading library fmodex.dll (which is needed by L"C:\\Program Files\\Diablo III\\Diablo III\\Diablo III.exe") failed (error c000007b).
err:virtual:map_file_into_view failed to set 00000007 protection on file map, noexec filesystem?
err:module:import_dll Loading library icuuc44.dll (which is needed by L"C:\\Program Files\\Diablo III\\Diablo III\\Diablo III.exe") failed (error c000007b).
err:virtual:map_file_into_view failed to set 00000007 protection on file map, noexec filesystem?
err:module:import_dll Loading library icuin44.dll (which is needed by L"C:\\Program Files\\Diablo III\\Diablo III\\Diablo III.exe") failed (error c000007b).
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\Diablo III\\Diablo III\\Diablo III.exe" failed, status c0000135

I'll also note that I created a link to the actual location of the game on a separate drive. That's why the location is slightly odd. I actually created the link because of this problem, so it's not the cause.

[post new] [reply to this]

  • RE: by Nick on Wednesday May 16th 2012, 17:59
  • RE: by John Horan on Thursday May 17th 2012, 7:19
  • RE: by Alexey Loukianov on Thursday May 17th 2012, 11:18

by cyzz on Wednesday May 16th 2012, 17:44
Thumb UP!

quick and clear Howto
thx alot

cc

[post new] [reply to this]

Launcher prevents Game to login
by ReCon on Wednesday May 16th 2012, 13:51
I have patched my WINE (1.5.4) with the patches, which are mentioned above, but if I try to start Diablo III with the Launcher it ended up at checking my Battle.net account / login data.

If I start the game without the patcher (this means with the Diablo III.exe -launch option) it is running fine ...

Does somebody has the same problem?

[post new] [reply to this]

Some crashes
by Janne M on Wednesday May 16th 2012, 13:41
For me the game crashes at some specific places like at the cathedral.
It always crashes at the same locations. Any ideas?
Ubuntu 10.04 and wine 1.5.4


Here is some messages from console after a crash:

fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
Handle Event: "shutdown event"
Unregistered Periodic Event: "shutdown event"
Handle Event: "shutdown event"
Unregistered Periodic Event: "shutdown event"
Handle Event: "auth validation event"

[post new] [reply to this]

Initially loads with Unity bar still visible - Ubuntu 12.04
by Michael Kosler on Wednesday May 16th 2012, 9:01
imgur.com/n9Z28

When I initially load the game using wine path/to/.exe -launch, it loads into a shrunk fullscreen where the Unity bar and universal task bar are still visible. If I make any changes to the resolution, it works fine from then on (even going back to the original resolution provides true fullscreen), but just on initial load everything is shrunk.

Not a huge deal, but still annoying.

I am running using the Wine version found in this PPA (launchpad.net/~cheako/+archive/packages4diabloiii).

[post new] [reply to this]

wine 1.5.4 patched
by Michael Speth on Wednesday May 16th 2012, 8:14
Hi all,
I have compiled a wine version that works flawlessly with Diablo 3. I have tried this version of wine only with PlayOnLinux but I would suspect it would work via command line too.

You can try it out here:
ubuntuone.com/0MtV8LxxhSltExh6XIDFKR

[post new] [reply to this]

FAQ on how to install D3 on gentoo
by Alexey Loukianov on Wednesday May 16th 2012, 4:44
One of AppDB users - Thomas Meister - had shared his approach on how to patch and recompile Wine to be compatible with D3 for gentoo linux.

It could be found here:
forums.gentoo.org/viewtopic-t-923504.html?sid=b35688bfdb6635072be8ef64a9025a99

Thomas, thanks for your work on this.

[post new] [reply to this]

black and rectangles
by kwek on Wednesday May 16th 2012, 4:22
After applying the latest patches on wine git HEAD i'm getting the following: i46.tinypic.com/24ne88h.png .

It looks like some textures are missing, all buttons are black and hard to read. The interface and game does load but unable to play because i cant see what im doing :)

wine-1.5.4-94-g8ee1277
64bit gentoo linux with kernel 3.1.6-gentoo
nvidia drivers 295.49
2x GeForce GTX 460 in SLI

output: pastebin.com/L7vEeHQg

Let me know if more info is needed.

[post new] [reply to this]

Darker pixelshader
by frostbitten king on Wednesday May 16th 2012, 3:53
Did anyone try the darker pixel shader from www.darkd3.com/ with wine? Idk, if I did read the manual correctly, but after extracting the stuff into the d3 directory, starting and pressing pause in the game doesn't have any effect. Can someone confirm this?

[post new] [reply to this]


by frostbitten king on Wednesday May 16th 2012, 1:09
You are right, that was it. It was my last desperate attempt. I was a little bit surprised, when I saw the compatibility mode was win2k. Changed it to win7 but didn't give it much thought afterwards.
*facepalm*. Could have spared me those 4 hours of trying to figure out, why those patches didn't work.

[post new] [reply to this]

  • RE: by Alexey Loukianov on Wednesday May 16th 2012, 1:30
vcrun?
by ReCon on Wednesday May 16th 2012, 0:30
I just don't needed vcrun ... the game is just working with the patches mentioned above. No winetricks needed at all ...

Also the launcher is working. So, why get the test results submitter exhorted, when they talking about "Platinum in next release, when the WINE patches are included in generally"?

[post new] [reply to this]

  • RE: vcrun? by Alexey Loukianov on Wednesday May 16th 2012, 1:28
Gold rating?
by StefanT on Wednesday May 16th 2012, 0:26
A custom wine with special patches is required?
Come on, this is not gold rating.

[post new] [reply to this]

Authenticating Credentials / Error 3007
by spiralofhope on Tuesday May 15th 2012, 22:02
I patched the git version of wine, and got it installed. That version cannot run the program, I get this stuff:

err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
Direct3D9 is not available without OpenGL.

I can run the game with wine-1.5.3 and get to the login screen. However, I cannot get into the game itself.

I get "Authenticating Credentials". If I wait, I will eventually get Error 3007. I have never had any other sort of result.

[post new] [reply to this]

SOLVED: An unexpected decryption error has occurred
by Erich Hoover on Tuesday May 15th 2012, 21:14
I launched the installer from the disk ang got the error "An unexpected decryption error has occurred." Assuming this issue was similar to the problem with the Starcraft II disk I remounted the disk like so:
sudo mount -o remount,ro,unhide /dev/cdrom /media/D3C1.0.0/

Remounting the disk like this then allowed me to successfully run the installer.

[post new] [reply to this]

Installation
by frostbitten king on Tuesday May 15th 2012, 16:24
I applied the 4 patches successfully, but the installer is stuck at 0%.
Repeating something like "auth event blah"

[post new] [reply to this]

Install w/o Wine patches
by kantlivelong on Tuesday May 15th 2012, 15:04
I've compiled a little howto with the needed files to install.

This has worked for enUS,deDE,enGB so far...

www.sendspace.com/file/ti85mr

Let me know if this helps.

You can aquire the files yourself as well by running the downloader in VirtualBox/VMWare/Physical Box. Then instead of installing just copy the Battle.net directory from ProgramData to your wine install then follow from step 1.

[post new] [reply to this]

Fourth Patch
by Chris on Tuesday May 15th 2012, 9:38
Does the fourth patch even work?

I tried applying it to 1.4, 1.5 and 1.5.3 and it failed on 4/5 hunks each time.

I'm going to try with just what it did accept.

In any case, I currently (before these patches) can't get Diablo 3 past the login window, it hangs while authenticating.

[post new] [reply to this]

Graphical Glitch
by Mark on Tuesday May 15th 2012, 9:01
Fairly minor, as it's running smoothly otherwise.

It seems that everywhere the picture should be complete black, it's displaying a bright red, as here.

tinypic.com/r/nejn7r/6
tinypic.com/r/206k6qw/6

Running on:

Ubuntu 11.10 32bit
wine 1.5.4 (with all five above patches)
Intel Core2Duo
nVidia GeForce GTX 570 (tested with nVidia current and current-update drivers)
No dll overrides, etc.

Sorry if I missed some needed info; ask and I'll post it.

[post new] [reply to this]

Performance/Offscreen Rendering Mode issues
by Christian on Tuesday May 15th 2012, 3:41
The game works perfectly for me, but the frame rate is pretty low...at about 16 fps with all detail settings at the lowest value on my GeForce 8800GTX.
I was playing around with the D3D settings in the registry and took notice, that setting the OffscreenRenderingMode to backbuffer greatly increases performance to >50fps (with all detail settings at max).
The thing is, that the backbuffer mode produces glitches as shown in this screenshot:
tinypic.com/r/ay7wcz/6

I suspect backbuffer dimension limitations here.
Does anyone have an idea, how I might be able to fix that problem, or another idea how to boost performance a bit?

[post new] [reply to this]

Ubuntu 12.04 and Integrated Intel HD3000
by Marcus on Tuesday May 15th 2012, 2:17
I've seen reports that the Intel HD3000 will work with Diablo 3 (at least for people running windows).

The installation worked fine using the patched 1.5.3 version of wine, however when the game is launched it just say that "Diablo 3 cannot run because this graphics card is missing required features. Updating your driver may fix this".

Anyone else got it to work with an integrated Intel HD3000 card?

D3Debug.txt: pastebin.com/WS4JLm7P
Console output: pastebin.com/iVhzCMrL

[post new] [reply to this]

DVD Installer
by William on Tuesday May 15th 2012, 2:12
I purchased the DVD (as it was $10 cheaper than digital purchasing). Turns out to install from DVD, you must mount the DVD with -ounhide, else the installer complains about "Failed to extract required files from an archive.", error code BLZPTS00008.

[post new] [reply to this]




   << Back

Page loaded in 0.25461 seconds.