WombatFromHell
WombatFromHell
You want to use GloSC for that. OSOL will most likely never have a way to launch UWP games.
https://github.com/WombatFromHell/OriginSteamOverlayLauncher/wiki/GloSC-or-Standalone
Just to verify, are you making sure to use the `EADesktop.exe` as the launcher target and `SkipLauncher=True`? (Edit: I think I see what you're talking about. In the process of...
It appears the defaults for OSOL are still the best middle-ground, but the issue where EA Desktop stops allowing launching is apparently very well known and related to a bug...
Had you tried moving the OSOL executable outside of the game's directory? Sometimes games/launchers have logic that prevents a non-game executable from launching inside the game's directory tree.
I’ll be getting some time for maintenance on OSOL soon so I’ll look into this and see what I can do.
I still use this app a few times a week, and I've not encountered any major issues for awhile with the launchers I use. Unfortunately, I don't really have time...
This is primarily an issue with the newer/newest EA launcher versions. It's believed to be a server-side check so there's nothing I can really do about it. Marking this as...
I've got some free time coming up to try a workaround for this issue. I believe it's related to how WMI queries handle single-quotes.
I may have fixed this issue in d1ca043806439f50bcbf89aa78bbc957da280875, but I'm not 100% sure. Try the v1.09j release on the Releases page and let me know if the behavior still occurs.