This is similar to the bug reported in Display/game resolution issue, but I haven’t gone through the re-installation process (yet). I’m running a 4K monitor with a RTX 2080, but all of my games have their maximum resolutions set to 2259x1271, which is a rather odd resolution.
My desktop resolution is set properly to 3840x2160, so I’m not sure what the problem is. Running KDE Plasma, and the open source NVIDIA drivers. Should I switch to the proprietary drivers? I just switched over from Pop!_OS, and I was getting the proper 3840x2160 resolution in game there, and that is the proprietary drivers which is the only thing I can think of that might be causing it.
The culprit is very often, that you have scaling enabled to f.e. 125% or 150% and that is also used in games. Set it back to 100% and try again…
That makes a lot of sense, and yeah when I changed the scaling from 170% to 100% the resolution in game went back to what I’d expect. Thank you, I didn’t even think of that.
Now if only the game knew my monitor was capable of HDR, and not just “generic monitor” that would be perfect. Ah well, I’m sure that’ll come in the future.
For HDR, use Proton GE or CachyOS.
Prerequisites:
AMD/Intel Mesa 25.1 minimum
Nvidia Install vk-hdr-layer
Wine Wayland driver
AMD/Intel
PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
Nvidia
PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 ENABLE_HDR_WSI=1 %command%
I’m guessing vk-hdr-layer isn’t installed by default which is why you’re telling me to install it, then I just need to add those flags to, for example, Diablo 4 and it should work?
And yeah, I’m using the 20250601 CachyOS Proton.
EDIT: I’m not finding vk-hdr-layer when trying to run pacman -S vk-hdr-layer.
If I remember correctly, you can install it with Octopi and enabling the AUR. Otherwise, you can install it yourself from here
https://aur.archlinux.org/packages/vk-hdr-layer-kwin6-git
Once it is installed, ENABLE_HDR_WSI=1 activates it. If Diablo 4 works with the Wine Wayland driver, it should work.
I got vk-hdr-layer installed, but unfortunately the game freezes as soon as I start it up with those options added to the command line. I’ve seen others talking about it working on reddit when searching, so I must have done something wrong.
Ahh, forgot to mention the Nvidia Wayland bug. Sorry about that!
Add this to your launch options:
VKD3D_DISABLE_EXTENSIONS=VK_KHR_present_wait %command%
You only need one %command%. I just put it in there to show where the command needs to go either before it or after.
Yeah, that did it. Thanks!
That is a bit weird. I’m honestly still not sure which package caused it but after reinstallation, everything was fine. I’m about to move up to a dual 1440p/4K monitor soon. I’m hoping I won’t have to do it again lol. I didn’t consider the scaling aspect of it and I’ll have to keep that in mind if I ever see the problem come up again.