![]() ![]() If you experience crashes when starting OSOL and are running Windows 7, make sure you install the. 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. Optional: for advanced functionality or compatibility options for particular launchers see the OSOL project Wiki.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).Name this new non-Steam game shortcut of OSOL (in Steam) whatever you like (such as your game's name).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 from this directory and it will prompt you to choose the path to your game executable (required) and the game launcher (which is optional). exe file from the OSOL archive into the game directory (where the game's executable is located for example). If you have trouble running it, or are running Windows 8 or earlier, you may need to download and install the. It also can simply be deleted if you wish to uninstall it at any time. This wrapper requires no installation other than copying it into the directory of the game executable you wish to run through Steam BPM/Overlay. OSOL currently supports the following launchers:, UPlay, Origin, GOG Galaxy, Epic Games Launcher, Steam, and most Emulators/Master Launchers that call a game's executable file. See the OSOL project wiki for more details about this and other application specific notes. 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).Īside from the most common mainstream launchers mentioned previously OSOL is also compatible with the vast majority of emulators and even some MMORPG/MMOFPS launchers. ![]() 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, Origin, or UPlay) then you know how annoying this combination can be. Practically exactly what I said in pieces in July plus the compatibility mode (which I personally don't need on my Windows 10) and some different browser protocol as Origin's launch argument?ĮDIT: And the different protocol is likely due to the different gameĭo you know the product_ID for Battlefield 1 Beta? I can't figure out how to find it.OSOL (O.rigin S.team O.verlay L.auncher) Why should I use OSOL Hope it works for you as well!!! Enjoy! So. Whoever finds this, sorry that i didn't link it everywhre.) Ursprünglich geschrieben von Benja:Okay I will post MY SOLUTION here and link to here from other posts (there are far to many posts with the same problem to be found. Probably not the only solution but the only one working for me I found in 2 days. start steam and click on the edited origin shortcut (in steam).go to properties->compatibility and activate the Win7 compatibility mode make sure origin is not running when you start a origin game from steam.Change name to "Star Wars Battlefront".The whole thing that is copy+pasted is the launch protocol for Origin games (Steam uses a similar one that is utilized when you create desktop shortcuts of games). Origin.OFR.50.0000940 is the game's product ID for Origin (this can be found by going to the game's webpage at and searching the source code of the webpage for "product_ID". In the target box, after "C.\Origin.exe" add a space and copy+paste: origin://launchgame/Origin.OFR.50.0000940 (no quotes).Right-click the newly added shortcut in Steam and select properties. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |