OSOL Troubleshooting - WombatFromHell/OriginSteamOverlayLauncher GitHub Wiki

Q: Is there a way I can set the Priority and CPU Affinity for the game process?

A: As of v1.07, yes - there is! You'll want to use GameProcessAffinity and GameProcessPriority respectively. The easiest way to use GameProcessAffinity is to set a string of digits representing the cores you want the process to use separate by commas (without spaces) like so: GameProcessAffinity=0,2,4,6. There are also several plain-text shortcuts for common configurations such as:

  • DisableHT (only use half the logical cores of the system to avoid hyperthreading)
  • QuadCore (use the first four cores)
  • DualCore (use the first two cores)
  • You may also use a number or a hexadecimal (ex: 0xAA) to specify the cores you want to use (see this image for how to get this value)

GameProcessPriority works similarly except the priorities that can be set are as follows (e.g. GameProcessPriority=AboveNormal):

  • Idle
  • BelowNormal
  • AboveNormal
  • High
  • RealTime

In addition, the timing for when these commands will be executed after the game process launches is controlled by the PostGameCommandWaitTime option in the INI (set in seconds from when OSOL attaches to the game process).

Q: Is there a way to force OSOL to close itself right after a game launches?

A: Yes. You want the TerminateOSOLUponLaunch option. Set it to True and OSOL will kill itself after launching a game/monitor process, or in the event that the GamePath/MonitorPath is not set it will die after the launcher spawns.

Q: I experience crashes when running OSOL. I'm running windows 7. Help!

A: If you experience crashes when starting OSOL and are running Windows 7, make sure you install the .NET 4.7.1 Redistributable found here.

Q: Can I replace a Steam launched game with OSOL (to take advantage of OSOL's pre/post-launch features)?

A: Yes, but only if the game itself does not have an embedded launcher (i.e. if it has it's own game executable it will work). Something like the following will work:

  • Rename the game executable to something else, say Game.exe becomes LaunchedGame.exe
  • Copy OSOL to the game executable's directory and rename it to the original game executable name, like: Game.exe
  • Now you have Game.exe (which is actually OSOL) and LaunchedGame.exe (which is the real game executable) in the same directory
  • Launch OSOL and choose -only- the game executable (in this case, LaunchedGame.exe). Simply cancel out of the Launcher path chooser dialog.
  • Launch your game via Steam. That's it!

NOTE: there are two possible downsides to doing this (AFAIK) - firstly, Steam's background game updater will most likely overwrite the OSOL executable when a new game update comes out, and secondly, some anti-cheat mechanisms may give false positives due to the game executable not being named the same as their internal manifest (unconfirmed).

The 100% safe thing to do is to just make a shortcut to OSOL that launches the game rather than doing it entirely through Steam. You do you, though.

Q: I have multiple games that I use with OSOL, how can I update all the OSOL exe's when OSOL is updated?

A: Until work is finished on the INI manager feature in OSOL you can put the OSOL exe file in a directory with a batch file (OSOL-updater.cmd for instance) that contains something like the following, removing the rem before the path you want to copy OSOL to, and adding your own game paths. Unpack a new version of OSOL to this directory, then run the batch file whenever you want to update all your OSOL installations:

@ECHO OFF
SET OSOLPRE=copy /y OriginSteamOverlayLauncher.exe
rem
rem Installed games you're using right now:
rem
%OSOLPRE% "C:\Games\Destiny 2"
%OSOLPRE% "C:\Games\Mirror's Edge Catalyst"
%OSOLPRE% "C:\Games\Tom Clancy's Rainbow Six Siege"
rem
rem Uninstalled games you might want to play in the future:
rem
rem %OSOLPRE% "C:\Games\An Uninstalled Game"

Q: Can OSOL minimize the launcher automatically when I launch a game?

A: Yes, set MinimizeLauncher=True in the INI

Q: How can I stop OSOL from restarting my launcher?

A: Go into your OSOL INI file and change ReLaunch=True to ReLaunch=False

Q: My game requires its launcher to be running in the background! How can I force OSOL to run LauncherPath when using CommandlineProxy?

A: As of release v1.06k, you can go into your OSOL INI file and change ForceLauncher=False to ForceLauncher=True. This will override CommandlineProxy so that the launcher will run before the game does.

Q: How can I stop OSOL from killing my launcher when the game exits?

A: Go into your OSOL INI file and change DoNotClose=False to DoNotClose=True

Q: Is there a way to run a command before and/or after a game is launched through OSOL?

A: Yes, there is, in the OSOL ini file you'll find four lines for PreLaunchExec and PostGameExec. They will call a command before the Game is called and after the Game exits (before the launcher is closed).

NOTE: As of v1.06j you can now choose whether to run PreLaunchExec and PostGameExec with elevated privileges by changing ElevateExternals in the INI.

Q: Can I adjust the waiting period in OSOL so my game saves will sync before the launcher is closed?

A: Yes, there is a line in the OSOL ini for this: PostGameWaitTime and it adjusts in seconds. You'll most likely want it set to 30 seconds or more depending on the speed of your internet connection.

Q: I have an older machine and OSOL tries to launch the game before the launcher has loaded. How do I prevent this?

A: You can adjust OSOL's launching timeouts in the OSOL ini. There are two you'll want to change: PreGameOverlayWaitTime and PreGameLauncherWaitTime. Simply increase them (in seconds) until the problem goes away.