Not Launching Overwatch 2

juliocoliveira commented 2 years ago

Not launching Overwatch 2 correctly, It opens the process but it keep stuck with low cpu and ram usage, The window does not open. db: [ow2] name=Overwatch 2 client=battlenet2 cmd=pro exe=Overwatch.exe

dafzor commented 2 years ago

Just tested and it seems to be working normally without changing anything. Was yours a new install or a converted overwatch 1 install?

juliocoliveira commented 2 years ago

To me it launches but only opens after 1 minute, If I launch by the battle.net it opens in the same time. Converted overwatch 1. Tried removing the db and launching by ow param, but it does the same thing.

juliocoliveira commented 2 years ago

Did a repair too, but the same issue still happen

dafzor commented 2 years ago

What's your battle.net launcher version?

juliocoliveira commented 2 years ago

dafzor commented 2 years ago

Still can't reproduce, follow the troubleshoot steps and post the log and i'll try to take a look.

juliocoliveira commented 2 years ago

dafzor commented 2 years ago

Realised you're using your custom ow2 profile instead of the built in ow. I was just using built in ow profile to launch Overwatch 2 (still the same game).

That said from your log everything seems successful however the reported path of the game is "odd", is your game really installed in V:\Battle.net\Overwatch_retail_\Overwatch.exe?

For comparison my game exe is in C:\Games\Overwatch\_retail_\Overwatch.exe.

juliocoliveira commented 2 years ago

Mine have a _retail_ folder too.

juliocoliveira commented 2 years ago

dafzor commented 2 years ago

But the log line is reporting a Overwwatch_retail_ folder:

20:38:30.5637|20700|Processes.GetProcessStartInfoById:124|INFO|Filename:'V:\Battle.net\Overwatch_retail_\Overwatch.exe'.

Instead of the correct path, it seems battlenet2 path discovery might be broken, but that said it's not required to launch Overwatch, if you use ow it should work normally.

Please try using the built in ow to launch the game

juliocoliveira commented 2 years ago

Already did as i said before, With ow2 custom or built-in ow the result is the same, it takes over a minute to open the window.

