| ulkesh |
Wednesday 1 January 2014 at 2:12
|
ulkesh
|
I downloaded the latest Diablo III installer file from Blizzard's website and ran the Diablo III PlayOnLinux installer. It proceeded to install and set up the Battle.Net beta launcher program. It then proceeded to install Diablo III and the full application was downloaded as expected (meaning, it went from Installing to Playable to Optimal in the launcher).
When clicking "Play", Diablo III never actually launches. I get no visible errors. The "Play" button simply goes to "Launching" then "Playing Now", then it just goes back to "Play" with no Diablo 3 running.
Here are my specs: Distro: Linux Mint 16 "Olivia" KDE Edition Wine version: 1.5.5-DiabloIII_v3 Desktop: KDE Errors: None that arise
Computer configuration: Intel Core i7 3.4GHz 16 GB RAM AMD Radeon HD 7970
Any help is very appreciated!
Thanks in advance. |
| booman |
Thursday 2 January 2014 at 13:30
|
booman
|
When you launch Diablo III or Battle.Net click "debug" instead of Run Then you will see a debug output That will show you any errors the game is getting. Are you using 64-bit Mint 16? Can you run any other games in Linux?
|
| ulkesh |
Thursday 2 January 2014 at 15:16
|
ulkesh
|
When you launch Diablo III or Battle.Net click "debug" instead of Run
Then you will see a debug output
That will show you any errors the game is getting.
Are you using 64-bit Mint 16?
Can you run any other games in Linux?
I will try the debug option asap.
Yes, I'm using 64-bit Mint 16. Yes, I'm able to run every game I've tried in Steam (at least 10). Please note that I'm able to run World of Warcraft via PoL and Starcraft II. Basically I do not have the original launcher for Diablo III which used to work fine in the past. This mainly has to do with using the Battle.Net launcher which works fine for the Hearthstone Beta, just not Diablo III. |
| ulkesh |
Thursday 2 January 2014 at 15:30
|
ulkesh
|
When you launch Diablo III or Battle.Net click "debug" instead of Run
Then you will see a debug output
That will show you any errors the game is getting.
Booman, I ran with debug turned on and tried to launch Diablo III via the Battle.Net launcher three times. Each time the following showed in the log:
D 14:23:53.604129 [InstallManager] {Main} Game is running: diablo3 D 14:23:53.604193 [ProductState] {Main} InstallState (diablo3): gameRunning=1 GameLaunching=0 err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files\\Diablo III\\Diablo III.exe" failed, status c0000135 D 14:23:58.854316 [InstallInfo] {Main} Operation status changed: opType=Execute oldStatus=On newStatus=Off agentUid=diablo3_enus D 14:23:58.854455 [InstallManager] {Main} Game is no longer running: diablo3 D 14:23:58.855013 [ProductState] {Main} InstallState (diablo3): gameRunning=0
Notice the "err:module:LdrInitializeThunk Main exe". Any idea on what that might mean? |
| ulkesh |
Thursday 2 January 2014 at 15:35
|
ulkesh
|
Oh, well, I just saw this in the log as well:
err:module:import_dll Library dbghelp.dll (which is needed by L"C:\\Program Files\\Diablo III\\Diablo III.exe") not found
I turned dbghelp to disabled so the Battle.Net launcher would run (based on other threads in these forums). Seems I'm in a catch-22 situation. I'll re-enable it to see if Battle.Net will launch or still error.
|
| ulkesh |
Thursday 2 January 2014 at 15:53
|
ulkesh
|
So after removing the override for dbghelp, I was able to attempt a launch of Diablo III. However, the graphics never really displayed correctly. I saw the startup movie attempt to load, but never did, then I ESC'd out of that to only see the D3 Arrow cursor on the screen and nothing else. Required a hard reboot to get back to the desktop (even killing the process didn't work, instead that simply messed up the video and shown a bunch of colored pixels near the top of the screen).
I will continue to try and will post back as I make progress. Any further help is certainly appreciated! I will continue to debug as well in case it shows why the graphics aren't working properly.
|
| booman |
Thursday 2 January 2014 at 17:03
|
booman
|
Ah you are getting somewhere. Yes keep trying. Since you have an AMD video card, I suggest checking drivers. I have heard that new drivers can break/fix things, so you may have to roll back a version or update. AMD drivers always seems to cause some kind of problem with DirectX and games. I have also seen that dbghelp bug too. Has something to do with wininet and the browser. Its been a problem with League of Legends and Battle.Net
|