search

WombatFromHell / OriginSteamOverlayLauncher

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

Battle.net launcher detection is busted #36

Closed AcidWeb closed 5 years ago

AcidWeb commented 5 years ago

Currently calling launcher with --exec="launch WoW" only start the launcher not the game itself. After launcher is ready it need to be started once more with --exec="launch WoW" to start the game.

So correct config in this case look like this:

LauncherPath=C:\Path\To\Launcher\Battle.net.exe
LauncherArgs=--exec="launch WoW"
GamePath=C:\Path\To\Launcher\Battle.net.exe
GameArgs=--exec="launch WoW"
MonitorPath=C:\Path\To\World of Warcraft\_retail_\Wow.exe

OSOL can't start Wow.exe directly as it will not receive auth data from Battle.NET client.

WombatFromHell commented 5 years ago

Try the pre-release v1.08a build in the releases section and let me know if it addresses this issue.

AcidWeb commented 5 years ago

It is not. It is more Battle.NET client issue than OSOL. Created this ticket only to point out that wiki is out-of-date.

WombatFromHell commented 5 years ago

This behavior sounds like OSOL is not detecting the Battle.net launcher properly. When Battle.net is detected OSOL uses different launch logic (it doesn't call the game path manually).

I'll look into it. I may need to add an optional override in the OSOL .ini to force OSOL to use that special logic in case the launcher window details change between releases

WombatFromHell commented 5 years ago

Confirmed. OSOL's launcher detection isn't working properly. ETA on a fix is "soon".

WombatFromHell commented 5 years ago

Try the pre-release v1.08b build that I just pushed to the releases page and let me know if it fixes the problem for WoW. I only have Overwatch installed at the moment to test against.

AcidWeb commented 5 years ago

I can confirm that issue is fixed. Settings provided in wiki now work correctly.