21:08:58.9283|23464|Program.Main:133|INFO|Starting bnetlauncher v2.17.8203.29406
21:08:58.9308|23464|Program.LogSystemInfo:733|INFO|Getting System details:
21:08:58.9308|23464|Program.LogSystemInfo:737|INFO|ENV: Microsoft Windows NT 10.0.22621.0 (4.0.30319.42000), 64bit
21:08:59.0075|23464|Program.LogSystemInfo:803|INFO|OS: Microsoft Windows 11 Pro (10.0.22621, 64-bit, 1033)
21:08:59.0075|23464|Program.LogSystemInfo:804|INFO|CPU: AMD Ryzen 7 5800X 8-Core Processor             , RAM: 32768MB
21:08:59.0085|23464|Program.LogSystemInfo:805|INFO|GPU: NVIDIA GeForce RTX 3060 Ti (31.0.15.1748, 4095MB)
21:08:59.0085|23464|Program.LogSystemInfo:806|INFO|HDD: SAMSUNG HD103SJ, Samsung M3 Portable USB Device, KINGSTON SA400S37120G, Force MP600
21:08:59.0160|23464|Program.LoadGameList:594|INFO|Loading gamedb files.
21:08:59.0260|23464|Program.LoadGameList:615|INFO|Loaded internal gamedb with '27' games.
21:08:59.0260|23464|Program.LoadGameList:632|INFO|Known games: '27'.
21:08:59.0260|23464|Program.Main:228|INFO|Given parameter 'ow'.
21:08:59.0260|23464|Program.Main:264|INFO|Using 'battlenet' client.
21:08:59.0260|23464|BnetClient.InstallPath:86|INFO|Client InstallPath:'V:\Battle.net'.
21:08:59.0270|23464|Program.Main:280|INFO|Checking for other bnetlauncher processes using same client
21:08:59.0270|23464|Program.Main:288|INFO|No other bnetlauncher detected
21:08:59.0651|23464|BnetClient.Start:124|INFO|Starting 'battlenet' client.
21:08:59.0651|23464|BnetClient.Start:133|INFO|Starting the client trough task.
21:08:59.0661|23464|BnetClient.InstallPath:86|INFO|Client InstallPath:'V:\Battle.net'.
21:08:59.0966|23464|Tasker.Exists:125|INFO|Found task for battlenet.
21:08:59.0982|23464|Tasker.Run:92|INFO|Starting battlenet task.
21:09:01.1206|23464|BnetClient.WaitUntilReady:180|INFO|Waiting for battle.net client to be ready.
21:09:05.5935|23464|BnetClient.WaitUntilReady:219|INFO|Client fully running with pid:'5840'
21:09:05.5935|23464|Program.Main:350|INFO|Issuing game launch command 'Pro' at '09:09:05.5935'
21:09:05.5935|23464|BnetClient.InstallPath:86|INFO|Client InstallPath:'V:\Battle.net'.
21:09:05.6781|23464|Processes.GetProcessByNameAfterDate:159|INFO|Searching for process 'Overwatch.exe' for '15' seconds.
21:09:06.3258|23464|Processes.GetProcessByNameAfterDate:168|INFO|Found game process started at '09:09:06.2769' with pid:'7988'
21:09:06.3268|23464|Processes.GetProcessStartInfoById:86|INFO|Attempt 1 to find start parameters
21:09:06.4585|23464|Processes.GetProcessStartInfoById:124|INFO|Filename:'V:\Battle.net\Overwatch\_retail_\Overwatch.exe'.
21:09:06.4585|23464|Processes.GetProcessStartInfoById:125|INFO|Arguments:' -uid prometheus'.
21:09:06.4585|23464|Program.Main:428|INFO|Closing game process and starting it under bnetlauncher
21:09:06.5126|23464|Program.CloseClientIfLast:672|INFO|Closing client 'battlenet'.
21:09:07.2258|23464|Program.Main:508|INFO|All operations successful, exiting

dafzor commented 2 years ago

On the ow log I'm not seeing anything wrong and matches the log when running my own machine:

