Diablo 3 not starting (error reporting dialog)

Questions about Wine on Linux
Locked
deki
Level 1
Level 1
Posts: 5
Joined: Thu Jun 28, 2012 12:19 pm

Diablo 3 not starting (error reporting dialog)

Post by deki »

Hi,

Diablo 3 is not running on my system (Debian unstable, Kernel 3.4, wine 1.5.6, Xorg 1.12.1 with radeon driver 2.4.33 and Mesa 8.0.3, ATI Radeon HD4850).
I created a fresh wine prefix, set the Windows version to 7, installed vcrun2008 and installed Diablo 3 (which worked without problems).
(After vcrun2088 installation, msvcr90 is listed with "native,builtin" order in winecfg)

But when trying to launch it, there is always the D3 error reporting dialog ("The application encountered an unexpected error.") and it just doesn't start.
Here are some logs that might help investigate the problem:

D3Debug.txt: http://pastebin.com/NJZ2mwkd
Console output with all warnings enabled: http://pastebin.com/LQDwNdxD (WINEDEBUG=warn+all,+loaddll wine Diablo\ III.exe -launch)
winedbg with D3 dump file: http://pastebin.com/GJDyuVqz (winedbg App-0.dmp)
D3 Agent Log: http://pastebin.com/htfQALEw (drive_c/users/Public/Application Data/Battle.net/Agent/Agent.1040/Logs/Agent-20120628-190723116.log)
D3 Agent Errorlog: http://pastebin.com/WbJN2eWj (drive_c/users/Public/Application Data/Battle.net/Agent/Agent.1040/Logs/AgentErrors-20120628-190723116.log)

I hope I didn't forget any important information and hope someone is able to help. :)
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Post by dimesio »

deki
Level 1
Level 1
Posts: 5
Joined: Thu Jun 28, 2012 12:19 pm

Post by deki »

I don't think that it's one of those bugs.
I tried the proposed solution with setarch and it didn't help. (I also have no yama or compositing enabled).

However I discovered that the error dialog does NOT show, when I append the "-locale enGB" parameter, but this still doesn't start the game, it just doesn't show the dialog.
Amathorian
Level 1
Level 1
Posts: 5
Joined: Wed Jun 27, 2012 5:34 pm

Post by Amathorian »

try renaming your current wineprefix to .wine-old and run winecfg again, after it installs Mono and Geko again, set it to Windows 7, then do winetricks vcrun2008 vcrun2010 vcrun d3dx9_36 d3dx9_39 then copy/paste Diablo III from your old wineprefix into your new one.

If that still doesnt work;
try self compiling wine 1.5.7 and start over, you can just rename your old wineprefix and let 1.5.7 create its own, then copy/paste your Diablo III installation from there, then do winetricks vcrun2008 vcrun2010 d3dx9_36 d3dx9_39

im currently running kernel 3.4.3 with wine 1.5.7 winetricks vcrun2005 vcrun2008 vcrun2010 d3dx9_36 d3dx9_39 dotnet11 dotnet40

on Fedora 17, and Diablo 3 plays just fine on it.
deki
Level 1
Level 1
Posts: 5
Joined: Thu Jun 28, 2012 12:19 pm

Post by deki »

Thanks for your reply.

I tested it again with a new prefix, set to Windows 7, installed the packages you suggested and moved the old D3 directory into the new prefix.
But it still won't run.

I haven't tested yet compiling wine myself because of the effort. I'll wait until it is packaged and then try again with it, though I doubt that this version will change anything, as many other users were able to get it to run with older wine versions.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Re: Diablo 3 not starting (error reporting dialog)

Post by dimesio »

deki wrote:radeon driver 2.4.33 and Mesa 8.0.3, ATI Radeon HD4850).
Try the proprietary driver.
deki
Level 1
Level 1
Posts: 5
Joined: Thu Jun 28, 2012 12:19 pm

Post by deki »

Unfortunately the proprietary driver no longer supports my card for the currect Xorg/kernel versions.
And it also doesn't seem to be a driver problem, as others are successfully running it with an open driver.
deki
Level 1
Level 1
Posts: 5
Joined: Thu Jun 28, 2012 12:19 pm

Post by deki »

Interesting, it is running now after setting the Windows version to XP and reinstalling vcrun2008.
Was not able to get it to run with Windows 7.
User avatar
dimesio
Moderator
Moderator
Posts: 13367
Joined: Tue Mar 25, 2008 10:30 pm

Post by dimesio »

deki wrote:Interesting, it is running now after setting the Windows version to XP and reinstalling vcrun2008.
Was not able to get it to run with Windows 7.
The default is still XP because that's what works for most apps. You shouldn't change it unless you know for sure the app needs a different version.
Locked