wombatfromhell/originsteamoverlaylauncher

An executable wrapper for Steam to make third-party launchers more convenient to use with a Steam Controller

OSOL (O.rigin S.team O.verlay L.auncher)

Why should I use OSOL

If you've tried using the Steam Controller (or any other Steam Input supported device) from a couch with a third-party non-Steam game (like with games on Battle.net, Origin, or UPlay) then you know how annoying this combination can be. OSOL was created to make this process significantly more user-friendly while also providing additional functionality not typically available using other tools (CPU affinity, process priority, and pre/post launch command execution).

Aside from the most common mainstream launchers mentioned previously OSOL is also compatible with the vast majority of emulators and even some MMORPG/MMOFPS launchers. See the OSOL project wiki for more details about this and other application specific notes.

OSOL currently supports the following launchers: Battle.net, UPlay, Origin, GOG Galaxy, Epic Games Launcher, Steam, and most Emulators/Master Launchers that call a game's executable file.

How To Install/Uninstall

This wrapper requires no installation other than copying it into the directory of the game executable you wish to run through Steam BPM/Overlay. It also can simply be deleted if you wish to uninstall it at any time. If you have trouble running it, or are running Windows 8 or earlier, you may need to download and install the .NET Framework Runtime v4.7.1.

How To Use

