Gamescope

[Lonsfor]

add ability to use the com.valvesoftware.Steam.Utility.gamescope extension and bump the runtime to 22.08
#50

[flathubbot]

Started test build 28091

[Lonsfor]

i runned into a rabbit hole but here it is.

@Eoin-ONeill-Yokai you are going to have to be the one to test it because i dont have wayland and the game comes out messed up.

use the env variables GAMESCOPE_ENABLE and GAMESCOPE_ARGS. so GAMESCOPE_ENABLE=1 flatpak run org.srb2kart also test srb2kart with -opengl and -software

[flathubbot]

Build 28091 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/10759/org.srb2.SRB2Kart.flatpakref

[Eoin-ONeill-Yokai]

I'll go ahead and test it out tonight.

[Eoin-ONeill-Yokai]

That works flawlessly.

Might be worth adding some default arguments to gamescope in the case that the user doesn't supply, specifically something like

-h 1080 -C 1000 -i

Which simply sets internal resolution to 1080p (the game is picky about resolutions it can run in, so best to force a known good one. You can see in the screenshot above that the top part of the screen is "stretching" and this can be solved by setting the internal renderer to 1080) hides the cursor after 1 second (just to keep the mouse cursor out of the way) and also applies a integer upscale when scaling (since it's the best upscale method for this type of game IMO). Otherwise it works great!

[Lonsfor]

what difference is there with setting -h 1080 and just changing the resolution withing the game?

[Eoin-ONeill-Yokai]

what difference is there with setting -h 1080 and just changing the resolution withing the game?

Well, the default launch options of SRB2Kart (on my system at least, I'm sure this will change from system to system) starts at 1280x800 which creates the following artifact at the top of the screen:

This can be solved by either changing resolution to 1280x720 for me.

Setting the internal resolution would mean that all users would be treated as having the same "monitor" and the results would then be scaled.

Regardless, this doesn't need to be fixed here necessarily -- it could be an upstream issue.

[flathubbot]

Started test build 29032

[Lonsfor]

i am having trouble visualizing what you said so i am just going to use your original suggestion and if someone else is having problems they can make an issue.

[flathubbot]

Build 29032 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/11696/org.srb2.SRB2Kart.flatpakref

[Lonsfor]

@ghisvail you still there?

[flathubbot]

Started test build 31529

[flathubbot]

Build 31529 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/14182/org.srb2.SRB2Kart.flatpakref

[Eoin-ONeill-Yokai]

Awesome, thanks again @Lonsfor and @ghisvail