What does the Doom log say?

steamapps/compatdata/379720/pfx/drive_c/users/steamuser/Saved Games/id Software/DOOM/base/Error*

.../Saved Games/id Software/ does not exist.

The demo uses denuvo AFAIK. It was dropped in the retail.

@maiself Oh derp. That appid is Doom retail and not for the demo. Seems @LeJimster may be on the right track.

Hi, I tried to run Doom 2016 on Ubuntu 18.04.1, but I couldn't. I share all info I could get from my system and the bug showed by Wine. I hope it helps to improve the support of Steam Play/Proton.

This is the basic configuration of my system:

-Ubuntu 18.04.1
-Motherboard: ROG STRIX X370-F GAMING
-CPU: AMD Ryzen 7 1700 Eight-Core Processor
-RAM: 32GB DDR4 3.200GHz.
-GPU: Nitro+ Radeon RX 580 from Sapphire

Fallo Doom Steam Play.zip

@cold-distance Please search the other Doom issues. Yours is because you are trying to use OpenGL. Setting it to Vulkan should work.

https://github.com/ValveSoftware/Proton/issues/488

@parkerlreed Thank you. It seems that Mesa lacks of a OpenGL extension that Windows has. I hope that Mesa corrects that in the future. I will try force the execution with Vulkan.

@cold-distance It is implemented. Vulkan is preferred for Doom anyways.

If you want to do OpenGL, you need Mesa 18.2 or newer.

Hi. kisak-valve just recently transferred my issue here. (Thanks.) I understood Proton is using Vulkan internally. I'm happy to use whatever works! Let me know if there is any other info I can provide.

I successfully played the demo from start to finish. That was on OpenGL.
However, the demo crashes when attempting to use Vulkan.

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG STRIX B550-A GAMING
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 5600G with Radeon Graphics
CPU Family: 0x19
CPU Model: 0x50
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4463 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"NixOS 23.11 (Tapir)" (64 bit)
Kernel Name: Linux
Kernel Version: 6.3.5-xanmod1
X Server Vendor: The X.Org Foundation
X Server Release: 12301001
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20230509.49499
Video Card:
Driver: AMD AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.52, 6.3.5-xanmod1)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.1
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 143 Hz
VendorID: 0x1002
DeviceID: 0x73df
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 2560 x 1440
Primary Display Size: 23.62" x 13.39" (27.13" diag), 60.0cm x 34.0cm (68.9cm diag)
Primary VRAM: 12288 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 15793 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 476427 MB
Largest Free Hard Disk Block: 82988 MB
Storage:
Number of SSDs: 1
SSD sizes: 500G
Number of HDDs: 0
Number of removable drives: 0

Steam Runtime Diagnostics: https://gist.github.com/SuperSamus/a25ac4d9e170c8907ec40301edbe5f77

Crashing on Vulkan is still an issue.
Though, apparently, this is an issue on Windows as well, so... nevermind.
https://community.amd.com/t5/drivers-software/doom-not-loading-7850-17-12-2/td-p/268523

PC Wiki says that "in the Demo Vulkan is completely not functional".
https://www.pcgamingwiki.com/wiki/Doom_(2016)#Crash_on_startup_after_switching_to_Vulkan_API
The easiest way to revert to OpenGL is to add +r_renderapi 0 as a launch option. It works both on the Demo and the full game.

PC Wiki says that "in the Demo Vulkan is completely not functional". https://www.pcgamingwiki.com/wiki/Doom_(2016)#Crash_on_startup_after_switching_to_Vulkan_API The easiest way to revert to OpenGL is to add +r_renderapi 0 as a launch option. It works both on the Demo and the full game.

For the sake of avoiding circular reporting, the one who added the note to the PCGW article is me.

I am gonna keep this one message short without uploading 9 immages:

In the Demo, Anti Aliasing doesn't seem to work, or it's worse at its job.
Granted, I am on Linux, but it shouldn't change anything nowadays... (It could be that OpenGL is bugged, but I don't have the health to test this one out properly, I have a chronic illness and little health to spare these weeks.)
Checking this on W10/11 is easy and quick, but I can't right now. This room is the easiest to get to for anyone and is a great test for performance overall; I'd advice using it for tests.

I've double-checked if Sharpening at 1.0 would be at fault, but no, it just accentuates the lack of AA.

Here's the screenshots from the Demo, with No AA and with TSSAA 8TX:

Here's the ones from the game proper, on Vulkan:

If the images got compressed it may be more difficult to check, but you can see that altho edges are better defined compared to their respective No AA defaults, the Demo's has way more aliasing just... everywhere.

I run DOOM 2016 at relatively low settings because I don't really need to raise them, I also prefer to get more fps rather then "a puddle of goo with 3x more details". The Demo instead defaulted to a mix of Medium and Ultra settings, so I left it as it was.
(I am running the tests before finishing the update on my Fedora KDE PC, and also it went into sleep mode a couple of times and had other programs in the background, so the "not expected performance" is due to that.)

Indeed after the update, reboot, and running the game alone, this is the performance.