• Unpack the OSOL .exe file from the OSOL archive into the game directory (where the game's executable is located for example).
• Run the OSOL .exe file from this directory and it will prompt you to choose the path to your game executable (required) and the game launcher (which is optional).
• Add the OSOL .exe to Steam as a non-Steam game by clicking the "Add a game" button on the bottom left of the Steam window, clicking "Add a Non-Steam Game" and selecting the OSOL .exe file in the path chooser.
• Name this new non-Steam game shortcut of OSOL (in Steam) whatever you like (such as your game's name).
• Run this non-Steam game shortcut from the Steam library as any other Steam game and the Steam overlay and third-party overlay should show up in-game (if enabled).
• Optional: for advanced functionality or compatibility options for particular launchers see the OSOL project Wiki.

Notes

If you're looking for specific instructions on getting OSOL working with a particular launcher or are having issues with behavior you believe is related to OSOL please read the project Wiki before making an issue ticket.

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

If you have difficulty getting the Steam overlay to hook into your game when launching with OSOL please follow these instructions, and make sure OSOL and Steam are both running with the appropriate permissions (if Steam is running as Admin, make sure to run OSOL as Admin as well so that all processes spawned from it can be hooked by Steam). This is important for older games (circa <2007).

If you have issues with games not launching with the Steam Overlay and are using a recent AMD graphics device you may need to disable the "AMD External Events Utility" service by following the instructions below:

• Run "services.msc".
• Browse down to the "AMD External Events" service.
• Double-click it, change the startup type to "Disabled", and click "Stop" to disable the service, then click "OK" and exit the dialog.

NOTE: This will break FreeSync functionality, but allow the Steam Overlay to hook into Origin games.

If you find a launcher that doesn't work with OSOL please report it so I can consider adding it to the supported launchers list.

How To Compile

If you wish to compile this project from Github source, you'll need Visual Studio v14+ or Visual Studio Community (targetting the .NET Framework v4.7.1 for C#). There are no external libraries required except for the .NET v4.7.1 framework package. The source code can be modified freely under the MIT license as long as the contributers and creator are given credit.

If you'd like to contribute please make sure to comment your code thoroughly and try to split major features up into their own PRs when possible.

Credits

Special thanks to CriticalComposer for his art/icon contribution to the OSOL project.

Thanks to Dafzor and his bnetlauncher wrapper (http://madalien.com/stuff/bnetlauncher/) for giving me the idea to make this.

Donations

If you find this project useful and you would like to donate toward on-going development you can use the link above. Any and all donations are much appreciated!

originsteamoverlaylauncher's Issues

Unable to launch Cemu

Firstly, thanks for OSOL. It's really convenient and solved a lot of my issues with playing non-Steam games on the Steam Link.

I'm trying to get OSOL to launch Cemu, following the steps listed in the Wiki, but for some reason Cemu never gets launched. When setting GamePath to my Cemu executable, nothing happens (other than the OSOL process being run).

Thanks in advance for any help provided!

Doesnt work with Battlefield 4

The first try actually worked I could use the overlay but after a couple of times (always a random ammount) the game crashes. And now the overlay launcher doesnt work at all. Even after reinstalling it. Is there anything that can be done ?

MinimizeLauncher doesn't work after game exited.

I'm using OSOL to launch Origin game from Steam, set Origin as launcher and set a specific game to start.

"MinimizeLauncher" is set to true, Origin can be minimized before game start, but after game exited, Origin is not minimized before it get killed.

Uplay Support

Opens Uplay but doesn't start the game.

Overlay not working properly with Battlefront II (2017)

I've followed all the steps, but when I try to launch Battlefront II with the overlay, it just won't work. In Steam, I get the "xxxxx in non-steam game" and it stays there until I close the game, but then I can't open de overlay with the usual shift+tab.

Epic Games Store URI Launching

Steam overlay is busted on Battle.net launched games

It appears to be a regression in the Battle.net client, but I'm currently investigating.

FIFA 19

When i launch the shortcut origins opens FIFA comes up and then origins crashes or reboots and game doesnt launch (Launcher skip also dosnt work)

Any way to make it work with windows store games?

I would love to use my SC with Gears of War, Minecraft Win 10 ed and Forza. Thanks!

Ranbow six siege - Anyone having issues.

Its seems to be having a lot of issues now for some reason. I think uplay did an update. Not sure can someone let me know if this is doing the same thing to them?

Origin and Battlefront 2

The game launches but the screen is black. After some time the game ends and closes everything

Assassin's Creed: Origins

Hey mate,

I have Assassin's Creed Origins running by loading using OSOL and the upc.exe except steam overlay doesnt seem to work at all, no response from pushing the steam button on controller.
I have tried with and without uplay overlay.
Attempted turning off Allow desktop configuration in launcher (under AC:O manage shortcut -> controller options).
Tried changing base desktop configuration to mimic a gamepad or similar.

My setup is pc -> steam link -> steam controller connected to link.
Either way I am not able to access steam overlay by pushing the steam button and seems to be running as a desktop style config no matter what.
My next step was to try glosc which it seems to work but causes low fps

Thanks,

Quit Origin on game exit

Hello, I'm trying to get Origin to quit on game exit. If the Origin app remains open, it causes functionality issues with the Steam Link. I can see there are PostGameExec= and PostGameExecArgs= options in the ini but cannot find an example of how to use these to quit Origin on game exit.

By any chance do you own escape from tarkov?

It seems to be a weird one. So the launcher launches the game but it dosent use the .exe because there is no in game login then. Not sure if there is a work around with this.

Executable arguments limited to 255 characters?

When launching an executable with additional arguments, it seems that OSOL cuts off anything beyond 255 characters in length. I'm trying to launch Elite: Dangerous via OSOL so that I can automatically start the Elite Dangerous Market Connector before the game. In order to start ED outside of its native launcher, you need to supply the game with your server auth token via command line as well as including a few extra switches (i.e. /novr to suppress the game starting SteamVR by default).

Would it be possible to extend the length of arguments beyond that?

Steam Overlay Overrides Origin Overlay

IGO_Log.Titanfall2_9604.txt

FIFA 18 not working in l

FIFA 18 worked at the b version but after l it doesn't show up anymore.
The overlay seems to appear in Origin and not the game.

Any way to have the process kill itself after Launch ?

First off, this is the first solution that has worked in my attempts to get Steam Controller/PS4 controller to be recognized with Xinput in Battlefield 4 allowing me to use a combination of Xinput/direct input/mouse Gyro's. So thanks for that.

Only version " J " works for me, I've tried K and L, they fail to have any result. I'm on Windows 7 Pro btw.

The error "OriginSteamOverlayLauncher.exe has stopped working" keeps popping up quite frequently until I Alt Tab out and kill the OSOL process. Which oddly leaves everything in perfect order afterwards, Steam is able to maintain Overlay and Controls within the game.

I'd love to have an option to have the OSOL process kill itself shortly after performing the launch of Battlefield 4. Not only for myself, but for my less PC inclined PC gaming friend who uses a Steam Controller for BF4 and is always complaining about the need to setup direct input controls in non Steam games. Also having to substitute WASD for Analog Sticks can be a killer in some games.

I need a detailed tutorial on how to use ;-;

Pls ;-; and ""install""

Origin stays open after game exit

Hello,
I have tested with both Titanfall 2 and Apex Legends. Origin launches and both games execute fine, but Origin stays open after game exit.

Here is my INI settings:

[Paths]
LauncherPath=C:\Program Files (x86)\Origin\Origin.exe
LauncherArgs=
LauncherURI=
GamePath=D:\Origin\Apex\r5apex.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

Here is my log:

[2/9/2019 6:23:43 AM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher
[2/9/2019 6:23:44 AM] [OSOL] Attempting to start the launcher: C:\Program Files (x86)\Origin\Origin.exe
[2/9/2019 6:23:44 AM] [OSOL] Searching for valid process by name: Origin
[2/9/2019 6:23:47 AM] [OSOL] Bound to a valid process at PID: 3456 [Origin.exe] in 3 seconds
[2/9/2019 6:23:47 AM] [OSOL] Waiting 12s for launcher process to load...
[2/9/2019 6:23:59 AM] [OSOL] Launching game, cmd: D:\Origin\Apex\r5apex.exe
[2/9/2019 6:23:59 AM] [OSOL] Searching for valid process by name: r5apex

Origin Fifa - Mouse wont disappear

Hi,

I like and use OSOL a lot at my living room while my PC is in the cellar. It works mostly perfect, having only one issue with FIFA on Origin. I use FIFA 2018 but tested it on FIFA 2020 DEMO as well.

After launching it the mouse cursor wont disapper and sticks at the middle of the screen. The controllers (XBOX 360 Controllers connected to steam link) work fine.

Any help or info would be appreciated.

Sorry for my bad english since I am not a native speaker.

Greetings

ListGrey

Please add a cmd option (/ini)

This is more of an enhancement request.

Could you add a cmd option where OSOL can find its ini file (or create it)?

I tried OSOL together with GOG galaxy and placing OSOL in the folder of the game didn't work.
Well the game started but the overlay of GOGgalaxy didn't work. Moving OSOL into the folder of the launcher changed that.
I used LauncherOnly and the cmd-line in the shortcut that gog created to run the game with gog.
Thanks for your efforts.

There is no .exe

So i dont see a .exe to even use. Is there something im missing?

Origin doesn't closes (Battlefront II)

With the 1.05c; The log says "FATAL" and can't find the game .exe process ID.
With the 1.04 says nothing.
In both cases just Origin doesn't closes after the game. Ir remains opened.

With Battlefront I (my other Origin game) it works perfect.

Can’t get FIFA 18 to work with Steam Overlay

Hey,
Maybe this is not the right place but I can’t get OSOL to work properly. After my first installation it deleted the Origin exe then on the second try the FIFA exe (?). This could be my foult but well after these tries I deactivated that AMD service and it launched but first the Overlay was about Origin and then it wouldn’t start because of failed cloud sync. (It did work before) I cleared the settings and shut down the cloud sync but then it wouldn’t start through OSOL anymore. Only Origin with the Overlay and not FIFA. I can give you any logs you want.
Again I’m not sure if this is a problem caused by me or OSOL so thank you in advance if you could look into that.

Origin Steam Overlay Launcher & Mirror's Edge Catalyst

Attempting to run Mirror's Edge Catalyst with OSOL through Steam results in Origin opening and then after attempting to open Mirror's Edge, crashing silently. Attached are the log for Mirror's Edge and the log created directly after that I believe may hold insight into what went wrong.
IGO_Log.MirrorsEdgeCatalyst_4960.txt
IGO_Log.igoproxy64_4744.txt

Any way to make OSOL work with Star Citizen?

So, I was wondering if there is any way to make OSOL work fully automatically, with the Star Citizen launcher (RSI Launcher) and game, so that I can launch Star Citizen from a shortcut in Steam?

As it is, I got it working... BUT, after steam starts OSOL, and OSOL starts the launcher, then I have to manually click the 'launch game' button inside the launcher, to get it to start up the actual game... Otherwise the game starts up and then crashes with an error message saying it couldn't find any user information.

Is there any way to make OSOL basically click that button for me? So far as I know, there are not any command line options for the launcher.. :(

The Star Citizen Launcher:

Star Citizen Startup/Loading Screen:

Apex Legends - Overlay Not working

The steam overlay not working with Apex Legends (origin)

Using 1.08c
Origin overlay disabled

Log:

[3/27/2019 3:39:24 PM] [NOTE] OSOL is running as: OriginSteamOverlayLauncher [3/27/2019 3:39:24 PM] [OSOL] Attempting to start the launcher: C:\Program Files (x86)\Origin\Origin.exe [3/27/2019 3:39:24 PM] [OSOL] Searching for valid process by name: Origin [3/27/2019 3:39:45 PM] [OSOL] Found a valid process in 21s: Origin.exe [13588] [3/27/2019 3:39:45 PM] [MONITOR] Monitoring process Origin.exe for 7s [3/27/2019 3:39:52 PM] [MONITOR] Target process (Origin.exe [13588]) is still running after 7s [3/27/2019 3:39:52 PM] [OSOL] Launching game, cmd: D:\Origin Games\Apex\r5apex.exe [3/27/2019 3:39:52 PM] [OSOL] Searching for valid process by name: r5apex [3/27/2019 3:40:14 PM] [OSOL] Found a valid process in 21s: r5apex.exe [7508] [3/27/2019 3:40:33 PM] [MONITOR] Process exited after 19s attempting to reaquire r5apex.exe [3/27/2019 3:40:33 PM] [MONITOR] Monitoring process r5apex.exe for 10s [3/27/2019 3:40:43 PM] [MONITOR] Timed out after 10s while monitoring the target process: r5apex.exe [3/27/2019 3:40:43 PM] [OSOL] Game exited, moving on to clean up after 7s... [3/27/2019 3:40:50 PM] [OSOL] Found launcher still running, cleaning up... [3/27/2019 3:40:50 PM] [OSOL] Exiting...

Checklist for 1.06

• Add 'ReLaunch' option to stop OSOL from closing a pre-existing launcher before launching a game
• Add 'DoNotClose' option to stop OSOL from closing a launcher after quitting a game
• Implement a mutex to stop obnoxious behavior in rare circumstances
• Expose more timeout options in the INI
• Add an INI command overview dialog when launching with "/help"
• Fix OSOL not launching Battle.net URIs properly in URI mode
• Look into implementing an optional auto-minimize upon detection of launcher
• Allow renaming OSOL executable (pick up non-hardcoded OSOL ini/log files)
• Investigate process detection desync (inability to detect PID in some cases?) (Delayed to v1.06a)
• Look into improving the management of OSOL INI files for different games (mediating pre-launcher?)
• Explore implementing GloSC integration (Delayed to v1.07)

Battle.net launcher detection is busted

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.

Glyph launcher (Command line arguments)

I'm trying to get steam overlay in Archeage Unchained (not the steam version). Glyph launcher doesn't run archeage.exe, it instead runs EasyAntiCheat's launch_game.exe, which seems to then run archeage.exe passing some parameters (ex -eac_launcher_settings settings_64.json -t+auth_ip xxx.xx.xx.xxx -auth_port xxxx -handle xxxxxxxxxxxxxxxx -lang en_us -glyphid xxxx -lang en_us).

I've been looking into older issues and it seems that the CommandLineProxy/DetectedCommandLine functionality was the way to do that, but it has since been deprecated. Is there a new way to pass these command line parameters?

This is how I've set the OSOL ini.

[Paths]
LauncherPath=D:\Glyph\GlyphClientApp.exe
GamePath=D:\Glyph\Games\AAUnchained\Live\launch_game.exe
LauncherArgs=
LauncherURI=
GameArgs=
MonitorPath=D:\Glyph\Games\AAUnchained\Live\bin64\archeage.exe
PreLaunchExecPath=
PreLaunchExecArgs=
PostGameExecPath=
PostGameExecArgs=
[Options]
ReLaunch=True
SkipLauncher=False
CloseLauncher=True
AutoGameLaunch=True
MinimizeLauncher=False
ElevateExternals=False
PreGameLauncherWaitTime=15
PreGameWaitTime=0
PostGameWaitTime=0
ProcessAcquisitionTimeout=120
InterProcessAcquisitionTimeout=15
GameProcessAffinity=
GameProcessPriority=Normal
[Info]
ReleaseVersion=1.0.9.8

Dead Space 3 issue

I've got an AMD GPU, but disabled the relive overlay as well as the event overlay and I still cannot get this game to recognize my controller. I don't have any GPU tuning software aside from the AMD catalyst thing, so could something else be interfering?

Battle.net client broke URI launch

The battlenet:// URI no longer launches the game, you can see bnetlauncher quick n' dirty hack in the altlaunch branch.

Just letting you know.

Game freezing post launch

First of all — thanks for making this. It’s great to be able to play non-steam games with my family from my couch.

I’m trying to load the Outer Worlds using Epic Launcher and it freezes post launch on the Link. The game continues to run on my PC, but the link freezes. This happens about 15-20 seconds after the game opens (and it seems to be running fine for those 15 seconds).

Do you have any idea what could fix this? Happy to provide more information if needed.

Checklist for v1.08

• Investigate GOG launcher misbehaving sometimes
• Implement workaround for processes that lack a MainWindowHandle or MainWindowTitle
• Fix URI mode behavior for newer Origin/EGL/Uplay games
• More code cleanup for better readability
• First pass at implementing unit tests for testable methods and classes
• Implement better monitoring for both launcher and game processes
• Migrate to a development staging branch for safer git deployment
• Re-factor process detection to be less brittle when launchers update themselves
• Implement mediating pre-launcher GUI for better INI management (postponed)
• Investigate implementing hot-launching of native Steam games using OSOL
• Implement SkipLauncher for games that relaunch themselves via third-party launcher when called by Steam
• Implement better behavior for Battle.net (game launch commands)
• Fix broken LauncherURI code wrt Battle.net and friends
• Fix broken CommandlineProxy when detecting unix-style paths (e.g. UE4/UE3 engine)
• Deprecate SendEnterToLauncher INI option (workaround)
• Improve MainWindowHandle/ModuleHandle detection (Cemu SC Gyro/Electron workaround)

ETA: When it's done!

Auto-login offline?

Awesome - love how it shuts Origin after closing the game.

One thing though: I always run Origin offline, and it always makes me type my password. Is there any way your app could force Origin to auto-login, even when offline?

Issue with ReadMe.md/Instructions

In the "How to Use" Section of your readme.md, it clearly states "Run the OSOL .exe file from this directory." However, I do not see an OSOL.exe file. I do not see an executable file anywhere in the project.

Was it removed? Renamed? Is this step still necessary?

Keep Battle.net open but detect if game runs

Hey,

many thanks for this great work!
I'm wondering if it's possible to keep the Battle.net Launcher open but let OSOL detect if the is closed.
I don't want to close Battle.net to keep my games updated automatically by it.

Thanks

Tom

Task list for v1.09

• Massive process detection and monitoring rewrite (is now properly asynchronous).
• Refactored INI handling for better maintainability.
• Replaced ForceLauncher with AutoGameLaunch option and fixed bugs.
• Deprecated TerminateOSOLUponLaunch option (made obsolete by AutoGameLaunch).
• Some minor improvements for EGS detection and handling.
• Implemented PreGameWaitTime option for delaying game launch.
• Deprecated CommandlineProxy feature (how many people even used this?)
• Adjusted timeouts for new asynchronous launching/monitoring.
• Deprecated LauncherMode, OSOL will now automatically use LauncherURI for setting its mode.
• Implemented parent/child process tracking and validation.
• Implemented config migration from old to new version.
• Bug testing and unit tests to cover refactored code.
• Fix non-traditional launching/monitoring behavior (for Steam mostly).
• Fix EGL launching behavior when using LauncherURI mode.

Refresh system tray icons

I'm using OSOL to launch Origin game from Steam, set Origin as launcher and set a specific game to start, Origin can be killed in several seconds after game exited, this works perfectly except one, the Origin icon still exists in system tray until mouse hover.

So, is it possible to refresh system tray icons?

Checklist for v1.07

• Refresh system tray icons after closing the launcher PID
• Explore implementing GloSC integration (auto-adding GloSC/Steam shortcuts) (low priority atm)
• Change ProcessLauncher() to support tracking process trees so the user can track any set of executables - not just launchers (useful for Cemu + SC Gyro util)
• Implement copying command lines from a pre-existing launcher/game to OSOL to improve support for third-party launchers (Escape from Tarkov, some MMORPGs)
• Try to improve MinimizeLauncher behavior when exiting Origin games
• Implement option to not elevate external pre-post processes
• Enable DPI awareness for non-blurry rendering on HiDPI screens
• Add ForceLauncher option for use with CommandlineProxy for games that require the launcher to run in the background (Star Citizen, et al)
• PreGameLauncherWaitTime will now work in both LauncherMode=Normal and LauncherMode=URI
• Implement an option to terminate OSOL after launching a game
• Implement setting CPU affinity for the game process
• Implement setting Process Priority for the game process

Task list for 1.10

• Implement smarter launcher monitoring to better detect when updates are happening.
• Reengineer OSOL to exist in a single location and execute 'profiles' (represented by .ini files) containing application launch data.
• Implement a GUI that assists the user in setting up OSOL and managing this new profile system.
• Implement a dialog overlay to inform the user of what OSOL is doing before a game is launched and after a game exits (and allow the user to forcefully quit OSOL).
• Implement an auto-updater so the user doesn't need to redownload new versions from the project releases page manually.
• Investigate implementing launching of XGP (wrapped UWP) games (Not possible without implementing a ViGEm overlay, ala GloSC)
• Improve how OSOL handles Battle.net v2 launch paths
• Fix issue #48 and improve how OSOL handles blank paths

ETA: TBD

The Crew doesn't hook

Added The Crew executable as game exe, upc.exe as launcher. UPlay starts, The Crew starts, overlay doesn't get hooked in.

Disabled all other programs with overlay, tried with both UPlay overlay set on and off in UPlay settings

Using a Steam Controller, so can use that to somewhat diagnose. I set "desktop configuration in launcher" as off in steam controller options. I get my ingame config (can feel the joystick haptics) while still in overlay, got controller button prompts but controller buttons did nothing (found when UPlay warned me about not having UPlay overlay on). When game starts, Steam Controller switches back to desktop configuration.

Closing The Crew closes UPlay. as expected.

Launching Black Ops 4 doesn't work properly

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.

Close the launcher after the game has stopped running

Could we see a feature of closing the launcher, Origin, Epic Games, etc, after the game such as Apex Legends has been closed?

Currently steam still shows the game running until the launcher is closed.

Could we get a Patreon Page?

I would like to help out with a monthly or by update donation.

Epic Games Launcher URI Launching is broken in the most recent update to EGL

It seems like launching games from the Epic Games Launcher no longer works with the most recent update to EGL (10.1.2-6910972+++Portal+Release-Live). Looking at the EGL logs, it seems like the URI isn't being passed properly. The logs show

GoToUrl('/null')

whenever OSOL tries to launch a game via URI.

Allow Origin to sync

First of all. Thank you!!! Been looking for something like this for a long time :)

As for the "issue" - Origin doesn't seem to get the chance to sync files:

"Unable to sync Cloud Storage data"

"A recent sync with the cloud has been interrupted or a sync is currently in progress on another computer. Please try again later."

Would love an option to delay the client shut-down slightly to allow for syncing after closing a game.

Battle.net and Destiny 2: SC configuration only working for Battlenet not Destiny

I recently tried setting up my steam controller for Destiny 2 and I found my way here. I followed the directions from the readme for the normal set up as well as directions about battlenet in the Wiki.

Unfortanutely GLoSC does not work for me on my computer(have tried multiple times but just wont work).

I did the following:
1.OSOL in my battlenet folder,
2. Ran it and set the game and launcher path/executable
3. Changed the Launchermode to URI and put in the battlenet://DST2
4. Added it to steam and named it destiny 2 so I could pick the correct controller configuration

When I launch it, it opens Battlenet and my configuration is working in that screen. When Destiny 2 opens automically about 10 seconds later, it flips back to the desktop configuration

Ill admit I'm new to the SC and I notice in the wiki it says if you cant use GLoSC you must use the "desktop mode of BPM" I wasn't sure if that mean I can't run games from BPM or if I had to use the desktop configuration.

Confused at installing this

New to github I really want steam overlay in my games. I'm figuring out so many things right now I'm really stupid sorry. I downloaded git? Do I even need that? Cause I did try downloaded this and there was no executable file seen in the download...it's missing. I have windows 10 and I dont have winrar do I need that? I have .sln file popping up that looks exactly the same file you said to place in game directory but there is no exe to be seen. It's frustrating for me