01:29:14.8470|17680|Program.Main:133|INFO|Starting bnetlauncher v2.17.8203.29406
01:29:14.8490|17680|Program.LogSystemInfo:733|INFO|Getting System details:
01:29:14.8500|17680|Program.LogSystemInfo:737|INFO|ENV: Microsoft Windows NT 10.0.19044.0 (4.0.30319.42000), 64bit
01:29:14.8981|17680|Program.LogSystemInfo:803|INFO|OS: Microsoft Windows 10 Pro (10.0.19044, 64-bit, 1033)
01:29:14.8991|17680|Program.LogSystemInfo:804|INFO|CPU: AMD Ryzen 9 5950X 16-Core Processor            , RAM: 32768MB
01:29:14.8991|17680|Program.LogSystemInfo:805|INFO|GPU: AMD Radeon RX 5700 XT (30.0.15021.11005, 4095MB)
01:29:14.8991|17680|Program.LogSystemInfo:806|INFO|HDD: WDC WD40EFRX-68N32N0, Samsung SSD 980 PRO 2TB, CT2000MX500SSD1, Samsung SSD 840 EVO 250GB, WDC WD40EFRX-68N32N0, Samsung SSD 970 EVO 500GB, SAMSUNG HD103SJ
01:29:14.9081|17680|Program.LoadGameList:594|INFO|Loading gamedb files.
01:29:14.9161|17680|Program.LoadGameList:606|INFO|Loaded 'C:\Users\daf\AppData\Local\madalien.com\bnetlauncher\gamedb.ini' with '1' games.
01:29:14.9171|17680|Program.LoadGameList:615|INFO|Loaded internal gamedb with '27' games.
01:29:14.9171|17680|Program.LoadGameList:632|INFO|Known games: '28'.
01:29:14.9171|17680|Program.Main:228|INFO|Given parameter 'ow'.
01:29:14.9171|17680|Program.Main:264|INFO|Using 'battlenet' client.
01:29:14.9181|17680|BnetClient.InstallPath:86|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
01:29:14.9181|17680|Program.Main:280|INFO|Checking for other bnetlauncher processes using same client
01:29:14.9181|17680|Program.Main:288|INFO|No other bnetlauncher detected
01:29:14.9411|17680|BnetClient.Start:124|INFO|Starting 'battlenet' client.
01:29:14.9411|17680|BnetClient.Start:133|INFO|Starting the client trough task.
01:29:14.9411|17680|BnetClient.InstallPath:86|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
01:29:14.9672|17680|Tasker.Exists:125|INFO|Found task for battlenet.
01:29:14.9682|17680|Tasker.Run:92|INFO|Starting battlenet task.
01:29:16.9828|17680|BnetClient.WaitUntilReady:180|INFO|Waiting for battle.net client to be ready.
01:29:21.2098|17680|BnetClient.WaitUntilReady:219|INFO|Client fully running with pid:'12988'
01:29:21.2098|17680|Program.Main:350|INFO|Issuing game launch command 'Pro' at '01:29:21.2098'
01:29:21.2108|17680|BnetClient.InstallPath:86|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
01:29:21.2628|17680|Processes.GetProcessByNameAfterDate:159|INFO|Searching for process 'Overwatch.exe' for '15' seconds.
01:29:21.9435|17680|Processes.GetProcessByNameAfterDate:168|INFO|Found game process started at '01:29:21.9222' with pid:'20320'
01:29:21.9445|17680|Processes.GetProcessStartInfoById:86|INFO|Attempt 1 to find start parameters
01:29:22.0756|17680|Processes.GetProcessStartInfoById:124|INFO|Filename:'C:\Games\Overwatch\_retail_\Overwatch.exe'.
01:29:22.0756|17680|Processes.GetProcessStartInfoById:125|INFO|Arguments:' -uid prometheus'.
01:29:22.0756|17680|Program.Main:428|INFO|Closing game process and starting it under bnetlauncher
01:29:22.1106|17680|Program.CloseClientIfLast:672|INFO|Closing client 'battlenet'.
01:29:22.4239|17680|Program.Main:508|INFO|All operations successful, exiting

I'll need a 3rd party to confirm it working or broken before I know which of our systems is the odd one out.

magic-bit-works commented 2 years ago

Below is what I was able to launch from Steam. I hope this is helpful.

The directory structure is as follows.

bnetlauncher
 |- bnetlauncher.exe
 |- gamesdb.ini

The settings are as follows.

1. add gamesdb.ini

[ow2]
name=Overwatch
client=battlenet
cmd=Pro
exe=%\Overwatch.exe

2. Add a Non-Steam Game

TARGET
"G:\Steam\bnetlauncher\bnetlauncher.exe"

START IN
"G:\Battle.net\Overwatch\"

LAUNCH OPTIONS
ow2

3. Play OverWatch2 from Steam.

There is a problem.

you cannot exit from Steam this way. If you exit from OverWatch, Battle.net window will remain.

juliocoliveira commented 2 years ago

With your command my overwatch 2 don't take over a minute to start, it starts right away. About battle.net auto exit you can force it on settings:

juliocoliveira commented 2 years ago

The problem that i found with that custom db command is that steam overlay does not work at all.

dafzor commented 2 years ago

You shouldn't need to add a new command, the existing ow should still work as expected.

Also the \ in %\Overwatch.exe is not a valid character for an exe name.

magic-bit-works commented 2 years ago

juliocoliveira

Thank you:)

you cannot exit from Steam this way. If you exit from OverWatch, Battle.net window will remain.

Battle.net App Setting "Restore BAttle.net window when the game ends" on disable. able to resolve the issue.

magic-bit-works commented 2 years ago

dafzor

Thanks for the reply. and Thanks for developing a great APP:)

Also the \ in %\Overwatch.exe is not a valid character for an exe name.

Changed %\Overwatch.exe to %\/Overwatch.exe. I am could not be deciphered the file "bnetlauncher/Program.cs".

You shouldn't need to add a new command, the existing ow should still work as expected.

