Game does not run when Battle.net is already running
Closed this issue · 4 comments
Hi,
First of all, thank you very much for your work.
However I wanted to talk to you about a problem that I suffered recently (and on the PC of my wife too). Since the last Battle.net update (1.10.1.9799), when Battle.net is already running (minimized as a tray icon) and when you double click on the shortcut created from Steam (Characteristic of the shortcut: Name: Overwatch / Target: "D:\My Games\Steam\BnetLauncher.exe" / Start In: "D:\My Games\Steam" / Launch Option: OW) the game does not run, the only way to unlock the process is to double click on the Battle.net tray icon, and the game is launched automatically (with Steam overlay).
Here is log when double click on the shortcut created from Steam :
[2018-02-10 13:06:46.6149]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2018-02-10 13:06:46.6199]: Environment: Microsoft Windows NT 10.0.16299.0 (4.0.30319.42000), 64bit
[2018-02-10 13:06:46.6209]: Getting Machine details:
[2018-02-10 13:06:46.6780]: OS: Microsoft Windows 10 Professionnel (10.0.16299, 64 bits, 1036)
[2018-02-10 13:06:46.6780]: CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz; RAM: 16384MB
[2018-02-10 13:06:46.6790]: GPU: NVIDIA GeForce GTX 980 (4095MB, 23.21.13.9077)
[2018-02-10 13:06:46.6790]: HDD: Corsair Force GS, ST2000DX001-1CM164, Generic STORAGE DEVICE USB Device
[2018-02-10 13:06:46.6810]: battlenet URI handler appears to present and correct
[2018-02-10 13:06:46.6810]: Checking for other bnetlauncher processes
[2018-02-10 13:06:46.6840]: No other bnetlauncher detected
[2018-02-10 13:06:46.6850]: Given parameter: OW
[2018-02-10 13:06:46.6850]: Known key for game 'Overwatch'
[2018-02-10 13:08:46.7631]: not enough battle.net Helpers started.
[2018-02-10 13:08:46.7631]: Couldn't find the battle.net running and failed to start it. Exiting
Here is log when double click on the shortcut created from Steam AND double click on the Battle.net tray icon :
[2018-02-10 13:50:22.0696]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2018-02-10 13:50:22.0746]: Environment: Microsoft Windows NT 10.0.16299.0 (4.0.30319.42000), 64bit
[2018-02-10 13:50:22.0746]: Getting Machine details:
[2018-02-10 13:50:22.1308]: OS: Microsoft Windows 10 Professionnel (10.0.16299, 64 bits, 1036)
[2018-02-10 13:50:22.1308]: CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz; RAM: 16384MB
[2018-02-10 13:50:22.1308]: GPU: NVIDIA GeForce GTX 980 (4095MB, 23.21.13.9077)
[2018-02-10 13:50:22.1318]: HDD: Corsair Force GS, ST2000DX001-1CM164, Generic STORAGE DEVICE USB Device
[2018-02-10 13:50:22.1328]: battlenet URI handler appears to present and correct
[2018-02-10 13:50:22.1328]: Checking for other bnetlauncher processes
[2018-02-10 13:50:22.1358]: No other bnetlauncher detected
[2018-02-10 13:50:22.1358]: Given parameter: OW
[2018-02-10 13:50:22.1368]: Known key for game 'Overwatch'
[2018-02-10 13:50:32.8160]: battle.net client is fully running with pid = 8652
[2018-02-10 13:50:32.8160]: Issuing game launch command 'Pro' at '01:50:32.8160'
[2018-02-10 13:50:32.9314]: Searching for new battle.net child processes for the game
[2018-02-10 13:50:32.9804]: No child process found.
[2018-02-10 13:50:33.5231]: Found battle.net child process started at '01:50:33.3479' with pid = 8508
[2018-02-10 13:50:33.5241]: Selecting battle.net child started at '01:50:33.3479' with pid = 8508
[2018-02-10 13:50:34.0259]: Attempt 1 to find start parameters
[2018-02-10 13:50:34.1416]: Filename = C:\Program Files (x86)\Battle.net\Overwatch\Overwatch.exe
[2018-02-10 13:50:34.1421]: Arguments = -uid prometheus Pro://
[2018-02-10 13:50:34.1421]: Closing battle.net child game process and starting it under bnetlauncher
[2018-02-10 13:50:34.1913]: Exiting
The problem does not occur when Battle.net is not already running.
By launching the game via the command battlenet://Pro, the game starts without problems (without Steam overlay of course)
Thank you in advance.
Note: If it can help you, on my PC the PID of:
Battle.net.exe: 8652
Battle.net Helper.exe: 1588
Hum, I see what's going on.
bnetlauncher users the battle.net client helper processes to know if it's fully started or not, before the client would have two running and keep them open but now seems behavior has changed to close one of them when the launcher has no window open.
I'll try to update bnetlauncher to account for this new behavior.
Has a temporary fix you might be able to work around it by disabling hardware acceleration in the battle.net client options (bottom of general).
Could you also try the unreleased 1,19 version to see if it exhibits the same issues? https://madalien.com/pub/bnetlauncher/bnetlauncher_v119.zip
Thank you for this quick response,
It's perfect with 1.19 version ! It works as before, thank you very much 👍