Doom Eternal (782330) - Initial month of feedback

[oscarcp]

Compatibility Report

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

System Information

• GPU: nVidia GTX 2060
• Driver/LLVM version: nvidia 440.54
• Kernel version: 5.5.7
• Link to full system information report as Gist: https://gist.github.com/oscarcp/6dce66429b3fdaf0f5eaf7c245a9a890
• Proton version: 5.0-4

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

Symptoms

The game starts, opens the system tray of wine, then closes abruptly.

Reproduction

• Install DOOM Eternal, click play
• Another way is force in the game propeties the Proton vesion to 5.0-4 and click play.

[kisak-valve]

Doom Eternal not starting

Issue transferred from #3655.
@APoniatowski posted on 2020-03-20T00:48:54:

Compatibility Report

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

System Information

soon...

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

Symptoms

Game crashes on start

Reproduction

-install
-start

---

@oscarcp commented on 2020-03-20T00:49:39:

Crap, we both started the ticket at the same time. Shall I put mine as duplicate?

[kisak-valve]

Hello @oscarcp, my understanding is that this game will need an updated video driver stack. I'm not sure of everything that is needed, but vulkan-loader 1.2.135 should be one of the requirements. This is rare, but Arch's vulkan-loader is currently too old. Opting into Steam's beta client, then completely closing steam and running Steam with steam-runtime should at least cover that requirement. It may also need a bleeding edge video driver version.

[oscarcp]

Hello @oscarcp, my understanding is that this game will need an updated video driver stack. I'm not sure of everything that is needed, but vulkan-loader 1.2.135 should be one of the requirements. This is rare, but Arch's vulkan-loader is currently too old. Opting into Steam's beta client, then completely closing steam and running Steam with steam-runtime should at least cover that requirement. It may also need a bleeding edge video driver version.

Updated nvidia drivers to 440.64 and my current vulkan-icd-loader is 1.2.132. There doesn't seem to be any more recents version, at least packaged. I'll investigate and see if I can update.

[APoniatowski]

switched to steam beta and using steam linux runtime, instead of proton. had an error where the idlauncher binary was missing, so running game file verification... might need to reinstall though

[APoniatowski]

nope... missing executable (idtechlauncher.exe). last ditch effort now is reinstalling the game

[kisak-valve]

Hello @APoniatowski, if you tested with the Steam Linux Runtime compatibility tool, that's a container for running Linux games on Linux. Selecting it is expected to fail because Proton is then not used to handle Windows games.

I should have clarified that the Steam runtime (not the compatibility tool) update in today's Steam client beta update contains the 1.2.135 vulkan loader.

[APoniatowski]

aaah, figured.

However, I did run it with proton, before trying the compatibility tool. still crashed unfortunately

[CSahajdacny]

Is there a file called DOOMEternalx64vk.exe?

[gardotd426]

@APoniatowski @kisak-valve I'm pretty sure what @kisak-valve was saying is that the "Steam Linux Runtime" compatibility tool is a replacement for (and conflict with) Proton, BUT that running the steam-runtime version of Steam instead of steam-native on Arch-based distributions uses the Steam runtime libraries, not the compatibility layer, and that's what's been updated to vulkan loader 1.2.135.

[oscarcp]

Here goes an update. I've updated vulkan-headers and vulkan-icd-loader both to 1.2.135 (I've modified the AUR files, I'll publish the changes tomorrow). As for the nvidia drivers, 440.64 is the latest available (latest beta available is 440.26).

I've also tried Steam beta and non-beta, running each natively and as runtime from terminal. Nothing has worked so far :(

[gardotd426]

@oscarcp That doesn't help Valve fix anything. You need to post the logs for each attempt, so they can see what changes, and what doesn't. Don't just say "it didn't work."

[APoniatowski]

@gardotd426 I should've clarified on my part as well. I only run steam-runtime (had to double check)

@kisak-valve Here's an updated log, after opting in for the beta and updating it, reinstalling the game and starting it again

steam-782330.log

[gardotd426]

@oscarcp also, you couldn't have updated the AUR files for vulkan-icd-loader, it's in the repos, there is no vulkan-icd-loader AUR package. vulkan-headers is also in the official repos, not AUR, although there is a vulkan-headers-git AUR package. But that's irrelevant anyway as that's for development, you don't need any vulkan-headers package installed.

