Crimson Desert on Linux

Just saved Pailune. Chapter 7, 139 hours in, and Crimson Desert has its hooks in me deep. Here's how the Linux launch actually went — crashes, workarounds, and the people who fixed it.

It Did Not “Just Work” #

Launch day on my RTX 5070 Ti: blue lens flare in the opening cutscene, then hard freeze. Audio kept going, GPU locked up. Every time. The 595 beta driver had a regression that crashed Blackwell cards at that exact moment.

I wasn’t alone — Proton issue #9595 filled up fast with the same crash. Nvidia 590 stable driver was the workaround. On Bazzite I had to roll back from stable to get it:

bazzite-rollback-helper rebase 43.20260303

I dropped that in the issue thread so other Bazzite users wouldn’t have to dig for it. That got me past the opening. But there was more.

Edge Flickering, Tree Artifacts, and the Fixes #

Once in-game, black outline flickering on high-detail models. Vegetation noise at 4K. Frame generation behaving weird. None of it was game-breaking, but it was all there.

The community chipped away at it. People tested Mesa versions, Proton forks, driver combinations, documented every quirk. Hans-Kristian tracked down a depth sync bug in vkd3d-proton and patched it. That fix killed the flickering for a lot of us. More PRs followed — descriptor heap fixes for 50-series crashes, barycentric workarounds for RDNA1.

This is the invisible work that makes Linux gaming possible. Not “click Play and forget” — but strangers sharing logs, compiling DLLs from source, and iterating until it runs clean.

The Game Itself #

Worth every workaround. The world is dense, combat is weighty, and I’ve lost hours climbing things I shouldn’t and staring at sunsets. Saving Pailune in Chapter 7 felt like a real milestone. Chapter 8 is calling.

Thanks to everyone in that issue thread — and especially Hans-Kristian — for making this possible. Now back to it.