dafzor / bnetlauncher Goto Github PK

View Code? Open in Web Editor NEW

226.0 11.0 27.0 451 KB

Launcher utility to help start battle.net games with the steam overlay.

Home Page: http://madalien.com/stuff/bnetlauncher/

License: GNU General Public License v3.0

C# 99.90% Batchfile 0.10%

steam-overlay steam battle-net utility launcher launcher-utility

bnetlauncher's People

Contributors

Stargazers

Watchers

bnetlauncher's Issues

WoW Shadowlands and Classic can not enter

Hi,

Updating my main post with latest findings.

Last 1 year i am playing only wow classic using bnetlauncher_v208 without any issues and WoW Shadowlands pre-patch with bnetlauncher_v208 without any issues. After Shadowlands release few days ago i am experiencing following issues.

1.When i use bnetlauncher_v211 to open WoW Classic after loading of bnetlauncher it is instantly giving me error showed on this picture https://ibb.co/1qP7GHt , then it is giving me game not found error https://ibb.co/6tZKJBP
2. When i use bnetlauncher_v211 to open WoW Shadowlands it is giving me game not found error showed on this video. https://youtu.be/wxbw6X05J7s
3. When i use bnetlauncher_v208 to open WoW Classic it is working as intended
4. When i use bnetlauncher_v208 to open WoW Shadowlands it is same behvior as point 2 showing game not found error https://ibb.co/6tZKJBP

If the bnet launcher is loaded minimized in system tray before i start bnetlauncher_v211
5. When i use bnetlauncher_v211 to open WoW Classic it is giving me same errors like in point 1.
6. When i use bnetlauncher_v211 to open WoW Shadowlands it is working, but not closing bnetlauncher, minimizing it in system tray.
If the bnet launcher is loaded minimized in system tray before i start bnetlauncher_v208
7. When i use bnetlauncher_v208 to open WoW Classic it is working, but not closing bnetlauncher, minimizing it in system tray.
8. When i use bnetlauncher_v208 to open WoW Shadowlandsit is working, but not closing bnetlauncher, minimizing it in system tray.

For now i can use your launcher only if i preload bnet launcher on windows startup and stay on background which is unnecessary recourse lock. Also if i play only WoW Classic i can use bnetlauncher_v208.

Can't launch CoD:MW with overlay anymore

Any way to fix this?
Everything worked "perfectly" through normal "battlenet" shortcut and renaming it til today's update.

Add support for SoM version of Classic WOW

Hello,

Regarding issue #37 and my research for the main issue in #56, there is workaround i worked with until SoM came out. Basically i made .bat file where it opens battle.net for part of the second on my screen, then wait a bit and use your launcher to open game. Main issue was that if battle.net launcher is minimized or not visible on main screen you launcher is not opening ClassicWoW, but only giving error.

Now when SoM is released your launcher is automatically launching Classic TBC by default, could you please integrate and Classic SoM version of the game so i can still use it.

If youre interested in the workaround maybe it could be implemented as a function in your launcher. It must show battle.net just for part of the second on the screen and then your launcher works.
@echo off start E:\Launchers\Battle.net\Battle.net\Battle.net.exe TIMEOUT 4 start /D "E:\World of Warcraft" Wow.exe

Where Wow.exe is your launcher.

Best Regards.

bnetlauncher able to find battle.net launcher, won't start game.

I assume this is a problem after the process has transferred to Blizzard's launcher but I don't know where else to ask. Hopefully you can help me :)


