Hitman 3 displayed with wrong height (1024px)
Hello, I'm new to gamescope and testing stuff, so not sure if it's a bug or if I'm doing something wrong.
I want to run Hitman 3 at 1920 × 1080, which is the native resolution of my screen. I use the following command in Steam:
gamescope -h 1080 -f -- %command%
When the game is started from Steam, it displays a small launcher window −which is fullscreen with gamescope (not a big deal)− then when the game itself launches it switches to 1920 × 1024 with some "ghost" graphics from the Steam interface. I've put a screenshot there: https://imgur.com/a/341EVcl
I've tried to set the full resolution for the game and gamescope (-w 1920 -h 1080 -W 1920 -H 1080) with no change. Also tried -b for a fullscreen window and the behavior is different: the panel from my desktop environment (XFCE) is kept on screen.
Resolution in game is set to 1920 × 1080, tried to change between windowed, fullscreen... but it doesn't change anything.
Tried an upscale just in case: game set at 1280 × 720 in its options, -h 720 -H 1080 for gamescope, same issue: I get 1024px in height.
Any idea of what I can try to get a proper display? I've tried another game (MultiVersus) with gamescope which displays fine.
Xubuntu 22.04 AMD Radeon RX 560 with Mesa 22.0.5 gamescope 3.11.32 (from ar-lex PPA)
I found a workaround just after posting, though it might confirm that it's a bug or a weird interaction: if I skip the launcher (there's a -skip_launcher option), the game starts directly and displays fine at 1920 × 1080 fullscreen.
So, I'm not sure what's happening: maybe the launcher steals focus and pass the wrong resolution to the game? or it has a fixed ratio (that goes to 1920 × 1024 when stretched to fullscreen) and despite displaying fullscreen it then pass that resolution to the game?
EDIT: weird thing: using the skip_launcher option works only once. If I quit Hitman 3 and try to relaunch it, it doesn't work until I re-enable the launcher. Then , if I remove it again, it'll launch properly once and so on...
One more thing: the issue might be specific to some DEs as I've just switched from XFCE to KDE and it doesn't seem to happen on the latter (with the launcher active).