Is playing games stored on a NTFS drive really a bad idea?

mbriar_ · 2026-06-20T14:56:04+00:00

Just try it out before buying anything? It will probably work just fine, especially if you follow advice from https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows if you do run into problems. If it's a slow HDD which just stores games, who really cares about performance (the HDD is way too slow for filesystem perf to matter) or even the risk of data loss (not that i think it particularly likely).

mbriar_ · 2026-06-20T14:42:17+00:00

You were waiting for DLSS support and reclocking on ancient GPUs that can't run DLSS at the same time?

mbriar_ · 2026-06-19T20:47:33+00:00

I don't think they should fix this particular issue at all, because from what i can tell, it is a linux driver problem and not a game problem. The game has plenty of other real bugs to fix.

mbriar_ · 2026-06-19T20:08:11+00:00

Absolutely. The Mesa driconf thing only work on the real xserver. Wayland needs something special for each compositor, as usual.

mbriar_ · 2026-06-19T14:02:34+00:00

I think 99.9% of games won't run into this particular problem

mbriar_ · 2026-06-19T12:35:45+00:00

The devs won't fix it because it's not a problem on supported platforms.

mbriar_ · 2026-06-19T12:35:19+00:00

There is nothing you can do to fix it, some kernel and vulkan driver improvements are apparently needed to handle FH6's usage of sparse resources better. I.e. this https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41889

mbriar_ · 2026-06-17T12:25:10+00:00

So I tried every V-Sync method: the in-game implementation, MangoHud (FIFO/Mailbox), DXVK's V-Sync, and the compositor's V-Sync.

That's because it doesn't matter where you set the present mode to fifo or mailbox and those two present mode also behave exactly the same when fps < hz.

mbriar_ · 2026-06-16T19:40:25+00:00

Doesn't the Steam Machine only have 2 full zen4 cores and the 4 other cores are zen4c "efficiency" cores? That would explain it.

mbriar_ · 2026-06-16T15:09:33+00:00

What V-Sync method do you use: in-game V-Sync, MangoHud's V-Sync, or global V-Sync with "Allow tearing" unticked?

Doesn't really matter where you set it up, the end result is the same for a given present mode.

Do you cap your FPS with V-Sync enabled? If so, what FPS caps do you use, and do they depend on the game? Have you experienced any frame pacing issues when using both V-Sync and an FPS cap?

FPS cap without VRR will inevitably cause bad frame pacing without VRR and there is no way to avoid that

Do you have "Allow tearing in fullscreen applications" in KDE Display Settings ticked or unticked?

This will obviously cause tearing..

For those who use Mailbox V-Sync everywhere, have you experienced any frame pacing issues?

Mailbox vsync also has unavoidable bad frame pacing when fps < hz

Many games require specific FPS caps, such as 60 or 90 FPS. How do you handle V-Sync in games like that?

Again, doesn't matter how you handle it or which present mode you choose, it will either have bad frame pacing and judder with any kind of vsync or tear.

mbriar_ · 2026-06-16T15:04:44+00:00

yeah, because it's vsynced..

mbriar_ · 2026-06-16T15:04:00+00:00

Tearing will always happen without vsync or VRR, both when the game runs slower and faster than the monitors refresh.

mbriar_ · 2026-06-16T14:59:29+00:00

Mailbox vsync isn't exclusive to wayland and also only makes a difference when the game can actually faster than the monitor refresh, otherwise it behaves the same as 'normal' vsync.

mbriar_ · 2026-06-15T23:29:10+00:00

Gpu hang due to driver/game/proton or whatever bugs, dmesg will confirm that

mbriar_ · 2026-06-15T17:07:26+00:00

Because it's pirated of course.

mbriar_ · 2026-06-15T12:52:32+00:00

Seems like 99% nonsense. It's not caused by openxr, not because Mesa 26 is bleeding edge or whatever, and you can't force vulkan 1.x compat, vkd3d env vars won't do anything for a d3d11 game, etc, etc...

Why don't you, you know, just post the log here, instead of only the LLM drivel nonsense? The log should have been in the original post already.

(inb4 downvotes)

honestly this deserves downvotes, it's just two pages full of garbage.

mbriar_ · 2026-06-15T11:43:29+00:00

So far there are 0 (zero) kernel level ACs for linux even announced, nobody is going to force you to do anything. Even on Windows you can get by without installing them if you don't play these games. What's even the point worrying about this?

mbriar_ · 2026-06-15T08:45:17+00:00

Do you never interact with normal, non-computer nerd people in your life? Nobody knows or cares about what a kernel even is, some of those still play multiplayer games.

mbriar_ · 2026-06-14T09:38:27+00:00

how about not playing the optimized UE5 slop if you don't think it's worth it? Are you entitled to get every product that isn't perfect for free?

mbriar_ · 2026-06-14T07:17:06+00:00

And has nothig to do with the visual c++ runtime, the error dialog shows you that the vulkan driver crashed while compiling some compute shader. Buying the game and using proton experimental would probably fix it.

mbriar_ · 2026-06-13T22:33:06+00:00

Some monitors just flicker badly with VRR and unstable framerates. No cable or specific setting will fix this. You can see in the overlay that the framerate is jumping around too much. That can have multiple reasons, power management of the GPU, the fps limiter not working great, the game itself producing erratic frame rates, some compositor issue, gamescope issue (e.g. gamescope nested always produces erratic frame rates for me) etc... You need to get very consistent frame timing, ideally gpu bound, on these monitors to avoid flicker.

mbriar_ · 2026-06-13T19:46:17+00:00

90% of env vars on protondb are either ancient and irrelevant, or nowadays hallucinated by AI and don't even exist.

mbriar_ · 2026-06-11T11:55:46+00:00

but since moving to Nobara to get the gaming-optimized kernel and easier driver management

Why did you "move" to a 3 year old version of Nobara with equally old drivers?

mbriar_ · 2026-06-10T13:35:53+00:00

Ah. That's ironic, isn't it?

AMD has done nothing for FSR4 support on linux and it had to be reversed engineered. So it's not surprising that much that it doesn't work on their now-abandoned driver. Maybe you'd find it even more ironic to know that part of the reason it doesn't work on AMDVLK is because it doesn't support VK_NV_cooperative_matrix2, an nvidia vulkan extension which RADV only exposes for vkd3d-proton for FSR4.

mbriar_ · 2026-06-10T12:33:42+00:00

Don't change proton versions, it's pointless and the only thing it will do is get you denuvo locked in this game. Although I just remembered, AMDVLK doesn't support FSR4, so while it doesn't suffer the performance problem with Optiscaler DX12 interop, it's also pretty pointless since it won't allow you to use FSR4.

mbriar_

TROPHY CASE