Star Citizen's launcher starts behind main game
pquerner opened this issue · comments
Hello!
Is it possible to filter application by name, for example by exact .exe name or otherwise?
Sometimes applications sit behind a launcher and these launchers cannot be avoided.
For example "Star Citizen". The launcher launches an OAuth login which then is saved to a local file. The real application - the game - then reads that credential file or otherwise gets told that it should look for the file and thus allows a game session to connect.
Without a filter you would also possible target the launcher - which may or may not be wanted.
With a filter you'd have the tool to work around above described issue.
Thanks for reading.
Hello @pquerner, this request is entirely unrelated to gamescope and not platform specific as well. You'll want to post this on the community forums at https://steamcommunity.com/discussions/forum/10/.
Hello kisak,
I dont understand how its unrelated to this repo.
But thanks for consideration.
Sorry, I misread the intent of this issue report. It should be focusing on Star Citizen's (mis-)behavior with the game's startup sequence.
Hello,
I still don't think its correct. What can I do to clarify it more? :)
The launcher of Star Citizen does not start behind main game.
But when you run gamescope with the launcher (because thats the only way afaik how you are able to run the actual game), you would end up affecting the launcher (if you want to render it at 720p and scale up; while only the main game should've been affected) - which you probably didnt intend.
gamescope should've only work on the game - not its launcher.