Doom Eternal (782330)

[kisak-valve]

Due to the early flood of feedback for Doom Eternal while the community figured out how to get this game to run, the discussion for this game has been reset. If you have an interest in the community efforts made to run this game, feel free to read #3654.

Known hard requirements:

Proton 5.0-6 or newer
Mesa 20.0.3 / LLVM 9.0 (AMD only) (or equivilant AMDVLK / AMDGPU-PRO) (RADV/ACO needs 20.1+)
nVidia 440.82 (nVidia only, mildly older drivers may work with degraded performance.)
vulkan-icd-loader 1.2.135 (This is provided by the Steam runtime. Drivers can report support for an older vulkan spec and that is okay.)

Known Quirks:

As of this writing, Denuvo is having a hard time with something in Wine-Staging, and third party Proton builds based on that may hit a 24 hour lockout after 5 runs per day.
Steam overlay degrades performance when visible. Improved Steam Overlay and FPS counter performance for games using Vulkan async compute (such as DOOM Eternal). in the 2020-04-16 Steam client beta update.
Alt-Tab may break the game rendering.

Tinkerer guides:

Please do not re-post tinker guides in this issue report. If you have one to share, please put it in a gist and request that the gist be shared in this section.

[poperigby]

I'm getting a hard crash that seems to happen after 30 minutes or so. Here's the log file:
https://send.firefox.com/download/945b855f1dd20e0d/#dP9yXbTc4PGFlF5mkZL1EQ

I have a RX 5700XT and am using ArchLinux with RADV.

[kisak-valve]

Hello @poperigby, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

As a side note, Proton logs are known to compress well, please consider throwing large logs into an archive.

[poperigby]

Here's the system information gist: https://gist.github.com/PopeRigby/263d2b99e3998f99fdf4e0d222845843

[jjbarr]

So does ACO work on Mesa 20.1 now? Last I heard ACO was not working.

[silviucc]

Is it still true that enabling the overlay causes performance issues?

My own experience shows the opposite:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394/30?u=silviu_c

[btegs]

@btegs, removing the pinned_libs_* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system.

Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf

Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool.

Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either.

What is going on and what steps are missing?

NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!

[tyqualters]

"Alt-Tab may break the game rendering."
Arch Linux with KDE Plasma, can confirm Alt-Tabbing broke game rendering, but it also resulted in unresponsiveness to the close procedure by right clicking the process in the task bar and clicking the "Close" button..
sudo kill -SIGHUP 31117 did close the game though
System Information: https://pastebin.com/1z80Y7WG

[poperigby]

My hard crash seems to be happening after about 20 minutes every time I start the game. Maybe I could time it to check.

[Emanem]

Adding bugs (perhaps obvious/already known):

• have to skip initial intro logo ("+in_terminal 1 +com_skipIntroVideo 1")
• audio is crackling a little bit sometime (have to increase pulseaudio sampling to 48 kHz)
• multiplayer doesn't work (this is bad)

[DarkArc]

This game is also seems to be affected by #2927

If you're having problems, and you have a Ryzen 3xxx processor, try the workaround there ^

[kisak-valve]

Doom Eternal Monitor/Resolution fail

Issue transferred from #3797.
@Kalevr1 posted on 2020-04-24T23:18:50:

Compatibility Report

• Name of the game with compatibility issues: Doom Eternal
• Steam AppID of the game: 782330

System Information

• GPU: RTX 2060 SUPER
• Driver/LLVM version: 4.6.0 NVIDIA 440.82
• Kernel version: 5.5.6
• Link to full system information report: https://gist.github.com/Kalevr1/6f5f51d29cc2e60e370c7dda858ace34
• Proton version: 5.0-6

I confirm:

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

steam-782330.log.zip

Symptoms