[2018-01-08 08:29:31.9957]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2018-01-08 08:29:32.0047]: Environment: Microsoft Windows NT 10.0.16299.0 (4.0.30319.42000), 64bit
[2018-01-08 08:29:32.0092]: Getting Machine details:
[2018-01-08 08:29:32.1288]: OS: Microsoft Windows 10 Home (10.0.16299, 64-bit, 1033)
[2018-01-08 08:29:32.1423]: CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz; RAM: 16384MB
[2018-01-08 08:29:32.1488]: GPU: Intel(R) HD Graphics 4600 (1024MB, 20.19.15.4835)
[2018-01-08 08:29:32.1533]: HDD: SSD2SC120G1CS1754D117-483, WDC WD10EZEX-00BN5A0
[2018-01-08 08:29:32.1603]: battlenet URI handler appears to present and correct
[2018-01-08 08:29:32.1703]: Checking for other bnetlauncher processes
[2018-01-08 08:29:32.1828]: No other bnetlauncher detected
[2018-01-08 08:29:32.1878]: Given parameter: ow
[2018-01-08 08:29:32.1918]: Known key for game 'Overwatch'
[2018-01-08 08:29:32.4491]: battle.net client is fully running with pid = 57048
[2018-01-08 08:29:32.4521]: Issuing game launch command 'Pro' at '08:29:32.4521'
[2018-01-08 08:29:32.4736]: System.ComponentModel.Win32Exception (0x80004005): Application not found
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at bnetlauncher.Program.BnetStartProcess(String bnet_command)
[2018-01-08 08:29:34.1241]: Searching for new battle.net child processes for the game
[2018-01-08 08:29:34.2943]: No child process found.
[2018-01-08 08:29:34.9474]: No child process found.
[2018-01-08 08:29:35.5896]: No child process found.

Not working as intended with Black Ops 4

Whenever I set-up BO4 to run through Steam the game will launch just like all of my other Battle.net games do, but a few seconds after launch I'm getting the error message "Error: Error Game Not Found", with the splash text that the bnetlauncher will be closing. The game itself stays open and launches perfectly, but loses all overlay functionality. Any idea what could be causing this? Running the latest version (1.22.6790.25902).

StarCraft Remastered Support

Howdy,

With some testing on my own, the battlenet://SCR argument launches Battle.net App to the StarCraft Remastered screen. However I don't own the game, so I can't confirm this works with the actual game.

Thanks for the tool and your support.

BUG: Game updates cause error dialog

First,
Great little tool works well as a launcher proxy.

Second,
When I launched BOPS4 today the battle.net wasn't open so this program launched it great! However the game needed updates which it then proceeded to download 4GB worth and install them. However this program didn't seem to be aware the game was updating and instead gave me the following error:

Perhaps it would be possible to check if the game updater process/exe is running and wait?

BUG - Mutes All Sound Devices When Using To Launch Any Game

So I tried this app and it works great, the only problem is it mutes all sound on my pc and then I can't enjoy the game because I can't hear anything. My setup is on window10 I use a Bluetooth speaker and headset for sound, neither work. After launching a game with the bnetlauncher I am presented with my game with all system sounds muted. Upon closing the game all system sounds return to normal.

Won't work with Microsoft SRP anymore. [x64 WIN 10]

Essentially, this used to work when Microsoft SRP was enabled and configured accordingly but for some reason - it's no longer the case. Interestingly, as soon as SRP is disabled the client works as per-normal.

I've attached the logs if that helps with future development. Also, would it be possible to provide any details on what and where the client is creating new files/folders etc. since this is usually what SRP is restricting.

Can't run Destiny 2 over steam in-home streaming

Hello, I can't seem to get this to work with Destiny 2 and steam in-home streaming. I've got the exe in the D2 program files folder, my steam shortcut is pointed to the exe with "dst2" as a parameter. It seems to launch the game correctly on the host, but on the client it sits on the battle.net launcher (though this becomes non-responsive, in the sense that I can't click anything and mousing over the battlenet UI doesn't do any of the animations one would expect) for a bit, then closes altogether (furthermore, I can hear the D2 audio until the steam window closes). After this, the host is still running D2, it just seems that steam is losing the streaming connection for some reason.

Is bnetlauncher known to work well with steam in-home streaming? Is there something I've missed? I enabled the debug logs, and didn't notice anything amiss there -- it gets to "Closing battle.net child game process and starting it under bnetlauncher" and "Waiting for destiny 2 to exit", and nothing else until "Exiting".

