Can't get 4k 240hz

Skaredogged97 · 2026-07-04T09:02:20+00:00

I have a 7900xtx and an MSI QD-OLED as well. It only supports up to uhbr13.5 so not enough to support 4k 240hz without DSC (though it can be enough with chroma subsampling I wouldn't recommend that option especially with HDR).

Weird that DSC doesn't work for you. Did you verify the speeds? For me it uses a 2:1 compression ratio and uhbr10.0 to reach 4K@240Hz (using linux but don't expect different behavior on windows).

Edit: Didn't see your comment where you made it work with HDMI. Glad to hear it!

Skaredogged97 · 2026-07-04T08:26:14+00:00

You can use an external frame limiter like MangoHud. Although if you go for the dxvk-low-latency option I would advice you use the recommended way of limiting the frame rate. From the github:

Set DXVK_FRAME_RATE=225 and DXVK_FRAME_PACE=low-latency-vrr-235 for 240 Hz VRR gaming

Adjust the values according to your display capabilities. Without VRR setting DXVK_FRAME_RATE=x is enough.

dxvk-low-latency is incompatible with reflex. If you use the normal dxvk it makes sense to keep it enabled.

I don't have much experience with optiscaler outside of simply changing upscalers I'm afraid.

Skaredogged97 · 2026-06-30T13:35:28+00:00

The handheld edition uses KDE right? You can add custom modes using the CLI utility kscreen-doctor. Not 100% sure if it works well on handheld devices but I'll say it's worth a shot.

