Dark souls 2 sotfs stuck at 720p in gamescope [solved] - eviltoast

I’m trying to play dark souls 2 with the graphics overhaul mod in hdr. I’m passing 1440p to gamescope with the -W, -H, -w, -h options and limiting framerate to 60 with -r and -o.

The game just refuses to display at anything other than 720p. I can change the in-game resolution setting to 1440p but the resolution just doesn’t change. I tried setting a lower resolution (480p iirc) as well, but it still looked the same. Also tried enabling fullscreen but that setting doesn’t save nor does it do anything.

I’m inferring that it’s 720p because the in-game cursor moves half the distance of the actual cursor with gamescope set to 1440p, but they’re in sync if I set it to 720p. To the eye it just looks blurry. The mod menu opens at the size it opens without gamescope but is also similarly blurred. Couldn’t interact with it to confirm the resolution due to the aforementioned mouse issue

Outside of gamescope fullscreen works fine and the resolution setting works too iirc (but they reset after reopening the game). Kde plasma. Tried disabling secondary screen, setting scaling to 100 and limiting desktop fps to 60, didn’t help

Could this be some kind of steam deck detection? Any ideas?

  • Lojcs@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 months ago

    I feel silly for not thinking this… It works fine without the mod unless you try to change resolution/fullscreen settings.

    Apparently the mod is supposed to disable in-game resolution controls and force it to borderless window at monitor resolution when the flipmodel swapchain is enabled (which is necessary for hdr). It seems to do this by always launching the game in a 720p window and depending on if the custom swapchain is enabled it either resizes it to the screen or applies the in-game resolution setting. Gamescope doesn’t respond to the change and keeps outputting 720p in a 1440p window :/.

    I can’t wait for wine wayland

    Edit: Just found that using the --force-windows-fullscreen option fixes this issue!!