[2017-10-25 02:59:24.4486]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2017-10-25 02:59:24.4557]: Environment: Microsoft Windows NT 10.0.14393.0 (4.0.30319.42000), 64bit
[2017-10-25 02:59:24.4577]: Getting Machine details:
[2017-10-25 02:59:24.6870]: OS: Microsoft Windows 10 Home Single Language (10.0.14393, 64-bit, 1033)
[2017-10-25 02:59:24.6900]: CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz; RAM: 16384MB
[2017-10-25 02:59:24.6930]: GPU: NVIDIA GeForce GTX 980 Ti (4095MB, 23.21.13.8800)
[2017-10-25 02:59:24.6950]: HDD: ST4000LM024-2AN17V, Samsung SSD 850 EVO M.2 500GB
[2017-10-25 02:59:24.6990]: battlenet URI handler appears to present and correct
[2017-10-25 02:59:24.7020]: Checking for other bnetlauncher processes
[2017-10-25 02:59:24.7040]: No other bnetlauncher detected
[2017-10-25 02:59:24.7070]: Given parameter: dst2
[2017-10-25 02:59:24.7091]: Known key for game 'Destiny 2'
[2017-10-25 02:59:24.7369]: battle.net client not running, trying to start it
[2017-10-25 02:59:33.4791]: battle.net client is fully running with pid = 9756
[2017-10-25 02:59:33.4826]: Issuing game launch command 'DST2' at '02:59:33.4821'
[2017-10-25 02:59:33.5212]: Searching for new battle.net child processes for the game
[2017-10-25 02:59:33.5829]: No child process found.
[2017-10-25 02:59:34.1406]: Found battle.net child process started at '02:59:33.7253' with pid = 11544
[2017-10-25 02:59:34.1436]: Selecting battle.net child started at '02:59:33.7253' with pid = 11544
[2017-10-25 02:59:34.6480]: Attempt 1 to find start parameters
[2017-10-25 02:59:34.7794]: Filename = C:\Program Files (x86)\Destiny 2\destiny2.exe
[2017-10-25 02:59:34.7823]: Arguments =  -uid destiny2 DST2://
[2017-10-25 02:59:34.7849]: Closing battle.net child game process and starting it under bnetlauncher
[2017-10-25 02:59:34.8269]: Closing battle.net client.
[2017-10-25 02:59:34.8991]: Waiting for destiny 2 to exit
[2017-10-25 03:00:21.7298]: Exiting

Any help would be greatly appreciated! :)

Cannot launch warzone with bnetlauncher.

Launching cold war works fine, but warzone does not launch unless I manually click play in battle.net. I can switch to warzone from bocw but that is slow and requires more loading.

Log: (Looks fine)

*Excuse the horrible video quality but there is a 10 mb size limit

2021-08-13.16-53-54.mp4

Enhancement: Allow manual opening of games

What I mean by that is: if you don't input any shortcuts (ow, wow etc.) it will just open battle.net and whatever game is manually selected afterwards.
I know this is possible from a bug, actually. Older versions of bnetlauncher would let you do this unintentionally. This is useful (at least from what I can use) to open Overwatch PTR through steam, letting me fully use the steam controller without fiddling with other programs.

Though I use the hacky way to do it (just using an old version)

Crash Bandicoot 4 doesn't launch.

With version 2.14, trying to start a game with the "bnetlauncher.exe cb4" command only opens the battle.net window, it doesn't select the correct game and doesn't start anything, I need to go to the correct tab and click on the play button after that overlay works fine.

I tried sending some commands directly:
"Battle.net.exe --game=wlby" opens the correct game tab, just doesn't start the game (as expected)
"Battle.net.exe --exec=wlby" doesn't work

Battle.net Beta client - URL scheme shortcuts not working

Hello,

Most URLs to launch games are not working on the current Battle.net Beta client. I don't know if this is a temporary issue or if the correct URLs have changed.

Here's the list that I have tested:

battlenet://WoW - not working
battlenet://D3 - not working
battlenet://WTCG - not working
battlenet://Pro - not working
battlenet://S2 - not working (but battlenet://starcraft works to start Starcraft 2)
battlenet://Hero - not working (but battlenet://heroes works to start HotS)
battlenet://SCR - not working
battlenet://DST2 - can't test

I realize that the Battle.net Beta client is in Beta for a reason and maybe it's a problem on their end, but I figured I'd open an issue to let you know and keep this in mind.

Also, I don't know how to find these URLs other than trial-and-error. If there's a better way to find these, I'd love to know.

Add support for Blizzard Arcade Collection

Would it be possible to add support for the Blizzard Arcade Collection?

I have been trying to guess the magic codes to start the game, but no luck up to now.

Game does not run when Battle.net is already running

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

Destiny 2 doesn't start if BNET App is not open

Blizz App starts, but Destiny 2 doesn't launch giving me "game not found" error. When I try again with App open, it launches the game. Even time limit 120 doesn't help. Launching as Admin doesn't work either.

BlizzApp was not launched in this log:

