search

WombatFromHell / OriginSteamOverlayLauncher

An executable wrapper for Steam to make third-party launchers more convenient to use with a Steam Controller
MIT License
413 stars 25 forks source link

Launching Black Ops 4 doesn't work properly #30

Closed rastla closed 5 years ago

rastla commented 5 years ago

So I set it up for Black Ops 4 like this:

LauncherPath=D:\Program Files (x86)\Battle.net\Battle.net.exe
LauncherArgs=--exec="launch VIPR"
LauncherURI=
GamePath=C:\Games\BattleNetApps\Call of Duty Black Ops 4\BlackOps4.exe

And first the launcher starts and then Black Ops 4 starts. But Black Ops 4 can't connect to the online services if it isn't startet through the BattleNET App.

WombatFromHell commented 5 years ago

That's odd. I've tested against Overwatch, Hearthstone, Destiny 2, and Heroes of the Storm and the launcher commands seemed to work okay.

I'll investigate and get back to you ASAP.

(Also, make sure you're running OSOL v1.07d as it has commits that address this issue.)

WombatFromHell commented 5 years ago

Could you post your OSOL log file for the game in question when you get a chance?

Running OSOL v1.07d, my working INI looks like this:

[Paths]
LauncherPath=C:\Program Files (x86)\Battle.net\Battle.net.exe
LauncherArgs=--exec="launch VIPR"
LauncherURI=
GamePath=E:\Games\Battle.net\Call of Duty Black Ops 4\BlackOps4.exe
GameArgs=
MonitorPath=
DetectedCommandline=
[Options]
LauncherMode=Normal
PreLaunchExec=
PreLaunchExecArgs=
PostGameExec=
PostGameExecArgs=
PreGameLauncherWaitTime=12
PostGameWaitTime=7
PostGameCommandWaitTime=7
ProxyTimeout=3
ProcessAcquisitionTimeout=300
ReLaunch=True
SkipLauncher=False
DoNotClose=False
ForceLauncher=False
MinimizeLauncher=False
CommandlineProxy=False
ElevateExternals=False
GameProcessAffinity=
GameProcessPriority=
TerminateOSOLUponLaunch=False

My OSOL log looks like this:

[8/11/2018 7:07:47 PM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher
[8/11/2018 7:07:47 PM] [OSOL] Found previous instance of launcher by name, killing and relaunching...
[8/11/2018 7:07:50 PM] [OSOL] Attempting to start the launcher: C:\Program Files (x86)\Battle.net\Battle.net.exe
[8/11/2018 7:07:50 PM] [OSOL] Searching for valid process by name: Battle.net
[8/11/2018 7:07:53 PM] [OSOL] Bound to a valid process at PID: 7184 [Battle.net.exe] in 3 seconds
[8/11/2018 7:07:53 PM] [OSOL] Waiting 12s for launcher process to load...
[8/11/2018 7:08:05 PM] [OSOL] Detected Battle.net launcher, calling game via: C:\Program Files (x86)\Battle.net\Battle.net.exe --exec="launch VIPR"
[8/11/2018 7:08:05 PM] [OSOL] Searching for valid process by name: BlackOps4
[8/11/2018 7:08:17 PM] [OSOL] Bound to a valid process at PID: 10768 [BlackOps4.exe] in 12 seconds
[8/11/2018 7:17:13 PM] [OSOL] The game exited, moving on to clean up...
[8/11/2018 7:17:20 PM] [OSOL] Found launcher still running, cleaning up...

The launching behavior (using Battle.net launch commands) is working and consistent with all titles launched via the Battle.net App on OSOL v1.07d as far as I can tell.

WombatFromHell commented 5 years ago

Since no additional information has been offered to support this ticket after 7 days I'll be closing this ticket. Feel free to provide additional information if you still need support and I'll re-open the ticket and assist.