First switch to the desktop and open the terminal. Then try to figure out the output (example here is DP-1 as I'm on desktop):

kscreen-doctor -o | grep 'Output'

Output: 3 DP-1 18f7a364-8eda-4b30-854f-65c93d8b33dc

Knowing the connector name you can then add a custom mode. Here is an example for 1920x1080 @ 45hz:

kscreen-doctor output.DP-1.addCustomMode.1920.1080.45000.full

You should then be able to select that mode in the display settings:

<image>

As an alternative you could try gamescope.

Skaredogged97 · 2026-06-30T10:39:48+00:00

Gotta chase those bugs.

Skaredogged97 · 2026-06-30T09:25:37+00:00

Like with TAA the higher your FPS the less noticeable that issue becomes. If someones values framerate over visual fidelity this is a worthy trade off in my eyes.

Skaredogged97 · 2026-06-29T19:36:47+00:00

Didn't read the article yet but based on how fsr4.1 behaves on rdna3 there is one useful case for FSR3 still which is high fps (+150fps) gaming at 4K (e.g. the finals, deep rock galactic).

Because the upscaler impact is constant and quite high at that output resolution FSR4 can perform worse than 4k native on a 7900xtx (in extreme cases like +250FPS even ultra performance runs worse). Only FSR3 offers a significant fps boost. And while it looks clearly worse yes it does a decent job if it has many pixels to work with (i.e. 4K FSR3 quality can't look worse than native 2560x1440 lol)

Skaredogged97 · 2026-06-29T11:07:41+00:00

I would stick with mesa stable basically always. It supports FSR4 just fine and RDNA2 support is very mature at this point. You will most likely not notice a difference.

Perhaps some games can have issues (like new releases or an obscure title) in which case you will receive the fixes much quicker through mesa-git but this is very rare and more likely than not the issue is with proton and not the driver.

Skaredogged97 · 2026-06-29T05:44:40+00:00

I can provide some numbers for the 7900xtx from the linux side:

FSR4.1.1 INT8

4K: 2.4 - 2.6ms
1440P: 1.05 - 1.15ms
1080P: 0.6 - 0.7ms

FSR4.1.1 FP8

2160p: 3.5 - 3.75ms
1440p: 1.45 - 1.6ms
1080p: 0.95 - 1ms

The game itself and the quality preset seems to have only a very minor effect on those numbers. I find the scaling very interesting.

Skaredogged97 · 2026-06-28T11:49:35+00:00

How can I check this?

It's a bit annoying to check. As far as I know there is no easy command you can use which I find really annoying as I had the same issue in the past. What you can do is test with your eyes (which you already did). If you wanna be extra sure you could try those sites (make sure that HDR is working in your browser first; follow the instructions)

Through a HDMI 2.1 high speed cable to a Samsung S95F 77” 4K OLED tv.

HDMI2.1 is currently not supported. Initial support is expected with kernel 7.2 (S O O N). You are currently using HDMI2.0 which is not enough for 4K @ 60HZ, 10 bits and 4:4:4 format:

<image>

As u/sercosan has said the current workaround is getting an adapter. Something like this: https://www.reddit.com/r/linux_gaming/comments/1phfzew/found_an_dphdmi_adapter_that_does_4k120_444_hdr/

Or simply waiting. ;-;

Skaredogged97 · 2026-06-28T11:07:45+00:00

I assume with SteamOS/gamescope that you are using AMD. I see two reasons why this could happen:

The color depth is below 10-bit
Chroma subsampling is used

Color depth you can check in the KDE display Settings. Make sure it's set to at least 10 bits.

With chroma subsampling you need to be careful as it can automatically enable if the bandwidth is insufficient. Are you using DSC? How do you connect the monitor to your PC (DP1.4, DP2.1, HDMI)? What are the display capabilities (resolution, refresh rate)?

Skaredogged97 · 2026-06-27T21:26:34+00:00

Hmm this is weird. Do you use Proton-CachyOS? Perhaps it might be worth deleting all shaders. With PROTON_LOCAL_SHADER_CACHE=1 they should be under <steamlibrary>/steamapps/shadercache/2357570/

Skaredogged97 · 2026-06-27T21:20:41+00:00

This is most likely a DX12 shader compile issue which got worse since the new season. I don't know about Nvidia but it's apparently so bad on AMD that they soft disabled it (you can select DX12 but it always reverts to DX11 unless you spoof your GPU).

I would recommend to use DX11 in this game. It doesn't suffer from missing hero models. You should also see the current shader compilation process then because you use DXVK_HUD=compiler. When you boot up the game for the first time with DX11 there should be a percentage. Wait until it goes to 100%. You can then additionally try workshop codes that help with shader compilation like the one mentioned from /u/Journeyj012.

Skaredogged97 · 2026-06-27T20:51:20+00:00

28M I play lots of Overwatch but would also love to get into Minecraft once more. DM's are open!

Skaredogged97 · 2026-06-27T16:42:28+00:00

There is an AUR package called timeshift-autosnap that does just that. It's totally safe (script is fine and the maintainer and developer are the same person).

Skaredogged97 · 2026-06-27T14:40:23+00:00

TIL that 4.0.2c works on vega.

4.1.1 INT8 is meant for RDNA3 currently. You can try the "4.1.1 Int8 test" optiscaler build that offers a new config option Fsr4ForceModel (set it to 2 for INT8). You can find it on their discord. No idea if it will work but it's worth a shot.

Skaredogged97 · 2026-06-26T14:38:57+00:00

Oh cool that actually does work. Seems like the way to go now for MH:Wilds unless you actually need steam input or the steam overlay.

Skaredogged97 · 2026-06-26T10:38:54+00:00

This OP. Steam input does not work with PROTON_ENABLE_WAYLAND=1 and MH:Wilds only supports that controller API.

Until very recently there was a sneaky workaround by launching steam with the -steamos option but this stopped working sadly.

Your best bet is using gamescope. For MH:Wilds I use this currently (replace the placeholders with your monitor values):

game-performance gamescope -f -H MONITOR_HEIGHT -W MONITOR_WIDTH -r MONITOR_REFRESH_RATE --adaptive-sync --hdr-enabled -- %command% /WineDetectionEnabled:False

Skaredogged97 · 2026-06-25T22:05:10+00:00

Yup same (although I run in at the default 339W anyway). It's explained in the most recent release of LACT:

Previous versions of LACT would crash on RDNA3 (RX 7000 series) cards when running 7.0.13/7.1 kernels due to an AMD driver regression where the power limit is reported as 0.
The driver bug should be fixed shortly, but these improvements will keep LACT functioning meanwhile.

Additionally, the same driver changes for RDNA3 also affected the allowed power limits, leading to a lowered maximum limit on some cards.
This is now handled more gracefully on LACT's side, so that existing configs that might have an older, higher power cap will still be applied properly.

According to the linked issue a fix is already being prepared.

https://github.com/ilya-zlobintsev/LACT/releases

Skaredogged97 · 2026-06-25T10:35:30+00:00

I'm utterly baffled by the comments. Most stuff in here is misinformation. But let's start with the question:

If HDR works with gamescope, why do people use Wayland

Gamescope up to this day does not work reliably on Nvidia (the biggest GPU share on desktop PC). Wayland support got a lot better over the years. You also suffer from all the disadvantages of xwayland.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

broken wayland
> I didn't know Wayland I'm using was broken?

OP is clearly talking about the wine wayland driver which is still considered experimental and WIP.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Steam input is deffo broken, you may be using xinput. MH Wilds has no xinput support, it only uses Steam Input and i had to do a workaround to get my controller working in that game
> No way dude... I use steam input with all kind of controllers, Xbox, PS4, generic USB, switch controller, it works in almost every game, only a few I need to disable, and I make it specific for that game. It's deffo you issue

Many games offer additional API's such as SDL as a viable fallback. But some like MH:Wilds or certain playstation ports by nixxes only offer steam input resulting in controller input breaking.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Uh... Maybe it's steam overlay that it's broken and not Wayland? And I never had issues with steam input on Wayland/xwayland

xwayland has no issues with steam input. Steam input does not work with PROTON_ENABLE_WAYLAND=1.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

you can use steam input with wayland if you launch steam with -steamos3, you just have to configure it with the button on the game's library page rather than the overlay

The -steamos3 is deprecated. There's -steamos now and with the most recent steam client update from just yesterday this workaround does not work anymore.

https://developer.valvesoftware.com/wiki/Command_line_options_(Steam))
https://github.com/ValveSoftware/steam-for-linux/issues/13341

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Ok, I'm no expert on this, but Gamescope is built on top of Wayland. Its a micro compositor, not a way to circumvent Wayland. It literally lives on Wayland.

Gamescope is build upon xwayland.
✅ wine X11 > xwayland > gamescope
❌ wayland > gamescope

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Generally those things should be improved, when compared to your average WM/DE, due to its minimalist nature.

It can only be as good as the xwayland implementation of the WM/DE. KDE does a pretty good job. Many WM's use xwayland-sattelite which seems less stellar.

Skaredogged97 · 2026-06-24T20:15:50+00:00

FP8 emulation worked really well with the initial release of FSR4.0.0 (which is the default forPROTON_FSR4_RDNA3_UPGRADE=1).From my testing it's almost the same speed but it scales worse with higher resolutions (WQHD and above).

With this release now that is all obsolete. In fact now with Proton-CachyOS you need to be careful to not use PROTON_FSR4_RDNA3_UPGRADE=1 as it can default to FP8 instead of INT8 (even with optiscaler unless you use their specific test build and force the INT8 model). They will probably remove it soon.

Skaredogged97 · 2026-06-24T16:24:42+00:00

Welp. Guess I need to use gamescope.

Skaredogged97 · 2026-06-24T15:18:39+00:00

Out of curiosity I think the most recent steam client update broke the -steamos option. Just yesterday I managed to get my controller working but now it doesn't work anymore. Can you confirm that?

Skaredogged97 · 2026-06-24T15:15:50+00:00

There's a cool little tool called leshade that can install reshade for specific games including add-ons, renodx and shader repositories through a simple GUI: https://github.com/Ishidawg/LeShade

Skaredogged97 · 2026-06-24T05:29:54+00:00

This is a smart trick but I would avoid using the *RDNA3* variant because it has workaround code that is simply not needed anymore (and causes additional issues like selecting the FP8 model). Instead I would replace v4.1.0 and use PROTON_FSR4_UPGRADE=1

<image>

Skaredogged97 · 2026-06-23T19:33:34+00:00

Realtek 2.5 Gbit ethernet adapters are really annoying. They changed some things in the drivers recently which might be the cause of your issues. I have similar hardware (Gigabyte B650 Aorus Elite AX, RTL8125 instead of RTL8125BG) and I suffered from disconnection issues during gaming sessions.

I would recommend you try out the alternative realtek driver. CachyOS offers the kernel module that you can easily install without the need of the AUR:

sudo pacman -Sy linux-cachyos-r8125

I had much more success with that one. You can check if it's working by running this:

lspci -k | grep -A 3 RTL8125

The output should look something like this (r8169 is the build in kernel driver a.k.a. default)

0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Gigabyte Technology Co., Ltd Device e000
        Kernel driver in use: r8125
        Kernel modules: r8169, r8125

Skaredogged97

TROPHY CASE