00:54:01.9656|14620|Program.Main:125|INFO|Starting bnetlauncher v2.0.6867.22474
00:54:01.9676|14620|Program.LogSystemInfo:684|INFO|Getting System details:
00:54:01.9686|14620|Program.LogSystemInfo:688|INFO|ENV: Microsoft Windows NT 10.0.17763.0 (4.0.30319.42000), 64bit
00:54:02.0324|14620|Program.LogSystemInfo:754|INFO|OS: Microsoft Windows 10 Home (10.0.17763, 64-bit, 1033)
00:54:02.0334|14620|Program.LogSystemInfo:755|INFO|CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, RAM: 16384MB
00:54:02.0344|14620|Program.LogSystemInfo:756|INFO|GPU: Intel(R) HD Graphics 530 (21.20.16.4550, 1024MB)
00:54:02.0354|14620|Program.LogSystemInfo:757|INFO|HDD: HGST HTS721010A9E630
00:54:02.0374|14620|Program.LoadGameList:549|INFO|Loading gamedb files.
00:54:02.0514|14620|Program.LoadGameList:570|INFO|Loaded internal gamedb with '9' games.
00:54:02.0523|14620|Program.LoadGameList:587|INFO|Known games: '9'.
00:54:02.0523|14620|Program.Main:182|INFO|Changing timeout to '120'.
00:54:02.0533|14620|Program.Main:213|INFO|Given parameter 'dst2'.
00:54:02.0543|14620|Program.Main:249|INFO|Using 'battlenet' client.
00:54:02.0564|14620|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
00:54:02.0574|14620|Program.Main:265|INFO|Checking for other bnetlauncher processes using same client
00:54:02.0583|14620|Program.Main:273|INFO|No other bnetlauncher detected
00:54:02.1606|14620|Program.Main:316|INFO|Client already running with pid:'13132'.
00:54:02.1616|14620|Program.Main:328|INFO|Issuing game launch command 'DST2' at '12:54:02.1606'
00:54:02.1626|14620|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
00:54:02.2189|14620|Program.Main:338|INFO|Searching for the game process 'destiny2.exe' for '120' seconds.
00:54:03.2212|14620|Program.Main:350|WARN|Game 'destiny2.exe' not running.
- bunch of repeats of this -
00:56:02.2015|14620|Program.Main:359|ERROR|Game 'dst2' not found within timeout.
00:56:04.6204|14620|Program.ShowMessageAndExit:532|INFO|Exiting.

BlizzApp was launched in this log

00:56:51.2777|15308|Program.Main:125|INFO|Starting bnetlauncher v2.0.6867.22474
00:56:51.2797|15308|Program.LogSystemInfo:684|INFO|Getting System details:
00:56:51.2807|15308|Program.LogSystemInfo:688|INFO|ENV: Microsoft Windows NT 10.0.17763.0 (4.0.30319.42000), 64bit
00:56:51.3455|15308|Program.LogSystemInfo:754|INFO|OS: Microsoft Windows 10 Home (10.0.17763, 64-bit, 1033)
00:56:51.3465|15308|Program.LogSystemInfo:755|INFO|CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, RAM: 16384MB
00:56:51.3465|15308|Program.LogSystemInfo:756|INFO|GPU: Intel(R) HD Graphics 530 (21.20.16.4550, 1024MB)
00:56:51.3475|15308|Program.LogSystemInfo:757|INFO|HDD: HGST HTS721010A9E630
00:56:51.3495|15308|Program.LoadGameList:549|INFO|Loading gamedb files.
00:56:51.3635|15308|Program.LoadGameList:570|INFO|Loaded internal gamedb with '9' games.
00:56:51.3645|15308|Program.LoadGameList:587|INFO|Known games: '9'.
00:56:51.3655|15308|Program.Main:182|INFO|Changing timeout to '120'.
00:56:51.3665|15308|Program.Main:213|INFO|Given parameter 'dst2'.
00:56:51.3665|15308|Program.Main:249|INFO|Using 'battlenet' client.
00:56:51.3684|15308|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
00:56:51.3684|15308|Program.Main:265|INFO|Checking for other bnetlauncher processes using same client
00:56:51.3694|15308|Program.Main:273|INFO|No other bnetlauncher detected
00:56:51.4817|15308|Program.Main:316|INFO|Client already running with pid:'13132'.
00:56:51.4826|15308|Program.Main:328|INFO|Issuing game launch command 'DST2' at '12:56:51.4817'
00:56:51.4836|15308|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
00:56:51.5295|15308|Program.Main:338|INFO|Searching for the game process 'destiny2.exe' for '120' seconds.
00:56:52.0039|15308|Processes.GetProcessByNameAfterDate:150|INFO|Found game process started at '12:56:51.9647' with pid:'13956'
00:56:52.0657|15308|Processes.GetProcessByNameAfterDate:150|INFO|Found game process started at '12:56:51.9647' with pid:'13956'
00:56:52.0678|15308|Processes.GetProcessStartInfoById:85|INFO|Attempt 1 to find start parameters
00:56:52.2054|15308|Processes.GetProcessStartInfoById:123|INFO|Filename:'D:\Games\Destiny 2\destiny2.exe'.
00:56:52.2064|15308|Processes.GetProcessStartInfoById:124|INFO|Arguments:' -uid destiny2'.
00:56:52.2074|15308|Program.Main:386|INFO|Closing game process and starting it under bnetlauncher
00:56:52.2862|15308|Program.Main:446|INFO|Waiting for dst2 process 14172 to exit

