Games running on 720p instead of native 1080p
On latest bazzite with proton ge 10-10 in lutris
I have a game (redout) that always starts in 720p. if i start the game in gamescope with 1080p command the game won't launch. Any tips on how to get to 1080p?
I have this with mutiple games... for example redout like i said, and redout 2. But however for redout 2 it doesnt crash with gamescope and the issue is fixed that way for that game...
So how can I fix it if a game can't do gamescope..?
I tried changing GameUserSettings.ini in the prefix of redout. but it doesnt seem to do anything still 720p
Now i also have this issue with Rise of the tombraider, Then I switched in gamescope from fullscreen to windowed and suddenly it worked..
then i check for redout. and yes it also works in windowed! however not for fullscreen still... and when i retried i couldnt get windowed working either...
1 Reply
The errors seem to be the samea= across mutiple when gamescope won't launch with the game:
failed to read Wayland events: Connection reset by peer
err: Presenter: Failed to create Vulkan surface: VK_ERROR_OUT_OF_HOST_MEMORY
err: Failed to create Vulkan surface, VK_ERROR_OUT_OF_HOST_MEMORY
err: DXGI: CreateSwapChainForHwnd: Failed to create swap chain, hr -2147467259
X connection to :1 broken (explicit kill or server shutdown).
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 63 requests (63 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 125 requests (125 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 72 requests (72 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 72 requests (72 known processed) with 0 events remaining.
after 77 requests (77 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 72 requests (72 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 72 requests (72 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 284 requests (284 known processed) with 0 events remaining.
XIO: fatal IO error 110 (Connection timed out) on X server ":1"
after 125 requests (125 known processed) with 0 events remaining.
Initial process has exited (return code: 134)