I am experiencing a severe rendering issue in Doom: The Dark Ages. When I enable the "Frame Generation" setting, the display immediately freezes or goes to a black screen. However, the game has not crashed; the background audio continues playing normally, and UI interaction sounds can still be heard.
Interestingly, Path Tracing and all other settings at "Ultra Nightmare" work perfectly fine at 4K resolution. The crash is strictly isolated to the Frame Generation toggle.
Steps to Reproduce:
Launch Doom: The Dark Ages via Proton.
Go to Video Settings.
Enable FSR and toggle "Frame Generation" ON.
The screen goes black immediately, but audio continues.
System Information (From In-Game Benchmark):
OS: Ubuntu 26.04 (Running via Steam Proton)
CPU: AMD Ryzen 7 7700X 8-Core Processor
GPU: AMD Radeon RX 9070 XT
Vulkan Driver: RADV GFX1201
Mesa Version: Mesa 26.0.3-1ubuntu1
Resolution: 3840 x 2160 @ 60Hz
System RAM: 32 GB
Please let me know if you need any specific Proton logs (PROTON_LOG=1) or Vulkan API traces to help debug this issue.
Hello,
I am experiencing a severe rendering issue in Doom: The Dark Ages. When I enable the "Frame Generation" setting, the display immediately freezes or goes to a black screen. However, the game has not crashed; the background audio continues playing normally, and UI interaction sounds can still be heard.
Interestingly, Path Tracing and all other settings at "Ultra Nightmare" work perfectly fine at 4K resolution. The crash is strictly isolated to the Frame Generation toggle.
Steps to Reproduce:
Launch Doom: The Dark Ages via Proton.
Go to Video Settings.
Enable FSR and toggle "Frame Generation" ON.
The screen goes black immediately, but audio continues.
System Information (From In-Game Benchmark):
OS: Ubuntu 26.04 (Running via Steam Proton)
CPU: AMD Ryzen 7 7700X 8-Core Processor
GPU: AMD Radeon RX 9070 XT
Vulkan Driver: RADV GFX1201
Mesa Version: Mesa 26.0.3-1ubuntu1
Resolution: 3840 x 2160 @ 60Hz
System RAM: 32 GB
Please let me know if you need any specific Proton logs (PROTON_LOG=1) or Vulkan API traces to help debug this issue.