Форум

Diablo III won't run with Battle.Net Launcher

Автор Replies
christoph Wednesday 13 August 2014 at 14:29
christophAnonymous

Hello all

I have a working instance of the Battle.net Application, with which I managed to install StarCraft II, Diablo III (Starter Edition) and Hearthstone. I can play Starcraft II fine, but Diablo III won't launch. It seems to be a very similar case to this thread.

Technical details

I'm using Ubuntu 14.04 64-bit. I have a GeForce Ti560 running with the xorg-edge drivers 340.32.

My PlayOnLinux is 4.2.2. I installed the Battle.net App in a 32-bit drive (otherwise I couldn't get it to work) and run it with Wine 1.7.22 (23 didn't work). I installed the wininet library, and vcrun2010.

The library overrides are

  • msvcr100 (native,builtin)
  • msvcp100 (native,builtin)
  • wininet (builtin)
  • battle.net (native,builtin)
  • dbghelp (builtin) (was disabled at first, to install stuff)

I can launche the game once I re-enable dbghelp, but it stalls on a black screen with the Diablo III mouse-pointer.

Here are the last lines of the debug log.

 
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:FlashWindowEx 0x33cf10
fixme:win:FlashWindowEx 0x33d370
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0x200a2
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x15f5b88): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
[08/13/14 14:25:16] - Running wine-1.7.22 winecfg (Working directory : /usr/share/playonlinux/python)

 

Since I've no experience with PoL & Co., any help would be much appreciated.

christoph Wednesday 13 August 2014 at 19:02
christophAnonymous

I tried installing winhttp and trying different overrides, at worst the game doesn't launch at all, at best the screen turns grey, then black with the Diablo III mouse pointer. So I removed that again. Also installed FlashPlayer and Flashplayer_Active X, to no effect, so I uninstalled them too.

I was getting some error messages in the debug console regarding OpenGL support, so I manually configured the Direct Draw Renderer to be OpenGL, and the error messages dissapeared. But still no progress in actually launching the game.

In the meantime, StarCraft II doesn't launch anymore, even if I revert back to "default" for the Direct Draw Renderer. Tried with dbghelp both set as "disabled" and "builtin".

Finally, I uninstalled vcrun2010, because I had it just it to try to get Diablo III running. It doesn't seem to change anything at this stage.

Thanks for reading!

 

christoph Thursday 14 August 2014 at 18:12
christophAnonymous

The most peculiar thing happened today. Both StarCraft II and Diablo III launched! (Wine Mono 4.5.2 seems to have appeared magically in the list of uninstallable programs, and Wine Gecko now exists in two versions: 2.21 and 2.24, but I've no idea how that happened.)

I can seamlessly play SCII, DIII crashes at various early stages. I went back to OpenGL as the Direct Draw Renderer, and installed the component "d3dx11", because I was getting some d3d related errors in the console (I'm really not conviced it helped, but...)

My best progress was getting to watch the initial video and choosing a starting characacter. After choosing a name and submitting, I got an error code. I tried to hit "Back", and then the screen went grey. Most of the time it stalls after being authentified by the server (clicking "Cancel" or "Exit" crashes the game graphically, the music continues to play).

From the debug console:

fixme:ntdll:NtLockFile I/O completion on lock not implemented yet

fixme:win:EnumDisplayDevicesW ((null),0,0x33f5f8,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:query_init Unhandled query type 0x11.
fixme:d3d:query_init Unhandled query type 0x12.
fixme:d3d:query_init Unhandled query type 0xe.
fixme:d3d:query_init Unhandled query type 0xd.
fixme:d3d:query_init Unhandled query type 0x6.
fixme:d3d:query_init Unhandled query type 0xf.
fixme:d3d:query_init Unhandled query type 0x5.
fixme:win:EnumDisplayDevicesW ((null),0,0x33f158,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:shell:SetCurrentProcessExplicitAppUserModelID L"BlizzardEntertainment.DiabloIII.retail": stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xfd1e9dc): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:FlashWindowEx 0x33d1e0

Thanks!

 

 

christoph Friday 15 August 2014 at 20:14
christophAnonymous

Okay, this is really weird. Does Play On Linux autoconfigure itself on a trial and error basis? After persistently trying to launch the game like a madman, it finally accepted once, then not again for a few times, and finally long enough to level a character up to Lvl8. Without me changing anything in the configuration.

It regularly freezes after authenticating my account. It also regularly freezes when starting a game, or configuring stuff (when communicating with a battle.net server?) When it freezes, it's pretty hard to get out and kill the process. I've had to reboot the machine a few times. But once it works, everything works beautifully. So, as far as I'm concerned, it's in a satisfying state. Maybe someone else will find this thread useful if experiencing similar problem: cling on, cross your fingers and hope for the best!

Ronin DUSETTE Friday 15 August 2014 at 20:46
Ronin DUSETTE
Admin

No, it does not auto-configure anything in that sense. It sounds like a lib issue on your system. You are for sure having graphics lib or driver issues, but since you didn't post your computer specs, I am just guessing. 

Do you have the proprietary drivers for your graphics card installed, as well as the 32 bit libraries for it? Can you post your FULL computer specs?


Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
christoph Friday 15 August 2014 at 21:58
christophAnonymous

Sorry, I thought the specs given in the first post would be sufficient. What do you mean by FULL computer specs? The complete output of the lshw command? How can I check if the libraries you're asking for are installed?

Ronin DUSETTE Friday 15 August 2014 at 23:04
Ronin DUSETTE
Admin

haha. Oh no. I just meant linux version, architecture, graphics card, etc etc etc.. You are fine. :) Let me take a look real quick. 


Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
Ronin DUSETTE Friday 15 August 2014 at 23:19
Ronin DUSETTE
Admin

So, do this:

delete the virtual drive that you have that stuff in. Diable III, according to our install script, only needs vcrun2008 and wine 1.7.15. 

 

"I can seamlessly play SCII, DIII crashes at various early stages. I went back to OpenGL as the Direct Draw Renderer, and installed the component "d3dx11", because I was getting some d3d related errors in the console (I'm really not conviced it helped, but...)"

 

You really never have to change the direct draw renderer. It defaults to OpenGL anyway. Also, don't install d3dx11. It is not needed, plus windows XP (which is what Wine defaults to) only got directx 9, so you will rarely need to install that. Wine, for the most part, does a great job with its builtin stuff, but sometimes you would need it. 

But yeah, It seems that these different games have different requirements, so you will need to install each game in its own folder, even if you have to install battle.net in multiple installs. 

Try to install Diablo III using the Install function in PlayOnLinux, into its own virtual drive. If that works, then you just need to make sure that the drive with battle.net is running what diablo requires, which is just 32 bit virtual drive, vcrun2008, and wine 1.7.15. Do that and post up here. 


Please:
Post debug logs & full computer specs in first post
No private messages for general help, use the forums
Read the wiki, Report broken scripts
christoph Saturday 16 August 2014 at 19:07
christophAnonymous

Hello there

All right, thanks for the explanations. Indeed, following your advice, it seems to be working like a charm now. Thank you very much!

Вы находитесь здесь: Index > PlayOnLinux > Diablo III won't run with Battle.Net Launcher