DOOM: The Dark Ages (3017860)

[matte-schwartz]

Compatibility Report

• Name of the game with compatibility issues: DOOM: The Dark Ages
• Steam AppID of the game: 3017860

System Information

• GPU: RTX 5090
• Video driver version: 575.51.02
• Kernel version: 6.14.5
• Link to full system information report as Gist: https://gist.github.com/matte-schwartz/c76d16c770e563ba28b102ebfa7184bf
• Proton version: experimental-10.0-20250509

I confirm:

• [X] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

Symptoms

With Gamescope: After enabling any level of DLSS Frame Generation within the game, the game crashes to desktop.

Without Gamescope: After enabling any level of DLSS Frame Generation, the game crashes if you alt+tab.

Other:

The colorspace with HDR enabled looks purple if DLSS Frame Generation is also enabled.

Frame Generation Off	Frame Generation On

• Proton log: steam-3017860.tar.gz. This log was captured after it had already crashed after enabling DLSS frame generation, then I subsequently disabled it and enabled it once again to get it to crash.

Reproduction

1. Launch the game on a NVIDIA GPU
2. Go into the graphics settings and enable DLSS Frame Generation

The game should crash at this point if you alt+tab a few times, or if you are running the game under Gamescope.

[SimpleHeuristics]

On Bazzite with 570.144 Proton Experimental bleeding edge the game will launch via the desktop steam client without frame generation and HDR. The color space will be completely wrong however as mentioned above even when it's running in SDR (everything Magenta).

Under Gamescope session the game will crash before loading the actual menu if frame gen is enabled but works fine with HDR enabled without frame generation. DLSS super resolution is Working as well.

[SuperMewio]

Game crashes to desktop on my AMD machine during the first bethesda logo cutscene. I have seen the same reports on the Linux_Gaming reddit. Tested with Experimental Bleeding Edge and Hotfix.

Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550 AORUS ELITE AX V2

steam-3017860.tar.gz

[robzombie91]

No major issues so far with me. Only issue is DLSS, which causes the game to go purple/pink and enabling fsr on my 5080 causes the game to display a black screen but with audio working

Kernel: 6.14.6 CPU: intel 12600k Gpu: Nvidia RTX 5080 Driver: 570.144 Proton experimental bleeding edge

[nuudlman]

For RADV, I think the issue is enabling options to make it compatible. It seems like this already happened for the steam deck, but I have no idea how to do this for desktops

[Nyvyme]

For RADV, I think the issue is enabling options to make it compatible. It seems like this already happened for the steam deck, but I have no idea how to do this for desktops

Can you please tell us where it can be done?

[keithallenjackson]

Game crashes to desktop on my AMD machine during the first bethesda logo cutscene. I have seen the same reports on the Linux_Gaming reddit. Tested with Experimental Bleeding Edge and Hotfix.

Operating System: Arch Linux KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Kernel Version: 6.14.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X3D 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550 AORUS ELITE AX V2

steam-3017860.tar.gz

Same issue I am having. AMD Radeon 6800XT, Fedora 42, latest updates. No iGPU at all.

For RADV, I think the issue is enabling options to make it compatible. It seems like this already happened for the steam deck, but I have no idea how to do this for desktops

Can you please tell us where it can be done?

I tried putting the option names as environment variables (just a wild guess), and it didn't work. (shrug)

[nuudlman]

I figured out that those options come from 00-radv-defaults.conf: https://github.com/bazzite-org/mesa/blob/54cf223f100a114680f51f43f5dfc632eeeefb3b/src/util/00-radv-defaults.conf#L126-L131. It was in /usr/share/drirc.d/00-radv-defaults.conf for me, and I added the entry for doom there, but the game still crashes at the bethesda logo.

steam-3017860.tar.gz

[DoomSlinger]

For RADV, I think the issue is enabling options to make it compatible. It seems like this already happened for the steam deck, but I have no idea how to do this for desktops

Can you please tell us where it can be done?

I tried adding these parameters in the launch options, the game still crashes, but with those options I get a boat load of artifacting.

[Nyvyme]

I figured out that those options come from 00-radv-defaults.conf: https://github.com/bazzite-org/mesa/blob/54cf223f100a114680f51f43f5dfc632eeeefb3b/src/util/00-radv-defaults.conf#L126-L131. It was in /usr/share/drirc.d/00-radv-defaults.conf for me, and I added the entry for doom there, but the game still crashes at the bethesda logo.

steam-3017860.tar.gz

Sad that I can't test it right now because Denuvo banned me for 24 hours because I was trying to launch game with different Proton versions.

I can't understand it. They removed Denuvo from Doom Eternal but re-added it in TDA.

[DoomSlinger]

Sad that I can't test it right now because Denuvo banned me for 24 hours because I was trying to launch game with different Proton versions.

I can't understand it. They removed Denuvo from Doom Eternal but re-added it in TDA.

They put Denuvo on there for the first few weeks to protect initial sales until the game gets cracked. They will probably remove it later with this game as well.

EDIT: Also, you have to remember that when DOOM eternal released, they accidentally released the denuvo free version on the bethesda launcher, meaning there was no point in keeping it at that point.

[matte-schwartz]

Regarding running the game under RADV:

Before you're able to apply all of those settings in 00-radv-defaults.conf, you need to make sure your Mesa version has the patch that implements radv_force_64k_sparse_alignment. Right now this patch is only available in Valve's Mesa tree from SteamOS unless it's been cherry-picked into your Mesa build.