Allowing Multiple instances of blizzard launcher breaks functionality

The option needs to be disabled for bnetlauncher to work

Make bnetlauncher controller config compatible

I know this has been brought up elsewhere, but i wonder if changing the Process.Start() method to a blocking command, think its Process.WaitForExit() or somthing like that, it may keep bnetlauncher active and allow for any controller profile assigned within steam to remain active instead of switching back to the desktop configuration.

Warcraft 3 reforged support

Good day,

Battle.net client now supports launching of Warcraft 3: Reforged via
--exec="launch W3" argument.
Requesting an addition into default gamedb.

It also looks like, it should be possible to launch WC3 classic via this after patch 1.30.2 on December 1st.
- Source one and two

WoW Classic not launching

Hello, thank you for this awesome tool! I'm on the new, updated version of Battle.net (1.33.0.12769), bnetlauncher 2.13, and WoW Classic does not launch when I use the wowclassic tag. It opens the launcher and switches the dropdown to WoW Classic, but it doesn't actually click the Play button, I get the standard "Couldn't find World of Warcraft Classic running" error message. Retail works just fine, Overwatch works fine, but WoW Classic doesn't.

Wow classic - Starting but warning popup

Wow Classic changed name of the executable to WowClassic.exe from Wow.exe.
The game starts all fine via battlenet, but the bnetlauncher thinks it never started so a popup with "retry"/"cancel" pops up.

Can't Launch StarCraft: Remastered

I don't think this is an issue with bnetlauncher itself, but I believe the battlenet URI handler changed as this doesn't seem to be working:

battlenet://scr

Can anyone confirm they can launch StarCraft: Remastered using the above run command?

Log for posterity:

[2018-05-28 09:18:41.4386]: battlenet URI handler appears to present and correct
[2018-05-28 09:18:41.4386]: Checking for other bnetlauncher processes
[2018-05-28 09:18:41.4396]: No other bnetlauncher detected
[2018-05-28 09:18:41.4396]: Given parameter: scr
[2018-05-28 09:18:41.4406]: Known key for game 'Starcraft Remastered'
[2018-05-28 09:18:41.4695]: Issuing game launch command 'SCR' at '09:18:41.4695'
[2018-05-28 09:18:41.5892]: Searching for new battle.net child processes for the game
[2018-05-28 09:18:41.6830]: No child process found.
[2018-05-28 09:18:42.2754]: No child process found.
[2018-05-28 09:18:42.8618]: No child process found.
[2018-05-28 09:18:43.4582]: No child process found.
[2018-05-28 09:18:44.0486]: No child process found.
[2018-05-28 09:18:44.6401]: No child process found.
[2018-05-28 09:18:45.2394]: No child process found.
[2018-05-28 09:18:45.8368]: No child process found.
[2018-05-28 09:18:46.4492]: No child process found.
[2018-05-28 09:18:47.0326]: No child process found.
[2018-05-28 09:18:47.6151]: No child process found.
[2018-05-28 09:18:48.2245]: No child process found.
[2018-05-28 09:18:48.8229]: No child process found.
[2018-05-28 09:18:49.4113]: No child process found.
[2018-05-28 09:18:50.0057]: No child process found.
[2018-05-28 09:18:50.6041]: No child process found.
[2018-05-28 09:18:51.1885]: No child process found.
[2018-05-28 09:18:51.7939]: No child process found.
[2018-05-28 09:18:52.3763]: No child process found.
[2018-05-28 09:18:52.9967]: No child process found.
[2018-05-28 09:18:53.5921]: No child process found.
[2018-05-28 09:18:54.1775]: No child process found.
[2018-05-28 09:18:54.7630]: No child process found.
[2018-05-28 09:18:55.3454]: No child process found.
[2018-05-28 09:18:55.9318]: No child process found.
[2018-05-28 09:18:56.5472]: No child process found.
[2018-05-28 09:18:57.0478]: No child process game found, giving up and exiting
[2018-05-28 09:19:00.0693]: exiting with error: Couldn't find a game started trough battle.net Client.
Please check if battle.net did not encounter an error and the game can be launched normally from the battle.net client.
bnetlauncher will now exit.