After installing latest SteamPlay Proton 5.06 I got one perfect play session that lasted several hours. I took a break to eat and then came back to continue play. I have a 2 monitor setup. When I tried to launch the game a second time, it switched to a small window on the the secondary monitor. The lower monitor is my default screen and sits at eye level. I can see the upper left corner of the Doom Intro being rendered within the quarter-sized window on the secondary monitor. The game engine thinks it is rendering on the entire screen but I only see the portion that overlaps the window. I can see 2 buttons in the UI and I can interact with them. I Alt-F4 to exit.

Seems fixable if I can manually force the monitor and resolution for the app but I don't know if that would work. One workaround I have found is if I delete ../steamapps/compatdata/782330 the game does 'first run' again, which always runs perfectly.

I have included a screenshot of both monitors (1920x2160 pixels). Steam is fullscreen below on primary and you see the Doom Window above on the secondary.

Reproduction

---

@Kalevr1 commented on 2020-04-24T23:21:15:

This is my first post so I hope it is correct starting a new report rather than attaching to another. If not apologies.

[BloodyIron]

I'm effectively in the identical scenario, same versions, cannot figure out how to get DOOM Eternal not to crash on start. :(

Did you get this figured out @btegs ?

@btegs, removing the pinned_libs_* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system.
Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf

Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool.

Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either.

What is going on and what steps are missing?

NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!

[Seltyk]

On the old thread a few users reported that battlemode can't find games, and I have the same issue. Nobody on that thread either suggested a cause or reported a fix, so I'd like to bring back attention to that issue.
When trying to find a match in battlemode, on any of the three choices, I simply cannot find a game, ever. There is not crash or error, though admittedly I haven't checked any log files.

[btegs]

I'm effectively in the identical scenario, same versions, cannot figure out how to get DOOM Eternal not to crash on start. :(

Did you get this figured out @btegs ?

@btegs, removing the pinned_libs_* folders prompts Steam to regenerate those folders the next time Steam is started (this is literally what I said previously). The folder's contents is the result of comparing the system libraries to the Steam runtime variants and pinning the Steam runtime variant if it is newer than the host system.
Steam prioritizes libraries in the following order: Pinned libraries > Host system > Steam runtime > ld.so.conf