[doitsujin]

also, you couldn't have updated the AUR files

You can obtain the PKGBUILD for the package via ABS and modify that though. I'm almost certain that that's what they meant.

FWIW I did the same (requires vulkan-headers-git to build) but it still fails with the exact same log that OP posted.

[APoniatowski]

I see lots of from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored and from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored errors in the log, now that I look at it

ERROR: ld.so: object '/home/sizigee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

ERROR: ld.so: object '/home/sizigee/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

[gardotd426]

@doitsujin Philip, yeah that is true, but that's not what they said so I didn't think that's what they meant. But that's fair enough.

Any ideas?

[gardotd426]

@APoniatowski I know that there are always a ton of those errors regardless, that are supposed to be ignored, but you're right it looks like a lot lot more than usual

[oscarcp]

@gardotd426 regou're right, so here goes:

• Steam Beta run from launcher with updated driver/vulkan https://gist.github.com/oscarcp/f915dba11124a1a41fd6ab146f009b24
• Steam non-beta https://gist.github.com/oscarcp/c1eea3b242d26938394d29acfc28b31d

Regarding the AUR, yes, I've downloaded the PKGBUILDS, regenerated the sha256sum and compiled them. Regarding headers, the loader deepends on the headers
vulkan-icd-loader 1.2.135 PKGBUILD: https://gist.github.com/oscarcp/9b54ea7f6bd4eb4144bd4e5e980f2c4c
vuikan-headers 1.2.135 PKGBUILD: https://gist.github.com/oscarcp/4c4fb71fa380015b722172f308d406b1

[APoniatowski]

looked at the launcher.cfg for doom eternal and saw this:
rgl_minNvidiaDriverVersion 44261
and changed it to my version:
rgl_minNvidiaDriverVersion 44064

still didn't work, for those who thought about mucking in cfg's... the only other cfg's there, are package and candidate details

[gardotd426]

The logs are huge, but so far they have the same errors, from what little I've been able to go over.

I would suggest AMDVLK over RADV if either of you were running AMD, but seems like we don't have anyone trying this with an AMD card yet.

EDIT: Removed WINED3D reference, somehow forgot this game was Vulkan only with no OpenGL or DX

[doitsujin]

The game uses Vulkan, so wined3d/dxvk makes absolutely no difference whatsoever.

FWIW I am using an AMD card.

[APoniatowski]

tried WINED3D now... same result, unfortunately.

steam-782330.log

[gardotd426]

@doitsujin, duh, I completely forgot this one was Vulkan-only, I was thinking of how DOOM 2016 had an OpenGL version.

Have you tried AMDVLK or anything like that? Are you getting the same sorts of errors as the guys with the Nvidia cards?

[ghost]

I'm experiencing the exact same symptoms on AMD hardware.

System Information

• GPU: Radeon RX Vega 64
• Driver/LLVM version: Mesa 20.0.0-devel
• Kernel version: 5.3.0-42-generic
• Proton version: 5.0-4

steam-782330.log

[APoniatowski]

come to think of it... is there a way to run DOOMEternalx64vk.exe instead of the launcher? I know launchers can be wonky for some/most games

[doitsujin]

@gardotd426 yes, this is not a driver issue.

FWIW I'm trying to build a current wine version with ValveSoftware/wine#85 applied, but so far I'm having issues rebasing the patch.

[gardotd426]

@APoniatowski try it in Lutris. If anyone has enough storage and a fast enough internet connection I would suggest maybe also trying to run it in Wine Steam.

[AllKind]

@Chanakaya it's possible you hit the Denuvo (drm - copyright protection). Did you start the game more than 5 times? You migh just need to wait 24 hours.
Some1 way above in that thread posted the exact error. If you find that (might take a day haha), you could compare that to your proton log.
The newest official proton release candidate contains a drm fix (I don't think that's already in 5.5-GE-1). #3721
Btw: you can disable the driver warning in the launcher.cfg (how to is posted a dozen times in this thread).

[rkfg]

Btw: you can disable the driver warning in the launcher.cfg (how to is posted a dozen times in this thread).

Offtopic: might not be that easy considering this wonderful GitHub "feature":