Question/Suggestion

Hi there,

Thanks a lot for this great software. Some of the issues in wow are related to cache, can i delete somehow cache foulder before opening your launcher ?

Usually before i was using .bat for this purpose - attached code, now i am unable to use it because we are not opening your launcher with regular target path and there must be wowclassic at the end:

rmdir /s /q "E:\World of Warcraft\_classic_\Cache"
START "" "E:\World of Warcraft\_classic_\Wow.exe"

Best Regards

(Intermittent) "Could not find <game> running"; "Retry" doesn't work

Title says it all; I'm getting the following error message:

(I think it happens primarily when the launcher itself was slow to start, such as the first launch after boot)

bnetlauncher_v202.zip
Battle.net is configured to remain signed in, but exit upon game launch
Can provide any other information needed

p.s., this issue aside, I really appreciate this tool. This (90+% of the time) works great to actually show me as in-game properly when I'm playing a Battle‌.net game; it causes such seamless integration with Steam, despite the fact that the [Blizzard] devs clearly couldn't care less about it working. Thanks so much for making this tool.

My bnetlauncher wont start game

hello!
added the bnetlauncher.exe as non steam game with ow parameter but is wont work
my game not in the default folder but i have a symlink: f:\Games\Battle.net\games\Overwatch\ to h:\Battle.net\games\Overwatch
battle.net see the game and i can start from it without steam
i see only this in battle.net:
This folder doesn't contain the correct version of this game. Please check the installation path and try again.
Error Code: BLZBNTAGT00000AF0

and its my log file:
[2017-10-07 23:02:50.2046]: Battle.net Launcher for Steam version 1.18.6465.31319 started
[2017-10-07 23:02:50.2096]: Environment: Microsoft Windows NT 6.1.7601 Service Pack 1 (4.0.30319.42000), 64bit
[2017-10-07 23:02:50.2106]: Getting Machine details:
[2017-10-07 23:02:50.2566]: OS: Microsoft Windows 7 Ultimate (6.1.7601, 64-bit, 1038)
[2017-10-07 23:02:50.2566]: CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz; RAM: 32768MB
[2017-10-07 23:02:50.2576]: GPU: NVIDIA GeForce GTX 660 (2048MB, 22.21.13.8541)
[2017-10-07 23:02:50.2576]: HDD: Samsung SSD 850 PRO 256GB ATA Device, WDC WD1002FAEX-00Y9A0 ATA Device, WDC WD1502FAEX-007BA0 ATA Device, WDC WD1502FAEX-007BA0 ATA Device, WDC WD30EFRX-68EUZN0 ATA Device, WDC WD4003FZEX-00Z4SA0 ATA Device
[2017-10-07 23:02:50.2606]: Exception while trying to retrieve battle.net client path:
[2017-10-07 23:02:50.2626]: System.NullReferenceException: Object reference not set to an instance of an object.
at bnetlauncher.Program.GetBnetClientPath()
[2017-10-07 23:02:51.3316]: Exception while trying to retrieve battle.net client path:
[2017-10-07 23:02:51.3326]: System.NullReferenceException: Object reference not set to an instance of an object.
at bnetlauncher.Program.GetBnetClientPath()
[2017-10-07 23:02:51.3646]: Checking for other bnetlauncher processes
[2017-10-07 23:02:51.3656]: No other bnetlauncher detected
[2017-10-07 23:02:51.3656]: Given parameter: -ow
[2017-10-07 23:02:51.3666]: Known key for game 'Overwatch'
[2017-10-07 23:02:51.5726]: battle.net client is fully running with pid = 9600
[2017-10-07 23:02:51.5736]: Issuing game launch command 'Pro' at '11:02:51.5736'
[2017-10-07 23:02:51.5896]: System.ComponentModel.Win32Exception (0x80004005): Unknown error (0x80041002)
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at bnetlauncher.Program.BnetStartProcess(String bnet_command)
[2017-10-07 23:02:55.5389]: Searching for new battle.net child processes for the game
[2017-10-07 23:02:55.6709]: No child process found.
[2017-10-07 23:02:56.2859]: No child process found.
[2017-10-07 23:02:56.9479]: No child process found.
[2017-10-07 23:02:57.5660]: No child process found.
[2017-10-07 23:02:58.2050]: No child process found.
[2017-10-07 23:02:58.8421]: No child process found.
[2017-10-07 23:02:59.4631]: No child process found.
[2017-10-07 23:03:00.1181]: No child process found.
[2017-10-07 23:03:00.7382]: No child process found.
[2017-10-07 23:03:01.3772]: No child process found.
[2017-10-07 23:03:02.0002]: No child process found.
[2017-10-07 23:03:02.6303]: No child process found.
[2017-10-07 23:03:03.2413]: No child process found.
[2017-10-07 23:03:03.8713]: No child process found.
[2017-10-07 23:03:04.5184]: No child process found.
[2017-10-07 23:03:05.1694]: No child process found.
[2017-10-07 23:03:05.8065]: No child process found.
[2017-10-07 23:03:06.4185]: No child process found.
[2017-10-07 23:03:06.9185]: No child process game found, giving up and exiting

