Comments (6)
For retry to actually work you'd need to have the game running which from the state of your play button I assume it's not.
What seems to be happening at first glance is the Battle.net Client isn't actually starting the game as it's supposed, a log might be helpful in trying to determine why (see troubleshooting in https://github.com/dafzor/bnetlauncher/blob/master/README.md)
from bnetlauncher.
Sorry about the delayed response, I had to wait to re-trigger it after enabling logging
@04:20:03.9003
I clicked Retry---after clicking Play in the launcher, though, so ignore past that timestamp. Importantly: as of that point, the bug had already triggered as described in the OP.
04:19:38.9728|17296|Program.Main:130|INFO|Starting bnetlauncher v2.2.6902.17778
04:19:38.9857|17296|Program.LogSystemInfo:718|INFO|Getting System details:
04:19:38.9867|17296|Program.LogSystemInfo:722|INFO|ENV: Microsoft Windows NT 10.0.17134.0 (4.0.30319.42000), 64bit
04:19:39.1428|17296|Program.LogSystemInfo:788|INFO|OS: Microsoft Windows 10 Pro (10.0.17134, 64-bit, 1033)
04:19:39.1447|17296|Program.LogSystemInfo:789|INFO|CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz, RAM: 12288MB
04:19:39.1468|17296|Program.LogSystemInfo:790|INFO|GPU: AMD Radeon HD 7800 Series (25.20.15031.1000, 2048MB)
04:19:39.1487|17296|Program.LogSystemInfo:791|INFO|HDD: WDC WD10EZEX-22BN5A0 ATA Device
04:19:39.1558|17296|Program.LoadGameList:581|INFO|Loading gamedb files.
04:19:39.1857|17296|Program.LoadGameList:602|INFO|Loaded internal gamedb with '10' games.
04:19:39.1868|17296|Program.LoadGameList:619|INFO|Known games: '10'.
04:19:39.1878|17296|Program.Main:205|INFO|Disabling task launching
04:19:39.1887|17296|Program.Main:225|INFO|Given parameter 'ow'.
04:19:39.1898|17296|Program.Main:261|INFO|Using 'battlenet' client.
04:19:39.1908|17296|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
04:19:39.1918|17296|Program.Main:277|INFO|Checking for other bnetlauncher processes using same client
04:19:39.1928|17296|Program.Main:285|INFO|No other bnetlauncher detected
04:19:39.3557|17296|Program.Main:328|INFO|Client already running with pid:'6468'.
04:19:39.3577|17296|Program.Main:340|INFO|Issuing game launch command 'Pro' at '04:19:39.3557'
04:19:39.3597|17296|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
04:19:39.6287|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '15' seconds.
04:19:40.6087|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '14' seconds.
04:19:41.6037|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '13' seconds.
04:19:42.6057|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '12' seconds.
04:19:43.6057|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '11' seconds.
04:19:44.5987|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '10' seconds.
04:19:45.5887|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '9' seconds.
04:19:46.6187|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '8' seconds.
04:19:47.6266|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '7' seconds.
04:19:48.6037|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '6' seconds.
04:19:49.6036|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '5' seconds.
04:19:50.6046|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '4' seconds.
04:19:51.5987|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '3' seconds.
04:19:52.5999|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '2' seconds.
04:19:53.6014|17296|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '1' seconds.
04:19:54.6074|17296|Program.Main:359|ERROR|Game 'ow' not found within timeout.
04:20:03.9003|17296|Program.Main:375|INFO|User chose to retry searching for game.
04:20:03.9543|17296|Processes.GetProcessByNameAfterDate:167|INFO|Found game process started at '04:19:58.1067' with pid:'2704'
04:20:03.9764|17296|Processes.GetProcessStartInfoById:85|INFO|Attempt 1 to find start parameters
04:20:04.1104|17296|Processes.GetProcessStartInfoById:123|INFO|Filename:'C:\Program Files (x86)\Overwatch\Overwatch.exe'.
04:20:04.1114|17296|Processes.GetProcessStartInfoById:124|INFO|Arguments:' -uid prometheus'.
04:20:04.1354|17296|Program.Main:418|INFO|Closing game process and starting it under bnetlauncher
04:20:04.4893|17296|Program.Main:497|INFO|All operations successful, exiting
(a note: I am launching it with -n
in this case [Overwatch], which is a deviation from the OP case [Destiny 2], however the bug is seeming to be identical)
from bnetlauncher.
It happens with and without -n
correct? From the log everything on bnetlauncher side seems to be working properly.
I see you're using a single mechanical drive, so at first glance I'd agree with your hypothesis that it could be caused by battle.net client taking longer to start and not being ready when bnetlauncher issues the launch game command.
But it's very weird to see it happen when the battle.net client is already running (as in the case of the posted log), there's also enough RAM that I'd think unlikely for the battle.net client to be paged out of RAM... Do you notice any IO spike or lockup on your system when the issue happens?
Regardless, I don't know if there's much I can do besides just adding an auto-retry launch option, which might not be effective since the issue is not consistent (only happens sometime). I also don't have access to any HDD based systems so can't really do much testing on my own.
PS: Out of curiosity why do you disable task scheduler launch for overwatch?
from bnetlauncher.
It happens with and without
-n
correct?
Yes; here is a log from without it:
18:27:15.3677|8232|Program.Main:130|INFO|Starting bnetlauncher v2.2.6902.17778
18:27:15.4427|8232|Program.LogSystemInfo:718|INFO|Getting System details:
18:27:15.4447|8232|Program.LogSystemInfo:722|INFO|ENV: Microsoft Windows NT 10.0.17134.0 (4.0.30319.42000), 64bit
18:27:15.7577|8232|Program.LogSystemInfo:788|INFO|OS: Microsoft Windows 10 Pro (10.0.17134, 64-bit, 1033)
18:27:15.7597|8232|Program.LogSystemInfo:789|INFO|CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz, RAM: 12288MB
18:27:15.7617|8232|Program.LogSystemInfo:790|INFO|GPU: AMD Radeon HD 7800 Series (25.20.15031.1000, 2048MB)
18:27:15.7637|8232|Program.LogSystemInfo:791|INFO|HDD: WDC WD10EZEX-22BN5A0 ATA Device
18:27:15.7707|8232|Program.LoadGameList:581|INFO|Loading gamedb files.
18:27:15.7947|8232|Program.LoadGameList:602|INFO|Loaded internal gamedb with '10' games.
18:27:15.7958|8232|Program.LoadGameList:619|INFO|Known games: '10'.
18:27:15.7967|8232|Program.Main:225|INFO|Given parameter 'ow'.
18:27:15.7977|8232|Program.Main:261|INFO|Using 'battlenet' client.
18:27:15.7987|8232|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
18:27:15.8007|8232|Program.Main:277|INFO|Checking for other bnetlauncher processes using same client
18:27:15.8017|8232|Program.Main:285|INFO|No other bnetlauncher detected
18:27:16.2037|8232|Program.Main:328|INFO|Client already running with pid:'12136'.
18:27:16.2047|8232|Program.Main:340|INFO|Issuing game launch command 'Pro' at '06:27:16.2037'
18:27:16.2057|8232|BnetClient.InstallPath:84|INFO|Client InstallPath:'C:\Program Files (x86)\Battle.net'.
18:27:17.1607|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '15' seconds.
18:27:18.1407|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '14' seconds.
18:27:19.1556|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '13' seconds.
18:27:20.1557|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '12' seconds.
18:27:21.1496|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '11' seconds.
18:27:22.1516|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '10' seconds.
18:27:23.1396|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '9' seconds.
18:27:24.1426|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '8' seconds.
18:27:25.1366|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '7' seconds.
18:27:26.1406|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '6' seconds.
18:27:27.1545|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '5' seconds.
18:27:28.1476|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '4' seconds.
18:27:29.1395|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '3' seconds.
18:27:30.1256|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '2' seconds.
18:27:31.1576|8232|Processes.GetProcessByNameAfterDate:158|INFO|Searching for process 'Overwatch.exe' for '1' seconds.
18:27:32.1555|8232|Program.Main:359|ERROR|Game 'ow' not found within timeout.
18:27:51.3612|8232|Program.Main:381|INFO|User chose to cancel.
Though, interestingly and (I think) importantly, even after the above log, Steam showed me as Playing through the entire duration of the Overwatch session [(update: including properly displaying the game's exit; this is with Steam 2019-04-29_14:01:22
/1556574584
, Overwatch v1.35.1.1.57979
, and Battleโ.net launcher v1.14.1.11144
)], despite the fact that I waited several minutes [after Canceling bnetlauncher] to click Play and actually start Overwatch. (This behavior, too, is observed both with and without -n
.)
(And I double-checked to be sure: Steam itself is calling bnetlauncher; I did not simply hook Steam up to Battle directly and forget about it)
PS: Out of curiosity why do you disable task scheduler launch for overwatch?
That is mainly out of an unsubstantiated hunch/guess that it would launch faster that way, since I don't see what the point of dragging extra system cruft into the picture is. (I know there is probably a purpose, I just missed it, it seems)
from bnetlauncher.
Steam overlay injects itself into anything started by steam, and of what you launch starts multiple applications each will get it's own overlay and you'll be shown playing until they all exit.
So if after the log above it still showed you as playing the game it means bnetlauncher.exe could have become stuck running, which shouldn't happen.
In a related note launching the client with a task is to avoid exactly that issue of having steam give the battle.net an overlay too.
Sadly none of it sheds any more light on the issue and I'm still unable to understand what might be going wrong.
from bnetlauncher.
No feedback in 4 months.
from bnetlauncher.
Related Issues (20)
- WoW Classic not launching HOT 1
- WoW Classic TBC HOT 9
- Crash Bandicoot 4 doesn't launch. HOT 12
- CoD: MW 2019 not launching properly HOT 2
- Cannot launch warzone with bnetlauncher. HOT 2
- Add support for Blizzard Arcade Collection HOT 3
- Add support for Call of Duty: Vanguard HOT 1
- Add support for SoM version of Classic WOW HOT 5
- Add support for Classic World of Warcraft HOT 3
- A way to launch overwatch 2 beta HOT 5
- Add support for Diablo Immortal HOT 2
- Breaks XInput in Overwatch HOT 7
- Not Launching Overwatch 2 HOT 32
- Add support for COD Modern Warfare 2 (CODhq) HOT 5
- Modern Warfare II does not launch properly HOT 4
- Vanguard launches with error HOT 3
- Steam Deck support HOT 5
- Spelling error in program.cs
- Diablo 4 Support HOT 1
- Error: Client not found & steam overlay not working
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bnetlauncher.