How to load all the comments and/or search them?
EDIT: found this extension, install and Alt+Click this button to load 200 comments instead of 60. A bit better but I'd prefer good old pagination and proper search instead.

[giblitz]

I see a lot of comments here saying to use Vulkan 1.2... I have nvidia 440.82 drivers installed and vulkan info claims Instance Version is 1.2.131, but when I run with Proton 5.4GE3 the performance stats in doom claim that i'm still on Vulkan 1.1.119. Is there a launch option I should be adding to force it to use 1.2?

[TheGreatMcPain]

@giblitz Vulkan-loader 1.2... Is only required to launch the game, so if it runs then you should be good to go, but if you really want 1.2 you'd need the nvidia vulkan beta drivers.

[krasmazov483]

Hi there!

I have been playing the game with the AMD-PRO drivers for a few days now and it runs great, but for some reason Battlemode doesn't work on Linux for me, I also tried on a Windows VM, and there it gets to a match just fine, is there any workaround for this?

My config:
OS: Solus 4.1 (I disabled the Steam Linux Integration, so Steam would use the bundled runtime for the newest vulkan header/loader)
GPU: RX 5700 XT (Mesa 19.3.4)
Proton Version: 5.5-GE-1 (Also tried with 5.4-GE-3)
Launch Options: VK_ICD_FILENAMES=/home/jojo/Documents/Drivers/AMDGPU-PRO/amd_icd64.json gamemoderun %command% +com_skipIntroVideo 1

[rkfg]

@zKhrona does it also freeze with black screen for you when you resize the window or if another window appears in front of it? I wonder if it's a driver issue or Wine's.

[75AngryDucks]

@rkfg I have no experience at all in this, but I remember early in the thread people mentioned that wine currently doesn't have true support for VK_EXT_full_screen_exclusive, only workarounds. Could that be what's causing the issue?

[krasmazov483]

@rkfg Luckily it doesn't, I saw some people talking about this issue here, but mine resizes through the menu just fine. I'm not able to alt tab the game, but changing workspaces work, even tho the mouse is still hooked to the game, so I can't use it. I don't know if the fullscreen issue is related to driver, but it could be working on mine because I'm using the PRO drivers.

[Vash63]

Wine log from my hang just by switching virtual desktops away and then back.

steam-782330.log.gz

Really hope it can be resolved, it's by far the most impactful bug remaining in this game

[rkfg]

@75AngryDucks I think no because it happens when I just resize the game window that's already in the windowed mode, not fullscreen.
@zKhrona Does it work both ways to windowed and back if you do it several times? If yes then it really could be an NVIDIA driver issue I think.

[krasmazov483]

After playing the game more, I found that I can move my mouse outside the game's window if I'm in a menu in either a mission or the Fortress of Doom and change workspaces to access my Desktop, as alt tab doesn't work for me even on Windowed mode. Unfortunately Battlemode is still not working for me, every time I try to find a match the game just say it can't find any. On Windows it works normally.

@rkfg I tried changing the resolution and screen ratio multiple times, seems to be working fine for me, it freezes for 2 or 3 seconds upon changing it, but that's all.

[rkfg]

@zKhrona Great, thanks for checking it. Then it's likely not a Wine issue at all. On a side note, I made a makeshift patch for that WM_ERASEBKGND message and all it did was remove the fixme lines in the log, the freeze itself wasn't fixed. Anyway, was worth a try. The issue is probably on the driver side.

[mnn]

How to load all the comments and/or search them?

@rkfg Threw together a simple user-script to load all comments: https://greasyfork.org/en/scripts/400462-git-hub-unroll-comments. Tested only in Firefox and I must say that after loading all comments on this page it gets a bit laggy occasionally (pagination would be better, but doing that in a user-script would probably break things like live adding of new comments or edits).

[AllKind]