Always exits Blizzard client

I'm running into an issue where, every time I launch Overwatch through bnetlauncher, even though Battle.net is already running in the background, it exits after I quit the game. However, it does not do this if I launch the game without bnetlauncher.

Looking at the code, it seems it's only supposed to exit the client if it wasn't already started, so I'm not positive what could be happening. Has anyone else seen this behavior?

Battle.net Client beta breaks capability to launch alternate versions of games

The latest beta of the Battle.net client breaks both methods bnetlauncher was using to start blizzard games:

~~The --exec parameter no longer launches the game.~~
Pressing enter on Battle.net client no longer defaults to the play action.

Not being able to use Enter key breaks the launch of ptr and WoW Classic versions of the game.

Error: Error: Game not found

Bnetlauncher is set to ow (launching overwatch) It's been working fine, until today. It pops up an error:

It says to check if battle.net can launch the game normally, which is the case.

Overwatch is started without any arguments

I followed your instructions, but haven't succeded in starting Overwatch with Steam overlay. The app always ends on this line

Failed to obtain game parameters. Game should start but steam overlay won't be attached to it.

I made a quick test

Process.Start(owLauncher);
var start = DateTime.Now;
Process owp = null;
while ((DateTime.Now - start).Seconds < 30) {
    owp = Process.GetProcesses().FirstOrDefault(x => x.ProcessName == "Overwatch");
    if (owp != null) break;
    Thread.Sleep(500);
}
if (owp == null) {
    Console.WriteLine("Overwatch process search timeout");
    return;
}
Console.WriteLine($"Info found:\nFileName: {owp.StartInfo.FileName}\nArguments: {owp.StartInfo.Arguments}");

Output (after I manually start Overwatch in Battle.Net):

ProcessInfo found:
FileName:
Arguments:

FileName and Arguments are always empty. It may be a recent change in Battle.Net/Overwatch.

Launch WoW Classic

Will bnetlauncher support launching WoW Classic in a way or this falls under "launching a PTR version" dropdown that is not supported via command line?

I couldn't find anything regarding what would be the b.net code for WoW Classic (like "VIPR" for Black Ops 4).

Attached snip shows the dropdown for both Retail and Classic.

Add support for Call of Duty: Vanguard

Need launch support for call of duty vanguard
shortcut code --exec="launch FORE"

WoW Classic TBC

Classic TBC can not be opened, tested with the latest 2.15exp

Can't load SC2 after recent Bnet launcher update

I get the following error when trying to run SC2 from steam via bnetlauncher.

I had an older version of bnetlauncher (1.22?) and it stopped working after I updated Battle.net, so I updated to the latest version. I can't get SC2 to run since then.