Sorry. I could not start it in my environment.

Perhaps. I assume it is because the APP path has been changed as follows.

OverWatch 1

G:\Battle.net\Overwatch
Overwatch.exe

OverWatch 2(overwatch 1 upgrade to overwatch 2)

G:\Battle.net\Overwatch\_retail_
Overwatch.exe

My method is not official, but I have solved the problem for now. Thank you.

dafzor commented 2 years ago

Changed %\Overwatch.exe to %\/Overwatch.exe.

The exe name should not contain directory separator characters, it's only matched with the name. It's using WQL to query the WMI.

You can run a similar query to the one bnetlauncher uses in Windows Powershell

$exe= 'Overwatch.exe'
Get-WmiObject -Query "SELECT Name, ProcessId, CreationDate FROM Win32_Process WHERE Name LIKE '$($exe)%'"

Glad you got things working for you.

juliocoliveira commented 2 years ago

Why you close it? I still having issue with the launcher....

magic-bit-works commented 2 years ago

Why you close it? I still having issue with the launcher....

Sorry. It was not closing. It was shrinking the launcher after the game.

Because I am using "Steam" in Big Picture Mode. I am using a controller only.

After the game "Battle.net" window cannot be operated when it is in the foreground.

juliocoliveira commented 2 years ago

I mean the issue, @dafzor closed it. For me is not fixed. If i use built-in ow command it takes over a minute to open the overwatch 2 window, But everything works fine. If i use your @samurai-archive db entry it launches right away after clicking on Launch/ Play, but the Overlay does not work. If i launch using standard battle.net launcher from desktop it works fine but not steam overlay, If i launch from steam from battle.net command Battle.net.exe --exec="launch Pro" it does not auto launch, takes over a minute to open the window but the overlay works.

dafzor commented 2 years ago

Why you close it? I still having issue with the launcher....

Because there wasn't anything more to be done on my side. That said I've reopened so it's visible to other users.

juliocoliveira commented 2 years ago

@dafzor ok, thanks. Do you have any idea why with @samurai-archive's db entry it launches right away but with the built-in ow one it takes over a minute to launch. Have any guess?

dafzor commented 2 years ago

@dafzor ok, thanks. Do you have any idea why with @samurai-archive's db entry it launches right away but with the built-in ow one it takes over a minute to launch. Have any guess?

The only difference from the built-in ow entry and @samurai-archive one is the invalid exe name, thus i'd expect it to work without the overlay as it can't find the game running (exe name will never match).

If with ow it take 1m i can only guess it's some interaction of overwatch and steam or even some anti-virus software.

you can use windows key + R to run bnetlauncher ow on it's own without steam and see if that also takes a long time. If it doesn't then the issue might be steam overlay itself.

juliocoliveira commented 2 years ago

Yes is some issue with steam, I launched from Run as you said and it launched in 6 seconds after auto clicked on Play/Launch. Its not AV because i disabled all the modules from my Kaspersky Plus and it still took over a minute to open. That said any clue of how to fix it? Maybe its a Windows 11 22h2 issue with steam i don't know.

dafzor commented 2 years ago

I use steam beta and windows 10, so you can try switching to the steam beta if you're not using it.

Other then that no other suggestion.

juliocoliveira commented 2 years ago

Bummer, steam beta didn't fixed, Probably its a Steam Overlay in Windows 11 22h2 issue for Overwatch 2 specifically, Other non steam games opens normal, and tested with StarCraft II and it opens normally too.

Its not the worst thing in the World waiting 76 seconds to play a game, its just really annoying.

juliocoliveira commented 2 years ago

Tried everything, run as Windows 8 compatibility, Run as Administrator, nothing fixes. As administrator the overlay does not work at all.

I just want know if this is normal for all Windows 11 users, or only me.

juliocoliveira commented 2 years ago

I tested on Windows 10, and it runs normally, So its a Steam Overlay issue on Overwatch 2 for Windows 11.

juliocoliveira commented 1 year ago

Its fixed, Today was released an update that fixed this issue! Thanks for the support!

dafzor / bnetlauncher