I took these from Valve's tree via SteamOS's Mesa source package and rebased them for mesa-25.1.0: https://github.com/matte-schwartz/mesa/commit/8119f91113b775afe34cdf980550425639bab7cd and https://github.com/matte-schwartz/mesa/commit/17676b7686aa3f99a4132656376c62e6f5360c4b, and now I can run the game on my 7900XTX rig

[DoomSlinger]

Replying to https://github.com/ValveSoftware/Proton/issues/8690#issuecomment-2874956966

Is this a complete fork for mesa or just the files that needed to be changed? Tried compiling it and installing it but it didn't seem to install.

[matte-schwartz]

I use the Mesa-git pkgbuild and just saved those two commits as individual patches. Up to you how you want to apply them. Mostly posted them there for better visibility than the source tarball they came from.

[ColinSalem]

If anyone wants more specific instructions, this is a diff of the PKGBUILD that I had after making changes that worked for me.

15c15
< pkgver=25.2.0_devel.204321.de6efc01c12.d41d8cd
---
> pkgver=25.1.0.204437.e8011985b02.d072636
94c94,96
<     'mesa::git+https://gitlab.freedesktop.org/mesa/mesa.git#branch=main'
---
>     'mesa::git+https://gitlab.freedesktop.org/mesa/mesa.git#branch=25.1'
>     'tda-workarounds.patch::https://github.com/matte-schwartz/mesa/commit/17676b7686aa3f99a4132656376c62e6f5360c4b.patch'
>     'radv-force-64k-sparse-alignment.patch::https://github.com/matte-schwartz/mesa/commit/8119f91113b775afe34cdf980550425639bab7cd.patch'
97a100,101
>             'SKIP'
>             'SKIP'
103a108,109
>         'SKIP'
>         'SKIP'

[DoomSlinger]

I use the Mesa-git pkgbuild and just saved those two commits as individual patches. Up to you how you want to apply them. Mostly posted them there for better visibility than the source tarball they came from.

Got it working, haven't ever patched a PKGBUILD before so had trouble figuring this out. Thanks for posting the patch!

[ZacharyVarney]

@DoomSlinger would you mind pointing me in the right direction, never really have patched a pkgbuild before either

[keithallenjackson]

Just tried this on my RTX 4070 Laptop running Fedora 42 (latest updates). Everything worked well with Steam defaults. Seems Mesa is the biggest issue causing AMD card users the crashing issues.

I haven't tried any of the original posts issues (DLSS frame gen), but overall the game is playable on nvidia hardware.

[alosarjos]

@matte-schwartz Thanks a lot for that, got it working!

Though I'm not sure what did I touch the first time that completely broke the menu of the game, not sure if it was frame gen. Had to delete the prefix to get it working

Curiously, I don't see any commit / MR / Issue on upstream mesa...

Are these patches some workaround for something that ID will fix on their end?

I don't see any other reason for Valve not reporting/fixing it there 🤔

[bsmntoid]

Can confirm that the game does work on my 7900XT Arch Linux system after installing mesa with the diff ColinSalem posted. For readers who aren't sure what to do with it, here's the steps I took:

1. Clone the mesa-git repository from the AUR (git clone https://aur.archlinux.org/mesa-git)
2. Move into the newly created directory
3. Create a file named tda.patch and paste in the diff
4. Apply the patch with patch PKGBUILD < tda.patch
5. Compile and install with makepkg -sic

Enabling FSR frame generation gave me a black screen, and after deleting my prefix to try and reset my settings I've unfortunately tripped Denuvo's activation limit.

[pixelcluster]

Curiously, I don't see any commit / MR / Issue on upstream mesa...

It's up now: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34944

[ZacharyVarney]

@bsmntoid I'm in the same situation as you with black screen on FSR Frame Gen, but I haven't tripped Denuvo & trying to avoid that.

[alosarjos]

@bsmntoid I'm in the same situation as you with black screen on FSR Frame Gen, but I haven't tried Denuvo & trying to avoid that.

Disable temporally cloud-saves and delete the prefix to go back to default config

[ZacharyVarney]

@alosarjos Wouldn't deleting the prefix be what trips Denuvo?

[alosarjos]

@alosarjos Wouldn't deleting the prefix be what trips Denuvo?

Yes, you can only do it like 5 times a day max or something like that. For one time there is no problem

[bsmntoid]

If you DO trip Denuvo, the game will still work if you play it on another Steam account via family sharing.

[ferrreo]

FSR framegen does indeed result in a blackscreen. Struggling to disable it too, deleting the prefix didn't work, validating files didn't work. Anyone got any ideas?

[alosarjos]

FSR framegen does indeed result in a blackscreen. Struggling to disable it too, deleting the prefix didn't work, validating files didn't work. Anyone got any ideas?

Disable cloud saves first and then delete the prefix

[ferrreo]

FSR framegen does indeed result in a blackscreen. Struggling to disable it too, deleting the prefix didn't work, validating files didn't work. Anyone got any ideas?

Disable cloud saves first and then delete the prefix

Still not resetting my config

Edit:

Looks like you need to disable cloud saves, close steam, delete the prefix and delete the local cloud save data. At least I had to.

[robzombie91]

The way I fixed the fsr issue on nvidia was by deleting the amd fx fidelity DLL and then restarting the game

[curtmgray]

Replying to https://github.com/ValveSoftware/Proton/issues/8690#issue-3058471061

I'm running into similar issues here, enabling DLSS Frame Gen causes purple screen. HDR doesn't need to be enabled though for it to occur.