Relevant versions:
Steam: 1550534751 (Feb 18th 2019)
Battle.net: 1.12.9.10979
Bnetlauncher: 2.0.2 (Current version)

EDIT: NVM reboot solved issue.

Configurable timeout?

Hello. bnetlauncher is wonderful, but with my PC, bnetlauncher took about 45 seconds to start the game from Battlenet.
In other words, bnetlauncher times out and can not find the game.
Perhaps, this problem will not be common.
However, I would be happy if I could specify the timeout time on the command line.

-nolaunch Doesn't Seem to Work

I have multiple WoW accounts and am trying to set this up to give me a moment to switch between accounts prior to launch. When I run the following, the game will launch right after the client opens. I've also tried modifying the gamesdb.ini to add the option in there and I'm getting the same result.

bnetlauncher.exe wowclassic -nolaunch

New bnet app update broke

Fatal Error

Couldn't find the battle.net running and failed to start it. Exiting application.

Currently running on version 1.8.5.9062 (Beta) (been on beta the whole time and it worked)

Cannot add a new value to the INI for Black Ops Cold War

I added a new value at the bottom the file for Cold War and it wont launch

Launch PTR

Are there parameters to launch PTRs? I would like to run the Overwatch PTR through steam.

Thanks for all your work!

Any idea why Overwatch is "Pro"?

Just wondering if you had any insight to this. I can't seem to find anything by Googling. It's the only battlenet URI launch key that seems out of place.

CoD: MW 2019 not launching properly

After the season 3 update, the executable apparently starts the game, even showing playing on the battlenet launcher, but seconds later without actually opening the game, it terminates the process without starting.
I tried to run with timeout but without success.
All other games work normally.
I collected the logs but I don't know if it was a change in the game, or in the battlenet.

debug_20210720.log

cold war issue

cant seem to launch cold war using this '"C:\Users\Andrew\Downloads\bnetlauncher_v213\bnetlauncher.exe" codbocw -t 10' is how i have it set up right now whenever i launch the game the overlay doesnt activate

CoD MW2: CR

I'm not seeing, in the Read Me documentation for v2.09, that Call of Duty: Modern Warfare 2 Campaign Remastered is supported.

Will this be added at some point?

Release EXE files on GitHub

Call of Duty Warzone missing.

Hello,

There is no shortcut for Call of Duty Warzone.

Best Regards.

Call of Duty: Modern Warfare

Good morning,

new year, new CoD game added to Battle.net
launch argument looks something like this:

Q:\Games\Battle.net\Battle.net.exe --exec="launch ODIN"

However I have still no idea what executable name they'll use.
Also, if I may, I'd like to suggest launch argument to be bnetlauncher.exe codmw2019 as we have no idea how more stupid naming scheme they'll use in future.

bnetlauncher crash

Setup in steam, D3 for the shortcut launch options.

Immediately crashes, Diablo 3 doesn't launch.

Log file attached.

debug_20170522_1608328301.log.txt

The errors thrown in the event viewer:

dotNetRuntime.txt

Application Error.txt

Any other info I can provide to help out?

Destiny 2 Support

If you open the game through steam while the battle.net app is opened, you will lose the In-game status when bnetlauncher exits. However, the status is retained properly if you launch the game through steam with the battle.net app initially closed.

Logs;

Showing ingame status properly;
https://pastebin.com/jCrD6yFf

Ingame status lost;
https://pastebin.com/1Dvmw8eX

In both cases, the ingame overlay is working properly ingame. Just the status message on steam is cleared out.

Battle.net update broke this

Battle.net auto-updated to Build 10202 on 2018/06/22 and since then I haven't been able to make bnetlauncher work with Overwatch. I don't have any other Battle.net games installed so I'm not sure if it's actually affected any other games.
I'm runninng the latest version of bnetlauncher, I was running an older version, but updated when I ahd this problem and the problem is still occuring. I've attached the debug log below.

debug_20180624_1245058048.log

Codmw2019 command prompt

When I open up cod, it loads up correctly and fast. But the command prompt does not go away until I close the game.

This does not happen with ow or wow.

dafzor / bnetlauncher Goto Github PK

bnetlauncher's People

Contributors

Stargazers

Watchers

Forkers

bnetlauncher's Issues

Recommend Projects

Recommend Topics

Recommend Org