Update to testing Proton 5.0.6 RC :
Mouse acceleration is different to previous versions and to the GE releases.
It's much faster and doesn't seem to be constant. If I manage to make it nicely playable for me, using the other versions results in extremely slow mouse moving.
(and still, Alt+Tab makes the game go black. Alt+Tab doesn't go back. Pressing Alt once and then Alt+Tab, goes back to game, but yeah black only...)

Proton log:
https://drive.google.com/open?id=1fJVizLLrEeOjkoODDFrbQLhEk7gCdsgi

kernel 5.6.3
latest stable nvidia drivers 64-440.82
linux mint 19.3 cinnamon DE
ROCCAT Kone Pure Owl-Eye Mouse

[ldb]

Does anyone else have problems signing in to Bethesdanet? Breaks Battlemode for me, unfortunately.

[willpiam]

Are these crashes only happening on Nvidia cards?

[PraetorianSC4]

@rkfg I have no experience at all in this, but I remember early in the thread people mentioned that wine currently doesn't have true support for VK_EXT_full_screen_exclusive, only workarounds. Could that be what's causing the issue?

Alt+Tab in Doom Eternal under 5.4-3 and 440.82-x drivers is guaranteed permanent blackscreen. Also Steam Overlay is also problematic. Game runs solid otherwise in Vulkan w/ 1080Ti

[sonic2kk]

@PraetorianSC4 The Steam Overlay is known to decrease performance in DOOM Eternal, it's not a Wine/Proton issue. A comment lists a 5fps boost, but for me it was more like doubling the FPS (running a 5700XT w/ Mesa 20.0.4 in fairness).

Another Reddit post said that it was the FPS counter causing issues, so you could try disabling that and instead either using DOOM Eternal's built in performance metrics, or using the likes of MangoHud which I personally prefer and use myself.

@willpiam I'd like to chip in and say that running the latest version of Vulkan and Mesa stable on Arch doesn't have any issues when you Alt+Tab, aside from the documented Dossier bug. So it seems like this is an Nvidia issue.

[megaden]

Hey guys, FYI just in case someone will run into the same issue as I did.

I got DOOM Eternal running perfectly on Ubuntu 18.04.4 with Nvidia Driver 440.82 from graphics-drivers PPA and Proton-5.4-GE-3.

However after installing some updates recently it ceased to work - just kept crashing at startup. Launching steam with PROTON_LOG=1 revealed the following message in the log:

FATAL ERROR: Please update your driver: VK_EXT_full_screen_exclusive is required.

After fiddling with that for a while by looking into /var/log/apt/history.log I noticed that with recent updates I got libvulkan1 and mesa-vulkan-drivers packages installed which weren't installed before.

Removing both fixed the issue for me, so I guess those cause some kind of conflict with Nvidia's Vulkan stuff hence info about extensions driver actually supported was incorrect.

[kisak-valve]

Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.

If you were to re-add libvulkan1, then go to <steam install dir>/ubuntu12_32/steam-runtime and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.

[nathanjackson]

With the new nvidia drivers released today on rpmfusion I've had a chance to re-test on both of my systems.

DOOM Eternal now seems to be playable.

Machine 1 (Desktop):
CPU: i7-4770
RAM: 32GB
GPU: GTX 1080ti
Drivers: 440.82
Distro: Fedora 30
Proton: Proton-5.4-GE-3
Launch Options: None

Machine 2 (Laptop):
CPU: i7-8750H
RAM: 16GB
GPU: RTX 2060
Proton: Proton-5.4-GE-3
Drivers: 440.82
Distro: Fedora 30
Launch Options (for PRIME offloading): __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%

Initially I had some audio crackling, but it seems to have resolved itself.

[poperigby]

I've got a crash log for that hard crash I was talking about earlier:
https://send.firefox.com/download/945b855f1dd20e0d/#dP9yXbTc4PGFlF5mkZL1EQ

[megaden]

Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.

If you were to re-add libvulkan1, then go to <steam install dir>/ubuntu12_32/steam-runtime and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.

Hi @kisak-valve thanks for your suggestion, it worked perfectly 👍 Actually it saved the day since later I found out that removing libvulkan1 broke something else, so super happy now everything works fine, thanks a lot!

[jasonphi]

Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.

If you were to re-add libvulkan1, then go to <steam install dir>/ubuntu12_32/steam-runtime and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.

This also solved my issues on Ubuntu 18.04. Thanks!

[kisak-valve]

Hello, in the interest of making usable feedback more accessible moving forward with this game, I'm archiving this issue report and we'll continue discussing Doom Eternal on #3773.

If you wish to continue receiving notifications about Doom Eternal, go to #3773 and click the subscribe button on the right side of the issue report.