Deleted those folders and were recreated once starting Steam. I checked the directory and they were symlinking to a 1.2.135 version of Vulkan. cool.
Then I load up a random game with Proton 5.0-6 with the DXVK hud set to 1 under Ubuntu 19.10. It shows up as Mesa 20.0.99 (using the bleeding edge git version from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers for my RX 580. Shows Vulkan 1.2.128 for my Vulkan version. I obviously cannot start DOOM Eternal either.
What is going on and what steps are missing?
NOTE: I found an Ubuntu repo at https://packages.lunarg.com/ which gives me an updated libvulkan1 and libvulkan1:i386 without affecting my current Mesa. 1.2.135 is installed, but whenever I try a game on Steam or using GameHub with a GOG game, it is still at 1.2.128. I have no clue where this version of Vulkan is coming from!

I upgraded to Ubuntu 20.04 with that Vulkan package from lunarg and I still am stuck with 1.2.128. I removed the pinned libs (Steam even warns me when its recreating it on launch) and cannot get that newer version to sync up.

@kisak-valve ignored my comment before, but I'm glad that there are other people having this issue.

[luisalvarado]

The following is Ubuntu 20.04, latest Nvidia drivers 440 with a GTX 1080. After the game is started, a small black screen shows on the second monitor and stays like that.

Sometimes it would show the actual menu instead of the black screen like this

But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose

[BloodyIron]

Alright well DOOM Eternal is now launching for me. I'm unsure what has changed for me to do this. It might have been a recent MESA driver update that fixed it, unsure. Just blind tried it again, and I'm able to get in and play the game. If I observe further issues I'll report them.

[Kalevr1]

The following is Ubuntu 20.04, latest Nvidia drivers 440 with a GTX 1080. After the game is started, a small black screen shows on the second monitor and stays like that.

Sometimes it would show the actual menu instead of the black screen like this

But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose

Did it happen on first-run as well or only subsequent launch attempts? If it's like my situation you can do a workaround by deleting the folder under compdata as I explained in my report, so that every run is a "first" run. I had to dual boot my way through this game unfortunately. It was either that or delete that folder with every launch of the game. Until they fix the multi-monitor launch bug, there is no other way that I can see.

[mtb-xt]

But if I try to make the game go fullscreen by pressing ALT+ENTER, then all hell breaks loose

@luisalvarado instead of pressing alt-enter, try going into settings, and changing 'windowed' mode to 'borderless windowed' first. If it works, change it to 'fullscreen' then. Or just play on borderless?

[atlrvrse]

Even when setting it to use the same prefix there's a problem getting the launcher and idstudio to be open at the same time due to pressure-vessel waiting for either application to exit first before running the other one. which seems to be a problem? im not sure? since im still new to idstudio, but you can still apparently upload mods through the launcher itself

[cncz42]

idstudio seems to black screen, it could be since it doesn't share a prefix with doom eternal but i'm unsure how to get around that in proton since setting WINEPREFIX still runs the setup in the new prefix
log: steam-2545650.log

Was this before or after it gives you the prompt to make a mod folder? You have to wait like 5 or 10 minutes maybe longer before it says "teleporting" and it launches the folder creator and the doom mod launcher.

I got it to boot my moving it to my ssd, not sure if the problem @atlrvrse mentioned affects things since I haven't tried any mod development yet but it appears the preview window is bugged and looks all blown out, it also breaks the editor when it grabs the mouse but that may just be a thing with the editor.

[cncz42]

oh looks like it hits you with a "mod portal must be running to execute this command" a lot when switching files around. Might need to add a workaround that forces the editor to run like it's in the same game as doom eternal for proton or something.

[cncz42]

pc-mod-preview works on proton-ge 9-11, however there's a pretty annoying menu bug that only appears in the modded launch mode where menu inputs get repeated twice meaning you can't rebind keys or do difficulty selection from the start. Could just be an issue on ID's end though.

can't comment on the mod tools yet

The menu bug (which also doubles mouse sensitivity) is fixable by closing the launcher or minimizing it while the game is running, not easy to do on gamescope though since you have to close it just before it boots

[frozen-sea]

Using ProtonGE 9-11 I was able to get the launcher to show up, successfully installed a mod and started the game with it loaded. The performance is terrible though, regardless of if you start with or without mods. Minimizing or closing the launcher after starting the game has no impact. I get hundreds of fps in the non-beta version which drops down to about 20-40 when on the beta branch.

[that404nerd]

pc-mod-preview beta hangs indefinitely on launch for me. No window is showing up, even after minutes. There is no crash in the log and no error as far as I can tell.

Sysinfo: https://gist.github.com/NoXPhasma/306dd756fb1ae36136a4c090ce328c46 Logfile: steam-782330.log

Kinda similar but it shows me the window but crashes before showing the "teleporting" text. I am using ProtonGE 9-11. I reinstalled the game like 2-3 times at this point but it doesn't work no matter what.

System Specs - https://gist.github.com/that404nerd/06ebd20dc1e5e491d03896bd539d64b2

[PorcelainMouse]

My issue doesn't look like the others here, but I think I'm not supposed to make a new issue.

Regression: DOOM Eternal shows graphic artifacts during cut scenes and loading screens. Otherwise, the game seems fine. This used to work, though; this is a new problem that wasn't happening a year ago.

Proton Log: steam-782330.log.gz

Proton 8.0, 9.0, 9.0-0.2 Experimental
Mesa 24.1.6
System Info: https://gist.github.com/PorcelainMouse/b797ba01fced6d7265e789b1f98cf3a7

edit: see below, cut scenes are okay, again.

[that404nerd]

Replying to #3773 (comment)

Using the launcher?

[PorcelainMouse]

Using the launcher?

Uh, is there a launcher? Sorry, I'm honestly not sure what you mean. I launch from Stream. If there is an official launcher for DOOM Eternal, I don' think I've seen it. I didn't disable it, either, AFAIK.

[that404nerd]

Using the launcher?

Uh, is there a launcher? Sorry, I'm honestly not sure what you mean. I launch from Stream. If there is an official launcher for DOOM Eternal, I don' think I've seen it. I didn't disable it, either, AFAIK.

Yes, it's available as an opt in feature. Here is the guide if you want to enable it: https://idstudio.idsoftware.com/#which-platforms-will-doom-eternal-idstudio-beta-be-available-on

[PorcelainMouse]

Hmm, interesting. No, I'm not currently using this new launcher. I prefer without the launcher, generally. But, if you think it will help, I guess that's possible. I highly doubt it, though. Think I should try it? The game is not just payable, but runs really well, otherwise. Perhaps I can live with it.

Oh, yeah, I should say that this is just the loading screens, now. I think I fixed something, but forget what, and now the cut scenes are fine, so I'm not missing as much as I originally described.

[that404nerd]

Hmm, interesting. No, I'm not currently using this new launcher. I prefer without the launcher, generally. But, if you think it will help, I guess that's possible. I highly doubt it, though. Think I should try it? The game is not just payable, but runs really well, otherwise. Perhaps I can live with it.

Oh, yeah, I should say that this is just the loading screens, now. I think I fixed something, but forget what, and now the cut scenes are fine, so I'm not missing as much as I originally described.

That's my issue right now. I am not able launch the game using the launcher. New mods can only be played using the launcher. I just want that to run but was unable to launch the game using it. Can you try launching the game using the new launcher and tell if it's working or not? Thanks!

[alasky17]

@that404nerd I'm hoping you ran into the same issue as I ran into when trying to test this. This should be fixed on experimental-bleeding-edge :)

[that404nerd]

@that404nerd I'm hoping you ran into the same issue as I ran into when trying to test this. This should be fixed on experimental-bleeding-edge :)

I will look into it soon. Thanks for the reply and have a nice day.

[that404nerd]

Hmm, interesting. No, I'm not currently using this new launcher. I prefer without the launcher, generally. But, if you think it will help, I guess that's possible. I highly doubt it, though. Think I should try it? The game is not just payable, but runs really well, otherwise. Perhaps I can live with it.

Oh, yeah, I should say that this is just the loading screens, now. I think I fixed something, but forget what, and now the cut scenes are fine, so I'm not missing as much as I originally described.

That's my issue right now. I am not able launch the game using the launcher. New mods can only be played using the launcher. I just want that to run but was unable to launch the game using it. Can you try launching the game using the new launcher and tell if it's working or not? Thanks!

@that404nerd I'm hoping you ran into the same issue as I ran into when trying to test this. This should be fixed on experimental-bleeding-edge :)

Also can you please explain why the game was crashing when I was trying to launch it from the official launcher?

[PorcelainMouse]

So, I tried the launcher, and it hung. In the properties, I 'Beta' to "pc-mod-preview", and Steam downloaded something. When I clicked 'Play', nothing happened, but I could see the launcher process running. I waited a while and nothing ever showed up. I had to 'Stop' it, so it was hung.

[that404nerd]

So, I tried the launcher, and it hung. In the properties, I 'Beta' to "pc-mod-preview", and Steam downloaded something. When I clicked 'Play', nothing happened, but I could see the launcher process running. I waited a while and nothing ever showed up. I had to 'Stop' it, so it was hung.

That's weird. I was able to run the launcher without problems. I used proton experimental and proton ge and the launcher works. Its the game that doesnt work at all. @alasky17 When is it gonna be fixed BTW? Also please share the reason for the game's crash. Thanks!

[that404nerd]

@alasky17 any update on the issue?

[simifor]

@that404nerd the game is working fine on my side, launches fine in the default branch for the game, and also launches from the mod branch (though I didn't attempt to actually mod the game). Is the game broken for you in both branches? add PROTON_LOG=1 %command% tot he game's launch parameters and upload the resulting file here, in your home folder look for steam-782330.log

[that404nerd]

@that404nerd the game is working fine on my side, launches fine in the default branch for the game, and also launches from the mod branch (though I didn't attempt to actually mod the game). Is the game broken for you in both branches? add PROTON_LOG=1 %command% tot he game's launch parameters and upload the resulting file here, in your home folder look for steam-782330.log

No only the mod branchisnt working for me . And also the log file is like 2-3 gigs in size. That's why I was unable to send it here. Is there a way to fix that? Thanks!

[alasky17]

@that404nerd Things are fixed and generally working for us in experimental now ... if you are still seeing a failure, it sounds like it is something different and potentially unique to your system. In order to attempt to diagnose the issue, we will need a log. You can use "xz -T0 steam-782330.log" to compress the log, which might get it small enough to upload?

[that404nerd]

@that404nerd Things are fixed and generally working for us in experimental now ... if you are still seeing a failure, it sounds like it is something different and potentially unique to your system. In order to attempt to diagnose the issue, we will need a log. You can use "xz -T0 steam-782330.log" to compress the log, which might get it small enough to upload?

I am using the bleeding edge of proton as you mentioned before and still crashes after the bethesda logo. Here is the log file:
steam-782330.log
It's only 11M for some reason so i am not compressing it. Thanks!

[kisak-valve]

Hello @that404nerd, experimental-bleeding-edge-8.0-82496-20240226-p479bb6-wa058f1-d9004c1-v806fd7 is an old build and not the current bleeding edge. Switch beta branches.

[that404nerd]

Hello @that404nerd, experimental-bleeding-edge-8.0-82496-20240226-p479bb6-wa058f1-d9004c1-v806fd7 is an old build and not the current bleeding edge. Switch beta branches.

Which version should I use exactly? Thanks!

[simifor]

@that404nerd this one

[that404nerd]

Replying to #3773 (comment)

Thanks for the quick reply! I will look into it.

[that404nerd]

It still crashes. This time it's before the teleporting screen.

[that404nerd]

@that404nerd Things are fixed and generally working for us in experimental now ... if you are still seeing a failure, it sounds like it is something different and potentially unique to your system. In order to attempt to diagnose the issue, we will need a log. You can use "xz -T0 steam-782330.log" to compress the log, which might get it small enough to upload?

Here is the compressed log file: https://mega.nz/file/lmsWkZIR#lKGV5qa1miAFxhLOjofBYnW734Mi2biDYhhZ_JZj59E

Github doesn't allow me to upload .xz files. Sorry for the inconvenience.

[DoomerDev2011]

I got an issue with Doom Eternal that I have not been able to figure out with any version of proton and I see it on all the gameplay videos that I see. For this bug, whenever a cutscene changes a camera, there's a brief shot of pure black in between. You can see this bug in almost any gameplay video for Doom Eternal on the deck.

https://m.youtube.com/watch?v=QVzfwR6YvX8&embeds_referring_euri=https%3A%2F%2Fwww.reddit.com%2F

https://youtu.be/L_oo5_fT1po?t=781&si=f5TTWIUYAuXHQMwt

https://youtu.be/L_oo5_fT1po?t=781&si=f5TTWIUYAuXHQMwt

This bug has also been found by other steam deck users.

https://www.reddit.com/r/SteamDeck/comments/1ef9e80/doom_eternal_flashes_of_black/

https://www.reddit.com/r/SteamDeck/comments/15ilyeq/why_does_this_happen_specifically_on_steam_deck/

I have not been able to find any solution for it. Wanted to report it here so maybe someone in the future could look into it. Thanks again!

[that404nerd]

For some reason, when i install mods through nexus or the official mod app the fps drops from 130-140 to low 50's. I thought it was just the in game metrics but the input lag is a lot more noticable. When i run the same game with the same mods on Windows it works really well on ultra settings (rt off). I reinstalled the game, tried to switch from proton ge to proton experimental but it didn't seem to work. I am running the game with a RTX 3050 in pop os 22.04 LTS. Also the game doesn't stutter but the input lag is lot more noticable as i mentioned above. I ran the game on Windows and Linux without DLSS.