Proton: 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:

• [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.

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 https://github.com/ValveSoftware/Proton/issues/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:

• [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.

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?

[3c8e1f54a4b6]

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 https://github.com/ValveSoftware/wine/pull/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.

[gardotd426]

@doitsujin lol it's always something, isn't it. Hopefully that will fix it once you get it figured out.

[AllKind]

Hello,

same here Doom Eternal won't start.

Linux Mint 19.3
Kernel 5.5.9
Nvidia driver 440.64
steam & steam beta.
Proton 5.0-4

How do you guys create those detailed logs? So I can also contribute one if wanted.

This is what I get when running steam from a terminal:

Terminal spew

```

Adding process 27762 for game ID 782330
ERROR: ld.so: object '/home/ellen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 27826 for game ID 782330
Game update: AppID 782330 "", ProcID 27826, IP 0.0.0.0:0
RecordSteamInterfaceCreation (PID 27826): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 27826): SteamUser020 / User
RecordSteamInterfaceCreation (PID 27826): SteamUser017 / User
RecordSteamInterfaceCreation (PID 27826): STEAMAPPS_INTERFACE_VERSION006 / Apps
wine: Unhandled page fault on write access to 0000000023377774 at address 0000000148D71006 (thread 003e), starting debugger...
ERROR: ld.so: object '/home/ellen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 27828 for game ID 782330
Unhandled exception: page fault on write access to 0x23377774 in 64-bit code (0x0000000148d71006).
Register dump:
rip:0000000148d71006 rsp:000000000092e758 rbp:0000000023377774 eflags:00010217 ( R- -- I -A-P-C)
rax:000000015bb567c2 rbx:000000015bb567c2 rcx:0000000023377774 rdx:000000015bb567c2
rsi:0000000157529f99 rdi:0000000023377774 r8:0000000072cc6fe6 r9:0000000023377774 r10:000000015bd128ac
r11:000000000092e91e r12:000000004bb38659 r13:000000014050f850 r14:000000002319d1de r15:000000015bb567c2
Stack dump:
0x000000000092e758: ffffffff9b2f4a10 0000000000014b1b
0x000000000092e768: 0000000000000000 000100000092f780
0x000000000092e778: 0000000000000000 0000000000000000
0x000000000092e788: b2fe000000000000 f9c00000000120db
0x000000000092e798: 0001000000000092 0001000000000000
0x000000000092e7a8: b882000000000000 0000000000015b01
0x000000000092e7b8: 04b1000000000000 0000000000015d88
0x000000000092e7c8: 0000000000000000 0001000000000000
0x000000000092e7d8: 0000000000000000 0000000000000000
0x000000000092e7e8: 0000000000000000 9290000000000000
0x000000000092e7f8: 0000000000015551 00fc000000000000
0x000000000092e808: 0000000000000000 0000000000000000
Backtrace:
=>0 0x0000000148d71006 EntryPoint+0xea8fbfe6() in doometernalx64vk (0x0000000023377774)
0x0000000148d71006 EntryPoint+0xea8fbfe6 in doometernalx64vk: movq %r13,0x00000000001da596(%r14)
Modules:
Module Address Debug info Name (127 modules)
PE 930000- a2c000 Deferred oo2core_8_win64
PE 62140000- 62144000 Deferred uxtheme
PE 637c0000- 6383d000 Deferred winmm
PE 64340000- 64346000 Deferred winhttp
PE 64940000- 64943000 Deferred shcore
PE 64c80000- 64c83000 Deferred steamclient64
PE 64d40000- 64d44000 Deferred vulkan-1
PE 65000000- 65028000 Deferred ole32
PE 65600000- 6561e000 Deferred xinput1_3
PE 65780000- 65784000 Deferred version
PE 66440000- 66449000 Deferred msacm32
PE 68a40000- 68a48000 Deferred shlwapi
PE 6a100000- 6a108000 Deferred oleaut32
PE 6a700000- 6a70f000 Deferred setupapi
PE 6afc0000- 6afc3000 Deferred msimg32
PE 6b2c0000- 6b2df000 Deferred wininet
PE 6b880000- 6b883000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bec4000 Deferred imm32
PE 6c0c0000- 6c0c4000 Deferred wsock32
PE 6d9c0000- 6d9cb000 Deferred mpr
PE 6e340000- 6e343000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6e6c3000 Deferred api-ms-win-core-localization-l1-2-1
PE 6e780000- 6e797000 Deferred oleacc
PE 6f480000- 6f484000 Deferred gdiplus
PE 6fbc0000- 6fbc4000 Deferred rpcrt4
PE 71240000- 71245000 Deferred jsproxy
PE 7b000000- 7b003000 Deferred kernelbase
ELF 7b400000- 7b681000 Deferred kernel32
-PE 7b410000- 7b681000 \ kernel32
ELF 7bc00000- 7bf01000 Deferred ntdll
-PE 7bc20000- 7bf01000 \ ntdll
ELF 7c000000- 7c003000 Deferred
PE 13b400000- 13b44b000 Deferred steam_api64
PE 140000000- 15eb45000 Export doometernalx64vk
PE 180000000- 18007b000 Deferred bink2w64
ELF 7fe0035e8000- 7fe00533a000 Deferred steamclient.so
ELF 7fe00533a000- 7fe0056b9000 Deferred lsteamclient
-PE 7fe005450000- 7fe0056b9000 \ lsteamclient
ELF 7fe0056b9000- 7fe0058ce000 Deferred libgpg-error.so.0
ELF 7fe0058ce000- 7fe005bea000 Deferred libgcrypt.so.20
ELF 7fe005bea000- 7fe005e06000 Deferred liblz4.so.1
ELF 7fe005e06000- 7fe00602c000 Deferred liblzma.so.5
ELF 7fe00602c000- 7fe0062b0000 Deferred libsystemd.so.0
ELF 7fe0062b0000- 7fe0064cb000 Deferred libresolv.so.2
ELF 7fe0064cb000- 7fe0066cf000 Deferred libkeyutils.so.1
ELF 7fe0066cf000- 7fe00691c000 Deferred libdbus-1.so.3
ELF 7fe00691c000- 7fe006b27000 Deferred libkrb5support.so.0
ELF 7fe006b27000- 7fe006d2b000 Deferred libcom_err.so.2
ELF 7fe006d2b000- 7fe006f5d000 Deferred libk5crypto.so.3
ELF 7fe006f5d000- 7fe007233000 Deferred libkrb5.so.3
ELF 7fe007233000- 7fe007444000 Deferred libavahi-client.so.3
ELF 7fe007444000- 7fe007650000 Deferred libavahi-common.so.3
ELF 7fe007650000- 7fe00789b000 Deferred libgssapi_krb5.so.2
ELF 7fe00789b000- 7fe007b27000 Deferred libcups.so.2
ELF 7fe007b27000- 7fe007d7d000 Deferred libvulkan.so.1
ELF 7fe007d7f000- 7fe007f85000 Deferred libxfixes.so.3
ELF 7fe007f85000- 7fe00818f000 Deferred libxcursor.so.1
ELF 7fe00818f000- 7fe00839f000 Deferred libxi.so.6
ELF 7fe00839f000- 7fe0085a2000 Deferred libxcomposite.so.1
ELF 7fe0085a2000- 7fe0087ad000 Deferred libxrandr.so.2
ELF 7fe0087ad000- 7fe0089b7000 Deferred libxrender.so.1
ELF 7fe0089b7000- 7fe008bbd000 Deferred libxxf86vm.so.1
ELF 7fe008bbd000- 7fe008dc0000 Deferred libxinerama.so.1
ELF 7fe008dc0000- 7fe008fd2000 Deferred libxext.so.6
ELF 7fe008fd2000- 7fe00909d000 Deferred winex11
-PE 7fe008fe0000- 7fe00909d000 \ winex11
ELF 7fe00913c000- 7fe00936e000 Deferred libexpat.so.1
ELF 7fe00936e000- 7fe0095b3000 Deferred libfontconfig.so.1
ELF 7fe0095b3000- 7fe0097e5000 Deferred libpng16.so.16
ELF 7fe0097e5000- 7fe009a99000 Deferred libfreetype.so.6
ELF 7fe009a99000- 7fe009ca1000 Deferred libffi.so.6
ELF 7fe009ca1000- 7fe009f22000 Deferred libgmp.so.10
ELF 7fe009f22000- 7fe00a156000 Deferred libhogweed.so.4
ELF 7fe00a156000- 7fe00a38c000 Deferred libnettle.so.6
ELF 7fe00a38c000- 7fe00a59f000 Deferred libtasn1.so.6
ELF 7fe00a59f000- 7fe00a91d000 Deferred libunistring.so.2
ELF 7fe00a91d000- 7fe00ab3a000 Deferred libidn2.so.0
ELF 7fe00ab3a000- 7fe00ae69000 Deferred libp11-kit.so.0
ELF 7fe00ae69000- 7fe00b086000 Deferred libz.so.1
ELF 7fe00b086000- 7fe00b3ec000 Deferred libgnutls.so.30
ELF 7fe00b3ec000- 7fe00b44a000 Deferred winspool
-PE 7fe00b3f0000- 7fe00b44a000 \ winspool
ELF 7fe00b44a000- 7fe00b48c000 Deferred ws2_32
-PE 7fe00b450000- 7fe00b48c000 \ ws2_32
ELF 7fe00b48c000- 7fe00b4e2000 Deferred winevulkan
-PE 7fe00b4a0000- 7fe00b4e2000 \ winevulkan
ELF 7fe00b4e2000- 7fe00bf2e000 Deferred shell32
-PE 7fe00b500000- 7fe00bf2e000 \ shell32
ELF 7fe00bf2e000- 7fe00bf60000 Deferred iphlpapi
-PE 7fe00bf40000- 7fe00bf60000 \ iphlpapi
ELF 7fe00bf60000- 7fe00c09b000 Deferred ucrtbase
-PE 7fe00bf90000- 7fe00c09b000 \ ucrtbase
ELF 7fe00c09b000- 7fe00c118000 Deferred dbghelp
-PE 7fe00c0a0000- 7fe00c118000 \ dbghelp
ELF 7fe00c118000- 7fe00c204000 Deferred msvcrt
-PE 7fe00c140000- 7fe00c204000 \ msvcrt
ELF 7fe00c204000- 7fe00c3b4000 Deferred gdi32
-PE 7fe00c220000- 7fe00c3b4000 \ gdi32
ELF 7fe00c3b4000- 7fe00c639000 Deferred user32
-PE 7fe00c3d0000- 7fe00c639000 \ user32
ELF 7fe00c639000- 7fe00c660000 Deferred bcrypt
-PE 7fe00c640000- 7fe00c660000 \ bcrypt
ELF 7fe00c660000- 7fe00c6a4000 Deferred sechost
-PE 7fe00c670000- 7fe00c6a4000 \ sechost
ELF 7fe00c7a4000- 7fe00c81e000 Deferred advapi32
-PE 7fe00c7b0000- 7fe00c81e000 \ advapi32
ELF 7fe00cc4e000- 7fe00ce60000 Deferred libnss_files.so.2
ELF 7fe00ce60000- 7fe00d07a000 Deferred libnsl.so.1
ELF 7fe00d07a000- 7fe00d286000 Deferred libnss_nis.so.2
ELF 7fe00d286000- 7fe00d490000 Deferred libnss_compat.so.2
ELF 7fe00eb6f000- 7fe00ed84000 Deferred libbsd.so.0
ELF 7fe00ed84000- 7fe00ef8a000 Deferred libxdmcp.so.6
ELF 7fe00ef8a000- 7fe00f18e000 Deferred libxau.so.6
ELF 7fe00f190000- 7fe00f3b8000 Deferred libxcb.so.1
ELF 7fe00f3b8000- 7fe00f6f0000 Deferred libx11.so.6
ELF 7fe00f6f0000- 7fe00f908000 Deferred libgcc_s.so.1
ELF 7fe00f908000- 7fe00fbbe000 Deferred libgldispatch.so.0
ELF 7fe00fbbe000- 7fe00fdef000 Deferred libglx.so.0
ELF 7fe00fdf1000- 7fe01018f000 Deferred libm.so.6
ELF 7fe010518000- 7fe01071c000 Deferred libdl.so.2
ELF 7fe01071c000- 7fe010924000 Deferred librt.so.1
ELF 7fe010924000- 7fe010bb0000 Deferred libgl.so.1
ELF 7fe010bb0000- 7fe010fa1000 Deferred libc.so.6
ELF 7fe010fa3000- 7fe0111c2000 Deferred libpthread.so.0
ELF 7fe0111c2000- 7fe011564000 Export libwine.so.1
ELF 7fe011564000- 7fe0117a1000 Deferred gameoverlayrenderer.so
ELF 7fe0117a3000- 7fe0119cd000 Deferred ld-linux-x86-64.so.2
Threads:
process tid prio (all id:s are in hex)
00000008 steam.exe
00000030 0
00000009 0
0000000c services.exe
0000002c 0
00000026 0
00000018 0
00000013 0
00000012 0
00000011 0
0000000e 0
0000000d 0
0000000f plugplay.exe
00000015 0
00000014 0
00000010 0
00000016 winedevice.exe
00000023 0
00000022 0
00000021 0
00000020 0
0000001f 0
0000001e 0
0000001d 0
0000001c 0
0000001b 0
0000001a 0
00000019 0
00000017 0
00000024 winedevice.exe
00000029 0
00000028 0
00000027 0
00000025 0
0000002a winedevice.exe
0000002f 0
0000002e 0
0000002d 0
0000002b 0
00000031 explorer.exe
00000037 0
00000036 0
00000033 0
00000032 0
0000003a idTechLauncher.exe
0000003c -2
0000003b 0
0000003d (D) Z:\GamesSteamLibrarysteamapps\common\DOOMEternalDOOMEternalx64vk.exe
0000003e 0 <==
System information:
Wine build: wine-5.0-481-g0295175
Platform: x86_64
Version: Windows 7
Host system: Linux
Host version: 5.5.9-mint-local-5.5.9
pid 27682 != 27681, skipping destruction (fork without exec?)
Game removed: AppID 782330 "", ProcID 27826
Game 782330 created interface STEAMAPPS_INTERFACE_VERSION006 / Apps
Game 782330 created interface SteamUser017 / User
Game 782330 created interface SteamUser020 / User
Game 782330 created interface SteamUtils009 / Utils
Game 782330 method call count for IClientUser::GetSteamID : 3
Game 782330 method call count for IClientUtils::GetAppID : 5
Game 782330 method call count for IClientUtils::RecordSteamInterfaceCreation : 4
Game 782330 method call count for IClientAppManager::GetCurrentLanguage : 1
Uploaded AppInterfaceStats to Steam
Exiting app 782330
No cached sticky mapping in ActivateActionSet.
´´´

[rabidlassie]

@AllKind launch the game with "PROTON_LOG=1" (no quotation marks), it will automatically create a log file named "steam-gameid.log" in your /home/ directory, in this case its name will be "steam-782330.log". Then you can upload that file using the attachment system right below the comment-box.

[gardotd426]

@AllKind you can also go to the game's properties in Steam and go to the launch options, and put PROTON_LOG=1 %command%, that way you'll get the log whether you launch from a terminal or not.

[NuclearNautilus]

steam-782330.log
I'm having the same issue. I'll upload my Proton log, just on the off-chance it can be helpful in any way.

[nathanjackson]

I can confirm I'm having the same issue.

GTX 1080 Ti
Driver/LLVM version: nvidia 440.64
Kernel version: 5.5.8
Proton version: 5.0-4

steam-782330.log

[Berinth]

steam-782330.log

Me too.

Ryzen R7 3700x
5700XT
kernel 5.5.9
Proton 5.0.4

[Tbird761]

steam-782330.log

Same experience on my end. The game launches, I see the tray icon, and then the game exits. Nothing but the icon ever draws on screen. I'm not dumped out of the loading screen or main menu or anything.

I tried running it with AMDVLK, and that is the run this log is for.

Debian Testing (mostly)
Kernel 5.5.0 RC5
Proton 5.0-4

AMD TR 2990WX
AMD Radeon VII
96 GB RAM

amdvlk/Ubuntu 18.04,now 2020.Q1.3 amd64 [installed]
libvulkan-dev/testing,unstable,now 1.2.131.2-1 amd64 [installed]
libvulkan1/testing,unstable,now 1.2.131.2-1 amd64 [installed]
mesa-vulkan-drivers/experimental,now 20.0.0-1 amd64 [installed]
vulkan-tools/testing,now 1.1.126.0+dfsg1-1 amd64 [installed,automatic]
vulkan-utils/testing,testing,now 1.1.126.0+dfsg1-1 all [installed]

[rabidlassie]

Here is my log as well. Same issues mentioned above.

• GPU: RTX 2070
• Driver/LLVM version: nvidia 440.64
• Kernel version: 5.4.24-1-MANJARO
• Link to full system information report as Gist: https://gist.github.com/rabidlassie/7c3ab9a232a152aa9e7a684aec86f1ee
• Proton version: 5.0-4

steam-782330.log

[CoatlessEskimo]

steam-782330.log

OS: Arch Linux
KERNEL: 5.5.8-zen1-1-zen
CPU: AMD Ryzen 5 2600 Six-Core
GPU: NVIDIA GeForce GTX 1070
GPU DRIVER: NVIDIA 440.64

Same issue as mentioned above. The game will appear as "playing" on Steam, and then nothing will happen, followed by being returned to "Online" status.

[GodfatherOfBandwidth]

Same issue as all the others:

steam-782330.log

GPU: AMD RX480
Driver: AMDGPU-Pro-19.50-967956
Vulkan Instance Version: 1.2.131
Kernel: 4.15.0-91 (Linux Mint 19.3)

[smclenithan]

Same issue:
steam-782330.log

GPU: 8 GB GTX 1070
Driver: 440.44
OS: Pop!_OS 19.10
Proton version: 5.0-4

Using the Steam Beta client.

[LarsBremen]

I do get an error message when starting the game

Unable to initialize SteamAPI.
Please make sure Steam is running and you are
logged in to an account entitled to the game.

Here my log: steam-782330.log

• GPU: Nvidia GTX 1070
• CPU: Intel i5 7600k
• OS: Kubuntu 18.04

I get this message when starting the game using Proton 3.16-9

Log when forcing proton 5.0-4: steam-782330.log

[wiltaylor]

steam-782330.log

Tried with steam-runtime with the beta mentioned above and get the same problem it crashes shortly after running.

GPU: Nvidia RTX 2080
CPU: i7 7820HK
OS: Arch
Graphics Driver: 440.64-5
Kernel: 5.5.10-arch1-1

[xA8EYLgMSN43oEHC]

Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.

[Newbytee]

Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.

Out of curiosity, which version of the NVIDIA driver do you have installed?

[UVCRocketRunner]

I have the same problem as the original poster, just gives me the Wine system tray and then stops.

I am running:
Fedora 31
i7-3770K
GTX 1050Ti, driver v. 440.64.
steam-782330.log

[xA8EYLgMSN43oEHC]

Out of curiosity, which version of the NVIDIA driver do you have installed?
440.64-0ubuntu0~0.18.04.2

[wiltaylor]

I just tried Prton-5.4-GE-1 too and got the GPU Driver Error page @xA8EYLgMSN43oEHC did above too. I am using arch so the version of the driver I have is 440.64-5.

[pKrysenko]

Steam log on proton-5.4.GE-1, i am using:
elementary OS 5.0
GPU: gtx 1050ti driver 440.64
steam-782330.log

[silviucc]

Adding logs for proton 4.11 and 5.0.4 along with steam hw and lib info:
steam-782330_proton411.log
steam-782330_proton504.log
steam_hw_info.txt

[AllKind]

Thanks @rabidlassie & @gardotd426
here with proton log...
steam-782330.log

Linux Mint 19.3
Kernel 5.5.9
Nvidia driver 440.64
steam beta.
Proton 5.0-4

[fls2018]

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).

Not true, latest driver is vulkan dev beta 440.66.03 which is for Vulkan 1.2:

https://developer.nvidia.com/vulkan-driver

[dpanter]

Tried latest Valve, TkG, GE Protons. GE asks about driver being version 337.88 like previously posted, click Play, then nothing. The others do nothing at all.

Using Siduction (Debian sid based) kernel 5.5.10-towo.1-siduction-amd64
Intel 8700k, 32GB RAM, Nvidia 1080Ti 440.64, KDE 5.17.5
steam-system-info.txt

All tests with fresh Proton prefix generated. Tried using +com_skipSignInManager 1 with GE but nothing really changed except for the log file size.
steam-782330.proton5.0-4.log
steam-782330.proton_tkg_5.4.r0.g676dd026.release.log
steam-782330.Proton-5.4-GE-1.log
steam-782330.Proton-5.4-GE-1_+com_skipSignInManager_1.log

[MuchiMuchiPink]

I have the exact same issues with the bethesdalauncher version and lutris.

[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).

Not true, latest driver is vulkan dev beta 440.66.03 which is for Vulkan 1.2:

https://developer.nvidia.com/vulkan-driver

Thanks for that I didn't know they kepts a separate page for Vulkan.. Accoding to their docs:

Vulkan 1.2 support is available in Windows driver version 442.75 and Linux driver version 440.66.02

So anyone in Linux with the driver lower than that version shouldn't stand a chance. Did anone tryy with 440.66.03?

[FTL-Space-Warp]

Did anone tryy with 440.66.03?

Would that have any chance of working? If it doesn't work, how long would we have to wait for a new driver release?

[xDShot]

Crash reports are enabled with +com_enableCrashHandler 2

[xDShot]

crashreport1.zip
x64_20200313-173912-viridian-salmon_0.zip

[APoniatowski]

is there any way of bypassing the launcher and run the actual executable/binary?

[pastapojken]

is there any way of bypassing the launcher and run the actual executable/binary?

AFAIK, adding +com_skipSignInManager 1 as a launch option should do it, but the game still crashes after that (at least for me on AMD)

[JusterK]

steam-782330.log

• Gentoo / sway-1.4
• Kernel 5.5.9
• Mesa 20.0.1 (RADV+ACO) / vulkan-loader-1.2.135
• Steam stable
• Proton 5.0-4
• GPU: Navi (AMD RX5700)

[jalabb]

Just tried 440.66.03, it doesn't change anything.

[silviucc]

Just a heads up. This game seems to be infested with Denuvo. I get this on Windows:

https://support.codefusion.technology/de_d90127jd781/?e=88500006&l=english

Currently your game purchase cannot be re-validated successfully, please wait 24 hours and try again.

[e-user]

steam-782330.log

• Fedora 31 Silverblue
• Linux 5.5.9
• nVidia 440.64
• Steam Flatpak 1.0.0.61 (stable)
• Proton 5.0-4
• GeForce GTX 1080 Ti
• Launched with PROTON_LOG=1 %command% +com_skipSignInManager 1

FWIW, replacing idTechLauncher.exe with DOOMEternalx64vk.exe doesn't make a difference. Also, I tried with a Denuvo-less binary as documented on a subreddit, same results.

[Comminux]

https://www.vg247.com/2020/03/20/doom-eternal-denuvo-free-exe/

We need to try use this leaked executable file.

[e-user]

steam-782330.log

Same as above but with the Denuvo-free binary, see my previous comment.

[oscarcp]

Sorry if this isn't useful at all, but I keep seeing ELF incompatibility errors on all the logs. As far as I know Steam on Linux uses 32bit binaries and libraries. Maybe DOOM Eternal only has a 64bit build?

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

In my last log i caught this, which I haven't seen in other logs:

38872.096:0037:0038:warn:seh:virtual_unwind exception data not found in L"DOOMEternalx64vk.exe" Unhandled exception: page fault on write access to 0x23377774 in 64-bit code (0x0000000148d71006). 38872.100:0039:003a:fixme:dbghelp:elf_search_auxv can't find symbol in module

Full log:
steam-782330.log

[e-user]

Sorry if this isn't useful at all, but I keep seeing ELF incompatibility errors on all the logs. As far as I know Steam on Linux uses 32bit binaries and libraries. Maybe DOOM Eternal only has a 64bit build?

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

These errors occur with every game using the Steam overlay and can be safely ignored.

[MuchiMuchiPink]

@oscarcp I have seen this in Lutris as well, but only when executing the binary directly I think. Is this correct for you as well? I tested through launcher etc so I'm not sure where I've seen it.
I think you mean the seh:virtual_unwind part, right?

[oscarcp]

@oscarcp I have seen this in Lutris as well, but only when executing the binary directly I think. Is this correct for you as well? I tested through launcher etc so I'm not sure where I've seen it.
I think you mean the seh:virtual_unwind part, right?

I mean the Unhandled exception: page fault on write access to 0x23377774 in 64-bit code (0x0000000148d71006) part, but don't worry. I'm runnin it throught Steam beta as usual, no changes or ;aunch parameters besides the proton log

[mozo78]

Sorry if this isn't useful at all, but I keep seeing ELF incompatibility errors on all the logs. As far as I know Steam on Linux uses 32bit binaries and libraries. Maybe DOOM Eternal only has a 64bit build?

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

In my last log i caught this, which I haven't seen in other logs:

38872.096:0037:0038:warn:seh:virtual_unwind exception data not found in L"DOOMEternalx64vk.exe" Unhandled exception: page fault on write access to 0x23377774 in 64-bit code (0x0000000148d71006). 38872.100:0039:003a:fixme:dbghelp:elf_search_auxv can't find symbol in module

Full log:
steam-782330.log

I tried with Wine, without Steam, with denuvoless .exe and the game doesn't work. We're waiting for Valve and NVIDIA to step in!

[gardotd426]

It's nothing to do with Nvidia, the game doesn't work with AMD either. It's
up to Valve, Bethesda and iD now whether or not we'll get to play this
game.

On Fri, Mar 20, 2020 at 8:37 AM mozo78 [e-mail] wrote:

Sorry if this isn't useful at all, but I keep seeing ELF incompatibility
errors on all the logs. As far as I know Steam on Linux uses 32bit binaries
and libraries. Maybe DOOM Eternal only has a 64bit build?

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

In my last log i caught this, which I haven't seen in other logs:

38872.096:0037:0038:warn:seh:virtual_unwind exception data not found in
L"DOOMEternalx64vk.exe" Unhandled exception: page fault on write access to
0x23377774 in 64-bit code (0x0000000148d71006).
38872.100:0039:003a:fixme:dbghelp:elf_search_auxv can't find symbol in
module

Full log:
steam-782330.log
https://github.com/ValveSoftware/Proton/files/4359487/steam-782330.log

I tried with Wine, Without Steam, with denuvoless .exe and the game
doesn't work. We're waiting for Valve and NVIDIA to step in!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601678490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33Z53PQYFI76MJ4UAV3RINPRJANCNFSM4LP25FOQ
.

[scottlinux]

There is a small file here:
~/.steam/steam/steamapps/common/DOOMEternal/launcherData/launcher.cfg

This file has the GPU driver warning pop-ups, and such. Move that file out of the way to disable all of those options and bypass that driver version screen.

rgl_minNvidiaDriverVersion 44261
rgl_minAMDDriverMajorVersion 20
rgl_minAMDDriverMinorVersion 2
rgl_minAMDDriverPatchVersion 2
rgl_minAMDDriverMajorVersionWin8 19
rgl_minAMDDriverMinorVersionWin8 10
rgl_minAMDDriverPatchVersionWin8 1
rgl_minAMDDriverMajorVersionWin7 20
rgl_minAMDDriverMinorVersionWin7 2
rgl_minAMDDriverPatchVersionWin7 2
rgl_showAMDStartupWarning 1
rgl_showIntelStartupWarning 1
rgl_showNvidiaStartupWarning 0

[MuchiMuchiPink]

@oscarcp I see, no I get this everytime through the Bethesdalauncher or the binary itself. unfortunatley this doesn't seem to help much.
I have AMD as well.

[rassie]

I can remember that DOOM (2016) could not properly run under Wine initially until Denuvo has been removed several months after release. Obviously, the situation is a bit different now with Proton, but I wouldn't be surprised if Denuvo became a major roadblock in supporting DOOM Eternal.

[MuchiMuchiPink]

Correct me if I'm wrong but the denuvo issue was because of a wrong bcrypt implementation, right?
This is what I see before the page fault, but just warnings.

0141:fixme:bcrypt:BCryptCreateHash ignoring object buffer 00d5:fixme:bcrypt:BCryptCreateHash ignoring object buffer 00d0:fixme:bcrypt:BCryptCreateHash ignoring object buffer 0197:fixme:bcrypt:BCryptCreateHash ignoring object buffer wine: Unhandled exception 0x80000003 in thread d5 at address 0000000140822876 (thread 00d5), starting debugger...

[mozo78]

Denuvo isn't the culprit here I think. I start the game with the leaked DRM Free exe and it doesn't start with pretty the same errors.

[FTL-Space-Warp]

@mozo78 I hope you're right, on that note a report on protondb is saying that the launcher works and only the main game crashes, if it's true it's promising.

[e-user]

@mozo78 I hope you're right, on that note a report on protondb is saying that the launcher works and only the main game crashes, if it's true it's promising.

I'd prefer if it were the other way around.

[APoniatowski]

additional steps taken:

• [x] installed/added Proton-5.4-GE-1
• [x] ran game with Proton-5.4-GE-1
• [x] renamed launcher.cfg after renaming idTechLauncher.exe and copying DOOMEternalx64vk.exe as idTechLauncher.exe
• [x] commented all options in launcher.cfg, with same steps as above
• [x] PROTON_LOG=1 %command% +com_skipSignInManager 1

I think it might be the game's binary, that's the issue (DOOMEternalx64vk.exe),

00000031 idTechLauncher.exe
    ["Z:\run\media\sizigee\Games\Steam\steamapps\common\DOOMEternal\idTechLauncher.exe" +com_skipSignInManager 1]
    00000035   -2
    00000034    0
    00000032    0
00000036 (D) Z:\run\media\sizigee\Games\Steam\steamapps\common\DOOMEternal\DOOMEternalx64vk.exe
    [DOOMEternalx64vk.exe +com_enableCrashHandler 0 +com_skipSignInManager 1]
    00000044    0
    00000043    0
    00000042    0
    00000041    0
    00000040    0
    0000003f    0
    0000003e    0
    0000003d    0
    0000003c    0
    0000003b    0
    0000003a    0
    00000039   -1
    00000037    2 <==

but I could be far off too.
steam-782330.log

[mozo78]

@Guy1524
Can you fix it like MK11 :)

[favonius85]

Another report with some different AMD hardware.

System Information

GPU: Radeon 7
Driver/LLVM version: Mesa 20.1.0-devel / LLVM 11.0.0
Kernel version: 5.5.9-200.fc31.x86_64
Proton version: 5.0-4

steam-782330.log
sysinfo.txt

[rkfg]

Another interesting option that Doom itself suggests is +in_terminal 1. I guessed it from the terminal output of the game: Terminal support disabled. Enable with in_terminal
With it the error is a bit more clear:

------ Initializing File System ------
Current search path:
    - C:/users/rkfg/Saved Games/id Software/DOOMEternal/base/
    - Z:/.../DOOMEternal/base/
------ File System initialized.
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
----- Registering decl types -----
----- Starting decls parse jobs -----
Added structured log listener print-redirect
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
------ Command Line ------
 Z:\...\DOOMEternal\DOOMEternalx64vk.exe +com_skipSignInManager 1 +in_terminal 1
2020-03-20T17:37:24.439+03:00 LOG: Command Line: Z:\...\DOOMEternal\DOOMEternalx64vk.exe +com_skipSignInManager 1 +in_terminal 1
------ OS Information ------
    Microsoft Windows 7 Build 7601

------ CPU Information ------
    Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    1 CPU package, 4 physical cores, 8 logical cores
    4.2 GHz     Intel CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX & HTT
    32768 kB 1st level cache, 262144 kB 2nd level cache, 8388608 kB 3rd level cache
    31.33 GB System Memory

idLib::SetProduction( PROD_PRODUCTION )
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
Initialized stack tracer
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.
wine: Unhandled exception 0x80000003 in thread 26 at address 0000000140822876 (thread 0026), starting debugger...

A couple of points: this is a denuvo-free binary (you know) and I run it with pure Wine 5.2, not Proton. However, I hope it's helpful anyway. Tried with both stable (440.59) and Vulkan developer (440.66.03) driver. No difference and this extension it complains about is kinda old.

[gardotd426]

That looks like it needs the same wine build that @doitsujin was referring
to earlier

On Fri, Mar 20, 2020 at 10:40 AM rkfg [e-mail] wrote:

Another interesting option that Doom itself suggests is +in_terminal 1. I
guessed it from the terminal output of the game: Terminal support
disabled. Enable with in_terminal
With it the error is a bit more clear:

------ Initializing File System ------
Current search path:

• C:/users/rkfg/Saved Games/id Software/DOOMEternal/base/
• Z:/.../DOOMEternal/base/
  ------ File System initialized.
  WARNING: idBroadcastManager::Register called with out of range system ID [65535]
  ----- Registering decl types -----
  ----- Starting decls parse jobs -----
  Added structured log listener print-redirect
  WARNING: idBroadcastManager::Register called with out of range system ID [65535]
  WARNING: idBroadcastManager::Register called with out of range system ID [65535]
  ------ Command Line ------
  Z:...\DOOMEternalDOOMEternalx64vk.exe +com_skipSignInManager 1 +in_terminal 1
  2020-03-20T17:37:24.439+03:00 LOG: Command Line: Z:...\DOOMEternalDOOMEternalx64vk.exe +com_skipSignInManager 1 +in_terminal 1
  ------ OS Information ------
  Microsoft Windows 7 Build 7601

------ CPU Information ------
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
1 CPU package, 4 physical cores, 8 logical cores
4.2 GHz Intel CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX & HTT
32768 kB 1st level cache, 262144 kB 2nd level cache, 8388608 kB 3rd level cache
31.33 GB System Memory

idLib::SetProduction( PROD_PRODUCTION )
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
Initialized stack tracer
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.
wine: Unhandled exception 0x80000003 in thread 26 at address 0000000140822876 (thread 0026), starting debugger...

A couple of points: this is a denuvo-free binary (you know) and I run it
with pure Wine 5.2, not Proton. However, I hope it's helpful anyway. Tried
with both stable ( and Vulkan developer driver

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601734731,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333BMGXARVKHZCBS3I3RIN55RANCNFSM4LP25FOQ
.

[APoniatowski]

ran what @rkfg did with +in_terminal 1, log looks bigger now.
steam-782330.log

[rkfg]

@gardotd426 ah yes, I'm a bit late to the party it seems. I guess if this is the only issue that prevents it from running we'll have it up in no time.

[OrdinaryMagician]

Finally some good news. Hope this doesn't take long to solve.

[rkfg]

@APoniatowski interesting that there's no information about your CPU and that Vulkan extension in your log. This option might be working only in the developer build that Bethesda accidentally leaked.

[mozo78]

But VK_KHR_get_surface_capabilities2 is present in all drivers already. It's there for Mesa too.

[gardotd426]

Not as far as Wine is aware, is the issue.

On Fri, Mar 20, 2020 at 10:55 AM mozo78 [e-mail] wrote:

But VK_KHR_get_surface_capabilities2 is present in all drivers already.
It's there for Mesa too.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601742031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33ZERDUZ4E2HJ6ZEYYLRIN7WPANCNFSM4LP25FOQ
.

[APoniatowski]

@rkfg Here's my system info, if that helps. The steam beta should have the latest vulkan loader, like @kisak-valve mentioned earlier
system-info.txt

[gardotd426]

@mozo78 https://github.com/ValveSoftware/wine/pull/85

[mozo78]

Ah, I see. Thanks :)

[dxgldotorg]

March 19, 2020 Beta client
Proton 5.0-4
NVIDIA 440.64
Game fails to start. Tried a trick that got DOOM Eternal running on Windows which was copy DOOMEternalx64vk.exe over idTechLauncher.exe and no difference.

[zaggynl]

System Information
GPU: AMD 5700XT
Driver/LLVM version: LLVM 9.0.1
Kernel version: 5.5.10
Proton version: 5.0-4
Link to full system information report as Gist: https://gist.githubusercontent.com/zaggynl/5812f8efa63bfc1d71a0f9aa1d38ee24/raw/508103729dab2ce6aa7bc079bae810b8c13a1284/sysinfo%2520zaggynl
Steam beta build as of 2020-03-19 @ 22:39:54
steam-782330.log

[makusu2]

People are making it sound like https://github.com/ValveSoftware/wine/pull/85 is the only thing left to do; don't we still have to wait for Denuvo to be removed as well?

[e-user]

People are making it sound like the PR is the only thing left to do; don't we still have to wait for Denuvo to be removed as well?

It depends. We do have a Denuvo-less binary to test against, and it may just happen it'll even work with Denuvo active.

[PraetorianSC4]

People are making it sound like ValveSoftware/wine#85 is the only thing left to do; don't we still have to wait for Denuvo to be removed as well?

Not necessarily?

See: https://github.com/ValveSoftware/Proton/releases

Fix Denuvo DRM failures in Just Cause 3 and Batman Arkham Knight.

While a DRM free version of the executable is preferable, it's presence does not necessitate a failure of running the game and playing it performantly.

[MacroHard-sys]

Sorry guys, I don't think I get it.

Uninstalled wine.
I downloaded wine 5.2 source and compiled it with the replacement files from ValveSoftware/Wine#85 by editing the files in the folders and saving them. Compiled and installed with ./configre and make.

Installed proton 5.4-GE-1. Rebooted steam. Same failed result. Am I supposed to try to run outside of Steam? Result is this:

wine blahblah/.steam/steam/steamapps/common/DOOM/DOOMx64vk.exe'
002b:fixme:heap:RtlSetHeapInformation 0x7a0000 0 0x32e380 4 stub
002b:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
002b:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
002b:err:module:LdrInitializeThunk "winevulkan.dll" failed to initialize, aborting
002b:err:module:LdrInitializeThunk Initializing dlls for L"Z:\home\user\.steam\steam\steamapps\common\DOOM\DOOMx64vk.exe" failed, status c0000142

Do you guys like, have it working? What'd ya do?

[mozo78]

I think you need to compile Proton, not Wine. There are Vulkan games that runs only with Proton like No Man's Sky for example. If you try to run NMS with Wine, it gives the same libvulkan.so.1 error.

[makusu2]

The PR is for Valve's wine fork, not proton, though...?

[MacroHard-sys]

I think you need to compile Proton, not Wine. There are Vulkan games that runs only with Proton like No Man's Sky for example. If you try to run NMS with Wine, it gives the same libvulkan.so.1 error.

Makes sense.

But HOOWWWW

[e-user]

Actually, Wine is compiled with Proton as a Git Submodule. What you'd need to do is clone Proton, init the submodules and change the wine submodule to point at the repo and branch of the pull request, then compile Proton (which compiles Wine along the way). Also, you need to have Vulkan development files installed.

[PraetorianSC4]

Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.

So I got this too. The question is, why does the launcher think you have a driver from late 2016 rather than 440+, which is 2020. I wonder if there's a driver string in the launcher that is getting mismatched somehow?

[Kron4ek]

Did someone managed to compile Proton with this PR applied? It applies correctly, but it doesn't compiles. Despite that i have the latest (1.2.135) Vulkan-Loader and Vulkan-Headers installed, i get multiple compilation errors:

../../../wine/dlls/winevulkan/vulkan.c:2724:11: error: unknown type name ‘VkPhysicalDeviceSurfaceInfo2KHR’
 2724 |     const VkPhysicalDeviceSurfaceInfo2KHR*      pSurfaceInfo,
  |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../../wine/dlls/winevulkan/vulkan.c:2725:5: error: unknown type name ‘VkSurfaceCapabilities2KHR’; did you mean ‘VkSurfaceCapabilitiesKHR’?
 2725 |     VkSurfaceCapabilities2KHR*                  pSurfaceCapabilities)
  |     ^~~~~~~~~~~~~~~~~~~~~~~~~
  |     VkSurfaceCapabilitiesKHR
../../../wine/dlls/winevulkan/vulkan.c:2752:11: error: unknown type name ‘VkPhysicalDeviceSurfaceInfo2KHR’
 2752 |     const VkPhysicalDeviceSurfaceInfo2KHR*      pSurfaceInfo,

This is just fragment, actually there are more errors.

By the way, TkG repo contains the patch for VK_KHR_get_surface_capabilities2 extension for regular Wine (and for Staging). Unfortunately, this patch doesn't add VK_EXT_full_screen_exclusive, which is also required for Doom Eternal.

[Kron4ek]

Edit. Proton 5.0-5 has been released and the game works on it, editing the game's exe with sed is not required anymore. However, you still need to install the latest Vulkan-Loader (1.2.135) and probably still need to replace the game's exe with the DRM-Free version.

I got the Doom Eternal working by compiling Wine-Staging with the patch from TkG repo and replacing strings with VK extensions in the game executable (yes, this dumb as f**k, but at least this allow the game to launch). Also the latest (1.2.135) Vulkan-Loader is required.

For example, i replaced vkAcquireFullScreenExclusiveModeEXT with vkCreateDescriptorUpdateTemplateKHR, i also replaced VK_EXT_full_screen_exclusive with VK_EXT_sampler_filter_minmax. I used sed for this purpose.

sed -i 's/vkAcquireFullScreenExclusiveModeEXT/vkCreateDescriptorUpdateTemplateKHR/g' DOOMEternalx64vk.exe
sed -i 's/VK_EXT_full_screen_exclusive/VK_EXT_sampler_filter_minmax/g' DOOMEternalx64vk.exe

Here is another variant that works better:

sed -i 's/vkAcquireFullScreenExclusiveModeEXT/vkGetImageSparseMemoryRequirements2/g' DOOMEternalx64vk.exe
sed -i 's/VK_EXT_full_screen_exclusive/VK_EXT_shader_stencil_export/g' DOOMEternalx64vk.exe

Replaced strings should have the same length as the original strings (it's important, otherwise the executable will not launch at all).

The game often hangs or crashes before entering the main menu, multiple attemps may be required.

I was able to get into main menu, but only once, on the next run the game hanged again:

After multiple attempts i was able to ge into main menu again and start the campaign:

Here is the video of gameplay (sound works, i just didn't record it). Don't look at the performance, i'm pretty sure it's bad because of this dirty way to run the game.

I've only tried DRM-Free executable, so can't say if the Denuvo version can be launched this way.

I will continue to experiment with strings, maybe i will get the game completely working.

p.s. Sorry for grammar mistakes, English is not my native language (but i'm improving it constantly).

[PraetorianSC4]

@Kron4ek what OS are you using? I'm looking at the vulkan-cd-loader availability on Manjaro, and only see up to 1.2.132-1. Am curious to know how you got your hands on 1.2.135.

[gardotd426]

@makusu2 Resident Evil 2 worked the whole time Denuvo was still a part of the game, they didn't remove Denuvo from RE2 until very, very recently. Denuvo's presence doesn't mean all that much, it will most likely still work.

@MacroHard-sys, all you did was install a new version of Wine to your SYSTEM with the PR. Proton uses Wine built-in, not system Wine. You don't even need Wine installed on your system to use Proton, specifically because Proton doesn't use your system's Wine at all.

You would need to compile Proton with the PR, and use that version of Proton to try and run the game.

@Kron4ek it seems like we should be able to get it working, then, it just may take a few days for Valve to accept the PR and figure out the last few kinks.

[ashkitten]

just tried patching the game executable (from steam) with @Kron4ek's commands, no dice. gives a small window with the id logo and then quits. i'm still working on building proton with the patches, will report if it works with that.

[Kron4ek]

@pastapojken I'm using Arch Linux, i compiled the latest vulkan-icd-loader manually.

[PraetorianSC4]

just tried patching the game executable (from steam) with @Kron4ek's commands, no dice. gives a small window with the id logo and then quits.

You have to recompile and install wine using TkG's patch with those string replacements and 1.2.135 of the vulkan-icd-loader and headers for it to work.

@Kron4ek gotcha.

[mozo78]

So, do we need vulkan-icd-loader 1.2.135 installed or patched Proton will suffice?

[wundrweapon]

@mozo78 you'll need the latest loader/headers installed, presumably for added features that the game makes use of

[ashkitten]

So, do we need vulkan-icd-loader 1.2.135 installed or parched Proton will suffice?

it seems like if you're using wine outside of proton then you need vulkan-icd-loader, but proton will use the steam runtime otherwise which should contain the correct version if you've opted into the beta version of steam

[mozo78]

Thank you. It gets harder and harder...

[wundrweapon]

@Kron4ek have you tried running the game with +com_skipSignInManager 1 in Steam launch options?

[PraetorianSC4]

According to DX4400 on the steam forums, you can add: +com_skipKeyPressOnLoadScreens 1 which disables the press spacebar to continue and just loads the game into the level. @Kron4ek if you're getting hangs during initial loads, maybe this might help.

Additional tweaks here: DOOT ETERNAL LAUNCH TWEAKS

[liberodark]

Better use :

+com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

[liberodark]

So, do we need vulkan-icd-loader 1.2.135 installed or patched Proton will suffice?

need to use vulkan-icd-loader & patch

[gardotd426]

@liberodark the steam-runtime beta Steam build contains the required vulkan versions, it should only be steam-native which disables the Steam runtime that requires those vulkan versions installed on the system, see what @kisak-valve said above.

[liberodark]

Im speak for launch without steam-runtime im not use this.

[gardotd426]

@liberodark steam-runtime and Steam For Linux Runtime are two different things, the first one is just Steam with builtin libraries, and is the default manner for launching the game in distributions like Manjaro. If you just run steam, it'll be running steam-runtime. The second is a compatibility layer, like Proton before Proton came out. It's what you can use to try and launch some games in the properties, like where you choose Proton versions.

considering that the required version of the vulkan-icd-loader and headers isn't even available for most Linux users without heavy manual intervention, Steam should definitely be run with the steam-runtime and not steam-native version, for right now.

[Kron4ek]

@Kron4ek have you tried running the game with +com_skipSignInManager 1 in Steam launch options?

Sorry, I didn't buy the game yet, so for now i'm only experimenting with the DRM-Free executable.
Though, I tried this argument on the DRM-Free executable, for some reason it doesn't work for me, the game still asks for login into Bethesda account. However, disabling internet connection works.

After multiple attemps i was able to get into main menu and start the campaign. Here is the video, i also edited my post above.

[liberodark]

It's nice to explain it to me but I know the difference well I worked on the two I admit that the containerization is very interesting.

[liberodark]

@Kron4ek good video :D

[gardotd426]

@Kron4ek so it looks like the game should work as soon as Valve fixes a couple things.

Maybe you could try explaining the EXACT process you used from beginning to end (after obtaining the game of course) to get it to work, so others can try and reproduce. Including whether you used the steam runtime or if not how you obtained and built the needed version of vulkan-icd-loader.

[Kron4ek]

@gardotd426 Yes, looks like the game should be completely playable after merging the 85 PR. Well, at least the DRM-Free should work, but i guess the Denuvo version will work too.

[gardotd426]

I've never had an issue with the few Denuvo games I've tried on Linux,
Resident Evil 2 worked fine even before they removed it. So that's one
reason for hope. We'll have to wait for word from Valve, I suppose. Or TKG
or GE, if nothing else.

On Fri, Mar 20, 2020 at 3:39 PM Kron4ek [e-mail] wrote:

@gardotd426 https://github.com/gardotd426 Yes, looks like the game
should be completely playable after merging the 85 PR
https://github.com/ValveSoftware/wine/pull/85/commits. Well, at least
the DRM-Free should work, but i guess the Denuvo version will work too.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601878901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33ZXPWHPJSRJ4753NADRIPA7VANCNFSM4LP25FOQ
.

[ReaperOfSouls1909]

can someone link me to vulkan-icd-loader aur

[liberodark]

no need aur

NVIDIA :

sudo pacman -S nvidia nvidia-utils lib32-nvidia-utils nvidia-settings vulkan-icd-loader lib32-vulkan-icd-loader

AMD :

sudo pacman -S lib32-mesa vulkan-radeon lib32-vulkan-radeon vulkan-icd-loader lib32-vulkan-icd-loader

INTEL :

sudo pacman -S lib32-mesa vulkan-intel lib32-vulkan-intel vulkan-icd-loader lib32-vulkan-icd-loader

[gardotd426]

@ReaperOfSouls1909 it's not in the AUR, it's in the official repos. You'll have to use something like svn to checkout the repo PKGBUILD, and manually edit it.

@liberodark that doesn't do them any good, the repo versions aren't new enough, they need .135, not .132. so just sudo pacman -S ... won't help them at all.

[ReaperOfSouls1909]

sudo pacman -S nvidia nvidia-utils lib32-nvidia-utils nvidia-settings vulkan-icd-loader lib32-vulkan-icd-loader

wrong version numbers that way

[ReaperOfSouls1909]

Vulkan-icd-loader-1.2.135-PKGBUILD.zip
found one

[oscarcp]

can someone link me to vulkan-icd-loader aur

I havve the AUR PKGBUILDs for both loader and header in a comment earlier in this ticket if yyou need them, but as they said steam-runtime should load their internal 1.2.135 versions

[ReaperOfSouls1909]

can someone link me to vulkan-icd-loader aur

I havve the AUR PKGBUILDs for both loader and header in a comment earlier in this ticket if yyou need them, but as they said steam-runtime should load their internal 1.2.135 versions

saw that thanks zipped it up above

[liberodark]

ok

[Niedzwiedzw]

same problem, any quick way to run this?

[liberodark]

you need last vulkan-icd-loader

[Niedzwiedzw]

pacman -S vulkan-icd-loader ?

[werman]

For people with Radeon GPU: use vulkan driver from amdgpu-pro, it runs much better than amdvlk (also seem not to hang every 10 minutes). With it I have stable 120+ fps with 5700 XT in 1440p + high settings.

[ReaperOfSouls1909]

pacman -S vulkan-icd-loader ?

no use this pkgbuild
Vulkan-icd-loader-1.2.135-PKGBUILD.zip

[gardotd426]

@Niedzwiedzw no, that doesn't give an up-to-date enough version.

You have to download the zip above

[gardotd426]

@werman how did you get it to run?

[liberodark]

oh is not authorized to share wine tkg ? @ValveSoftware

[kisak-valve]

Hello @liberodark, while it's okay to share Proton builds, it's not okay to share game executables, and the link you used is region locked so I couldn't look closer to evaluate beyond your description of the contents.

[liberodark]

ok im make version without that

[werman]

@gardotd426 At what step do you have issues?

[gardotd426]

Someone needs to clearly explain how to get it to run, this thread is an absolute mess right now.
@werman:

1. How did you get it to run. What version of Steam are you running, steam-native or steam-runtime? What launch options, what version of Proton?
2. Where did you get the pro version of amd's vulkan driver? On Arch, it's months out of date and only up to 19.30.

It doesn't help anyone if there's not even a semblance of a step-by-step guide when all of these workarounds are needed at the moment.

[Niedzwiedzw]

@ReaperOfSouls1909 how do i do that? :O

[gardotd426]

@Niedzwiedzw
https://wiki.archlinux.org/index.php/Makepkg

[liberodark]

New link just pure wine tkg precomplied version : https://drive.google.com/open?id=1_pPRwztcq_Vp6IKGAXo-XIrnicizZqlk

patch your game exe :

sed -i 's/vkAcquireFullScreenExclusiveModeEXT/vkGetImageSparseMemoryRequirements2/g' DOOMEternalx64vk.exe
sed -i 's/VK_EXT_full_screen_exclusive/VK_EXT_shader_stencil_export/g' DOOMEternalx64vk.exe

[winteriscariot]

It doesn't help anyone if there's not even a semblance of a step-by-step guide when all of these workarounds are needed at the moment.

@gardotd426 give it a bit my dude, this thread is hyper-active and it would be good to show some patience. we have a lot of people doing great work, give them a minute to catch their breath and get things in order.

[liberodark]

have some error in your pkgfile @ReaperOfSouls1909 better share compiled version

[kisak-valve]

@liberodark, taking a look at the wine build you shared, it contain a legally problematic workaround and and has been removed.

[ReaperOfSouls1909]

not my script @oscarcp made it if there is an error im not the one to go to

vulkan-icd-loader-1.2.135-1-x86_64.pkg.zip

[liberodark]

but no have share any files bad or illegal juste is tkg have better solution.
Im go to make pure wine version @kisak-valve

[Voxed]

Had to disable ACO for Vulkan 1.2.135 to be used.

Otherwise the game runs great after all the workarounds.

[liberodark]

@kisak-valve have updated the link look is only wine tkg pre compiled with a patch for doom

[PraetorianSC4]

Had to disable ACO for Vulkan 1.2.135 to be used.

Otherwise the game runs great after all the workarounds.

So that we understand correctly, you installed 1.2.135. Is there anything else you did besides disabling ACO (and how did you do that for that matter) to get the game to run? Did it involve leveraging the wine modification for DOOT Eternal?

[Kron4ek]

Edit. Proton 5.0-5 has been released and the game works on it, editing the game's exe with sed is not required anymore. However, you still need to install the latest Vulkan-Loader (1.2.135) and probably still need to replace the game's exe with the DRM-Free version.

Ok, here is the pretty short instruction about how to run the game with the DRM-Free exe:

1. Install latest videodrivers for your GPU (probably not required, but highly recommended)
2. Install the latest (1.2.135) Vulkan-Loader and Vulkan-Headers. Compile them manually or find some repo.
3. Compile the latest Wine-Staging with this patch applied
4. Replace the game executable with the DRM-Free version (can't post the link here, but it can be finded pretty easily)
5. Perform this commands inside the game directory:

    sed -i 's/vkAcquireFullScreenExclusiveModeEXT/vkGetImageSparseMemoryRequirements2/g' DOOMEternalx64vk.exe
    sed -i 's/VK_EXT_full_screen_exclusive/VK_EXT_shader_stencil_export/g' DOOMEternalx64vk.exe

1. Run the game exe (DOOMEternalx64vk.exe) using the Wine-Staging that you compiled in step 3

As i said before, the game often crashes or hangs before entering the main menu, so multiple game restarts may be required.

[gardotd426]

@PraetorianSC4 unless you have RADV_PERFTEST=aco in either your /etc/environment, ~/.profile, ~/.zprofile, ~/.zshrc, ~/.bashrc, etc, or in the launch options (so basically unless you have manually enabled ACO, it's not enabled by default. If you've got it enabled elsewhere, you can use RADV_PERFTEST=llvm.

@Voxed, are you running the Steam version or DRM-free version? If not the Steam version, has anyone actually gotten the Steam version to work yet?

[liberodark]

The pre compiled version of wine is here : https://drive.google.com/file/d/1_pPRwztcq_Vp6IKGAXo-XIrnicizZqlk/view?usp=sharing only wine

[Voxed]

@PraetorianSC4 unless you have RADV_PERFTEST=aco in either your /etc/environment, ~/.profile, ~/.zprofile, ~/.zshrc,~/.bashrc, etc, or in the launch options (so basically unless you have manually enabled ACO, it's not enabled by default. If you've got it enabled elsewhere, you can useRADV_PERFTEST=llvm`.

@Voxed, are you running the Steam version or DRM-free version? If not the Steam version, has anyone actually gotten the Steam version to work yet?

The DRM free version, you need the tkg patch to get it to work.

[ReaperOfSouls1909]

i will compile wine-tkg with that patch and upload the install file for arch

[liberodark]

precompiled version for arch : https://drive.google.com/open?id=1Gvvq5rxvSZmeLOaZZeGcm95FBT9mtOrq

[gardotd426]

So then DRM is an issue for this game, if it's impossible to run it without the DRM-free version. Or has anyone with the Steam version actually tried any of this?

[liberodark]

no just need to wait for drm when the pr is merge is ok

[PraetorianSC4]

@gardotd426: unknown at this time. I don't think anyone has gotten far enough yet with the drm version of the game.

[ashkitten]

i'm still working on getting the incredibly janky proton build process to work so i can build with patches from that pr

[liberodark]

but bethesda launcher is other probable issue
Probably just rename files ?

[gardotd426]

TKG's proton build uses the same patches as wine-tkg, so all you'd have to do is build proton-tkg with the patched wine-tkg.

[jjbarr]

@gardotd426 The issue is that at present the workaround involves hotpatching the executable because of a deficiency in Wine.

There's no reason we know of the DRM build won't work once that gets fixed.

[kisak-valve]

Hello @gardotd426, Denuvo is anti-tamper software, so it's not surprising that sed'ing the executable to lie about vulkan extensions would make it upset.

[werman]

I'm using drm-free version. amdvlk hangs for me every 10 minutes so I use amdgpu-pro

1) I've compiled vulkan-icd-loader 1.2.135 with https://gist.github.com/werman/af271c89410b942e6d50963ccf0f34f1 PKGBUILD (you can find compiled version above in thread, I think)
2) Radeon* Install amdgpu-pro vulkan, PKGBUILD https://gist.github.com/werman/696063d328fb9a49ed5ca609df6dff50, do makepkg and then do sudo pacman -U vulkan-amdgpu-pro-19.50_967956-1-x86_64.pkg.tar amdgpu-pro-core-meta-19.50_967956-1-any.pkg.tar amdgpu-core-meta-19.50_967956-1-any.pkg.tar
3) You need Proton 5.0 + two patch wine libs, https://cdn.discordapp.com/attachments/542099730751160338/690574741819621386/frog.7z (taken from dxvk discord, and compiled by doitsujin) - place both .so into Proton 5.0/dist/lib64/wine/

or use patched wine from above

4) For amdgpu-pro add VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json
5) Add +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 to launch options
it can look like VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json %command% +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
6) There may be issues with alt-tab (or whatever I have in i3) so you may want to enable virtual desktop in wine prefix
7) Enjoy

It's a bit hectic and people already posted guides above, but maybe this will help someone. At least Ithis worked for me.

[PraetorianSC4]

Now we just need to take @werman's list and convert for nvidia card holders, apply it to the steam version of the game, and hope for the best.

[wundrweapon]

@werman my distro doesn't have a build for the proprietariat's drivers. I haven't tested anything yet, but if amdvlk is so bad, then maybe the Mesa Radeon Vulkan driver would be better suited? Really I'm just throwing things at the wall

@ashkitten best of luck with the Proton build; I'm really hoping to see the game run out of the Steam client on day-1 :crossed_fingers:

[werman]

@wundrweapon I wasn't able to launch game with Mesa, but I didn't really tried

[gardotd426]

@jjbarr @kisak-valve I was under the impression that the patches for wine being mentioned (that are required to get the game to run) ARE what's in the PR, and what we're waiting on to be implemented in Wine. So shouldn't the Steam version just work with a patched Proton?

[liberodark]

But need vulkan-headers 1.2.135 too @ReaperOfSouls1909 you have this in pre compiled ?

[monban]

@PraetorianSC4 if I'm understanding correctly, @werman's instructions still involve using an executable of questionable legality, so if that's truly required then I doubt we'll see this fix making its way into the Steam Play defaults any time soon.

[kisak-valve]

Hello @gardotd426, if you dig back into the discussion, there was talk of another variant similar to PR 85 which applies cleanly to wine git master, but does not cover everything in that pull request.

[Voxed]

@PraetorianSC4 if I'm understanding correctly, @werman's instructions still involve using an executable of questionable legality, so if that's truly required then I doubt we'll see this fix making its way into the Steam Play defaults any time soon.

AFAIK the DRM-free version is only being used as to circumvent running through steam. The DRM version might still work with proton-tkg.

[liberodark]

OK HAVE FOUND BETTER SOLUTION :D

[mahmutpek]

Someone make a noob-proof guide/video? Some users (like me) even forget how coding works..
Also can this work on arch or gentoo linux?
Thx!

[wundrweapon]

@mahmutpek seems like all the testing in this thread so far has been done on Arch. Personally I'm just hoping that it all works smoothly on Void (now that I've updated Vulkan on their repos)

[ashkitten]

Someone make a noob-proof guide/video? Some users (like me) even forget how coding works..
Also can this work on arch or gentoo linux?
Thx!

the solutions given so far are not "noob-proof" at all. you should wait for a better solution if you lack the understanding required to use the ones given so far.

[Berinth]

@mahmutpek

You'll have to wait a bit. I've been watching this thread since it was opened a whole ~20 hrs ago, and they are still figuring it out

[gardotd426]

@kisak-valve, that makes much more sense, thank you for the clarification.

[mahmutpek]

@wundrweapon Yeah seems like I will try arch too but hope all of them will work.
@ashkitten True, I'm in the wrong league.
Thanks for all answers, also the new ones.

[liberodark]

im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing

[MacroHard-sys]

im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing

what would someone do with that on debian/ubuntu?

[ashkitten]

looks like https://github.com/ValveSoftware/Proton/blob/proton_5.0/vagrant-user-setup.sh#L7 failed because fetching http://repo.steampowered.com/steamrt/pool/main/libx/libxcb/libxcb-xinerama0-dev_1.11.1-1ubuntu1+steamos1+srt2_i386.deb timed out, unfortunately. it's a real pain to get this environment set up, because repo.steampowered.com is very slow.

edit: retried and it did not fail to fetch this time... let's see if the whole docker container will build now

[Voxed]

im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing

What patch did you use?

[liberodark]

is just build of wine precompiled.
For me not problem to run that on ubuntu or debian if you have same lib version for icd

[Voxed]

Yes but what did you do to get it to compile with VK_EXT_full_screen_exclusive support?

[CatalinPuscoci]

im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing

Do I just cp -r / it?

[liberodark]

Yeah use this version make a backup of your proton version.

[MacroHard-sys]

Yeah use this version make a backup of your proton version.

how do we get steam to use it and where do we put it?

[liberodark]

For run quickly the game and for drm-free or steam version @Kron4ek :

+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

[ashkitten]

finally got the vagrant box working to be able to try and build proton... getting some nasty errors, i think the patch might not be working properly. will try again in a bit.

[liberodark]

Ok this is a mini tutorial

tar -xvf winev2.tar.gz

mv ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist_back

mv wine ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist

run your game

[Voxed]

finally got the vagrant box working to be able to try and build proton... getting some nasty errors, i think the patch might not be working properly. will try again in a bit.

With proton-tkg?

[wundrweapon]

@liberodark tried what you posted, ran the Denuvo-infected version from Steam. No dice. Is there something I'm forgetting? I replaced the Proton dist with your latest wine build and ran with the specified options

[annmuor]

So I getting after doing all the stuff, with latest nvidia drivers & vulkan from Arch repos:
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.

Any ideas?

[Kron4ek]

@annmuor vulkan-icd-loader from the Arch repos is not new enough, 1.2.135 version is required.

[liberodark]

yeah you need : 1.2.135

[annmuor]

@Kron4ek @liberodark yep I know but ...

pacman -Ql vulkan-icd-loader
vulkan-icd-loader /usr/
vulkan-icd-loader /usr/lib/
vulkan-icd-loader /usr/lib/libvulkan.so
vulkan-icd-loader /usr/lib/libvulkan.so.1
vulkan-icd-loader /usr/lib/libvulkan.so.1.2.135
vulkan-icd-loader /usr/lib/pkgconfig/
vulkan-icd-loader /usr/lib/pkgconfig/vulkan.pc
vulkan-icd-loader /usr/share/
vulkan-icd-loader /usr/share/licenses/
vulkan-icd-loader /usr/share/licenses/vulkan-icd-loader/
vulkan-icd-loader /usr/share/licenses/vulkan-icd-loader/LICENSE.txt

[Joshua-Ashton]

You'll also need a version of Proton with my VK_KHR_get_surface_capabilities2 + VK_EXT_full_screen_exclusive patches.

[CatalinPuscoci]

You'll also need a version of Proton with my VK_KHR_get_surface_capabilities2 + VK_EXT_full_screen_exclusive patches.

seems like that is what's missing for me as well(FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required - I see that in the logs), but I did get the prebuilt wine liberodark put earlier in the thread

PS: I did get the new vulkan-icd-loader and headers too, and I'm using a GTX 1060 if that's useful info

[Kron4ek]

@Joshua-Ashton I can't manage to compile Proton with your PR for some reason, there are winevulkan related errors during compilation. Is this some problem on my end or the problem is in the PR?

I even tried to clone and compile your proton-wine VK_KHR_get_surface_capabilities2 branch, still get the same errors.

[liberodark]

The version that I sent works perfectly with doom eternal now it is true that it is especially those who arch linux or manjaro who will be able to play it most easily.
By the time the pull request is merge. My solution is only a workaround

[Joshua-Ashton]

@Kron4ek You'll need to run make_vulkan in dlls/winevulkan before building

[PraetorianSC4]

make[2]: *** [loader/CMakeFiles/asm_offset.dir/build.make:63: loader/CMakeFiles/asm_offset.dir/asm_offset.c.o] Error 1 make[2]: Leaving directory '/home/user/Downloads/vulkan-icd/src/Vulkan-Loader-1.2.135/build' make[1]: *** [CMakeFiles/Makefile2:201: loader/CMakeFiles/asm_offset.dir/all] Error 2 make[1]: Leaving directory '/home/user/Downloads/vulkan-icd/src/Vulkan-Loader-1.2.135/build' make: *** [Makefile:141: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Oof. Thoughts?

Does makepkg PKGBUILD go out and get vulkan-icd-loader-1.2.135 or is that something you have to procure first in order to build the package that pacman would then use to install?

[CatalinPuscoci]

make[2]: *** [loader/CMakeFiles/asm_offset.dir/build.make:63: loader/CMakeFiles/asm_offset.dir/asm_offset.c.o] Error 1 make[2]: Leaving directory '/home/user/Downloads/vulkan-icd/src/Vulkan-Loader-1.2.135/build' make[1]: *** [CMakeFiles/Makefile2:201: loader/CMakeFiles/asm_offset.dir/all] Error 2 make[1]: Leaving directory '/home/user/Downloads/vulkan-icd/src/Vulkan-Loader-1.2.135/build' make: *** [Makefile:141: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

Oof. Thoughts?

Does makepkg PKGBUILD go out and get vulkan-icd-loader-1.2.135 or is that something you have to procure first in order to build the package that pacman would then use to install?

make sure you get the headers first(they're in this thread), otherwise it'll fail

[liberodark]

no need headers run the game in headers 1.2.332
no have found the 1.2.335 :(

[Kron4ek]

@Joshua-Ashton Thank you, i didn't know that this is required.

[dylanmc1975]

yeah you need : 1.2.135

Nice job .. I've placed the patched wine ... but in my gentoo box no vulkan loader 1.2.35 yet .. :(

[kisak-valve]

Friendly reminder that the Steam runtime (not the Steam Linux Runtime compatibility tool) in the current Steam client beta provides the 1.2.135 vulkan loader.

[liberodark]

ah so sorry :( @dylanmc1975

[xDShot]

How do I make make_vulkan happen in @Tk-Glitch proton-tkg build?

[dylanmc1975]

@liberodark Unfortunatly gentoo is not too reactive, I have to hope in valve I think

[grinceur]

You rocks guys Thank You !!

[MuchiMuchiPink]

I have the same issues as @annmuor I build the required vulkan-icd-loader and tried @liberodark wine bottle and still get the crashes..

[PraetorianSC4]

So tutorial on how to get up to 1.2.135 in arch (Manjaro):

cd ~/Downloads
mkdir -p vulkan/icd vulkan/headers

wget -O ./vulkan/icd/PKGBUILD "https://gist.githubusercontent.com/oscarcp/4c4fb71fa380015b722172f308d406b1/raw/5d87d9e302fdc1f435457fcdd0dfc7ecaa5bcfa2/gistfile1.txt"

wget -O./vulkan/headers/PKGBUILD "https://gist.githubusercontent.com/oscarcp/9b54ea7f6bd4eb4144bd4e5e980f2c4c/raw/a33607a4f0966e1fed00440c9f8f99a4b7295402/gistfile1.txt"

cd vulkan/headers
makepkg --syncdeps
pacman -U vulkan-headers-1:1.2.135-1-any.pkg.tar.xz -y

cd ~/Downloads/vulkan/icd
makepkg --syncdeps
pacman -U vulkan-icd-loader-1.2.135-1-x86_64.pkg.tar.xz -y

Next:
milkyway vulkan-icd]$ pacman -Ql vulkan-icd-loader
vulkan-icd-loader /usr/
vulkan-icd-loader /usr/lib/
vulkan-icd-loader /usr/lib/libvulkan.so
vulkan-icd-loader /usr/lib/libvulkan.so.1
vulkan-icd-loader /usr/lib/libvulkan.so.1.2.135
vulkan-icd-loader /usr/lib/pkgconfig/
vulkan-icd-loader /usr/lib/pkgconfig/vulkan.pc
vulkan-icd-loader /usr/share/
vulkan-icd-loader /usr/share/licenses/
vulkan-icd-loader /usr/share/licenses/vulkan-icd-loader/
vulkan-icd-loader /usr/share/licenses/vulkan-icd-loader/LICENSE.txt

And then follow this (courtesy of @liberodark):

cd ~/Downloads
mkdir dootwine
mv winev2.tar.gz dootwine/.
cd dootwine

tar -xvf winev2.tar.gz

mv ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist_back

mv wine ~/.local/share/Steam/steamapps/common/Proton\ 5.0/dist

Assuming I didn't miss anything, THE ONLY THING THEY SHOULD FEAR IS YOU...

Edit:

Still crashes for the Steam version of the game :-1:

HALP

[pastapojken]

same as @MuchiMuchiPink , @liberodark I tried your wine build but for me, at least, it crashes. Log is here.
I compiled vulkan-icd-loader to 1.2.135 by modifying the PKGBUILD. Running Arch 5.5.10 with an R9 290 and latest from the mesagit repo

[liberodark]

if you want the icd : @pastapojken
vulkan-icd-loader-1.2.135-1-x86_64.pkg.zip

Have retry with 1.2.332 is crash need to reboot after install

[wundrweapon]

Still haven't gotten anywhere since this

[Berinth]

Still haven't gotten anywhere since this

What distro are you running? these guys here are running it on an Arch-based distro. I'm on Pop!_os (ubuntu-based) and it doesn't work for me either.

[UVCRocketRunner]

@wundrweapon I believe you need to get the DRM-free executable involved, as mentioned above. Granted, I don't know if liberodark et al are using the DRM-free version.

EDIT: I'd like to attempt this myself, but maybe with a simpler dummy-proof guide, though I am running Fedora.

[MuchiMuchiPink]

Update here i used @liberodark wine as a new runner in Lutris and now it works. Thanks everyone.

[AllKind]

Hi guys,

can't follow half of what you do/say, but I used the wine version of liberodark and (with and without) the launch options it crashes.
I'm on Linux Mint 19.3 (ubuntu 18.04 based) with kernel 5.5.9 and nvidia 440.64 drivers - trying it from steam (purchased it there).
The 'systems' vulkan is too old, but as mentioned above they'd come with steam-beta, right?
Did I miss something? Should I install the latest beta driver from here: https://developer.nvidia.com/vulkan-driver ?

Thanks you h4ck3rz :)

[liberodark]

I do what I can, maybe I can't help everyone with my solution.
If necessary I will give you my discord id to share a screen with me and try to help you as much as I can.
liberodark#0928

[wundrweapon]

What distro are you running?

Void Linux

I believe you need to get the DRM-free executable involved

Maybe I do… So be it

I will give you my discord id

Thank you; sent a request, not sure if/when I'll need help

[rabidlassie]

@wundrweapon I've done the same, replaced Proton 5.0/dist with @liberodark 's Wine, however after I run the game Steam automatically overwrote everything so it didn't work with his Wine modifications. You can check it yourself as well.

[Tbird761]

Does anyone know how to run a Steam game using the system's wine instead of Proton?

[Kron4ek]

Actually, there is no need to replace the whole Proton's directory, it just necessary to replace winevulkan.dll.so and winex11.dll.so inside the "steamapps/common/Proton 5.0/dist/lib64/wine" directory, and after that Proton will be capable to run the game (as being said before by @werman).

Vulkan-Loader 1.2.135 is required, so make sure you have it installed.

And i didn't see any post that mention running the Denuvo version successfully, so DRM-Free exe is probably still required.

[rabidlassie]

@wundrweapon after running a game with Proton, Steam extracts proton_dist.tar to dist/ folder. I changed that proton_dist.tar file to be same as @liberodark 's Wine and tried it but idTechLauncher.exe immediately crashed (no system tray icon either), even tried replacing idTechLauncher.exe with DOOMEternalx64vk.exe but it didn't work either. Probably it doesn't work with DRM version.

[VincentGuinaudeau]

After manually patching Proton 5.0 and upgrading the vulkan icd loader, can someone detail the command to run the game ?

If I use ./[...]/Proton\ 5.0/dist/bin/wine64 [path to the game.exe] directly the game run but I have terrible audio (no FAudio I presume ??)

If I use ./[...]/Proton\ 5.0/proton run [path to the game.exe] I have the FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.

I'm on manjaro, using the drm free version.

[grand248]

Hi guys, i'm a little lost from all the posts, is everyone getting this running in Steam? Or via Wine or Lutris or all the above?
Is it running with standard Steam version or is required to use the DRM-Free exe?
If the DRM-Free exe is required, where can we get it from?
I'm sorry if this has been previously posted but how does one update Vulkan-Loader 1.2.135 in Manjaro?
I have now switched Steam to Steam beta, does this mean I am automatically running Vulkan-Loader 1.2.135? Or do I need to select other options?
Thanks guys, awesome you got it running!

[PraetorianSC4]

@grand248: Variable level of success with drm-free exec, will have to get the Bethesda.net version of the game (possible that it's been patched out already). Steam version of the game is borked.

[Voxed]

After finally getting the DRM-version not to crash I got a nice greeting from Denuvo.

Refund it is.

[PraetorianSC4]

@Voxed what'd you do to get that far?

[pKrysenko]

@PraetorianSC4 I have the same. I didnt change anything, just upgrade beta steam. And get this shit from Denuvo

[Voxed]

@PraetorianSC4 Put liberodark's wine patch in the "Proton\ 5.0/dist" directory, overwriting the already existing files, I think you might need the version file already in there (not sure). And updating icd-vulkan-loader.

Also you need to disable ACO if you got that.

My launch command is:
RADV_PERFTEST=llvm PROTON_LOG=1 %command% +in_terminal 1

[AllKind]

@Voxed - I'm getting that error on my Windows 10 (dual boot). You have any idea what is going on? Why that error? I could play it after game launch in Windows. After a reboot I got that message.

[PraetorianSC4]

@Voxed: radeon gpu yeah? Unlikely to work for me, nvidia card over here.

I've already done all of the following:

• https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601940820
• https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601932287

No luck thus far. Majorly disappointing.

[pastapojken]

Yeah, personally no matter what I do or if I use DRM/no DRM, it just crashes. Hopefully someone has it actually figured it out when I wake up ¯\_(ツ)_/¯

[Voxed]

@AllKind Denuvo doesnt want you to have fun, you could always try to get the drm free version.

[AllKind]

@Voxed , but It's a purchased version on Windows from steam???

[Voxed]

@AllKind this is the wrong place for this conversation. Either wait 24 hours or get a refund.

[mozo78]

The game runs but the performance is terrible:
https://i.imgur.com/wK7Xr3H.png
Only in the begining of the level I can get 60 FPS. If I walk some steps and I get 18...

[liberodark]

yes @mozo78 is not pretty good and im on nvidia
Better without hdr and vsync

[mozo78]

Yes, now it's 24 :D

[CatalinPuscoci]

im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing

This one did it for me alongside the two pkgbuilds for the 1.3.5 vulkan-icd-loader and header, many thanks @liberodark

To mention that I did put the patched wine in the dist folder of proton 5.0

[wundrweapon]

Tried with a certain alternative executable. Assuming that exe isn't busted, It works somehow less now. I'm gonna sit back for a while until everything looks good, or until my 2-week refund period is about to expire :upside_down_face:

[liberodark]

To launch and play the game correctly it would take two things an improvement of dxvk and proton to correctly take care of the game also the game this launches in vulkan it is bad.

[Voxed]

To launch and play the game correctly it would take two things an improvement of dxvk and proton to correctly take care of the game also the game this launches in vulkan it is bad.

DXVK is not used for doom. It natively runs in vulkan.

[jjbarr]

Yeah, the improvement that is required is actually to Proton/Wine's libvulkan shim.

[annmuor]

Finally I got it running, hell yeah. Have an issue with alt-tabing but who cares.
So, overall, a quick instruction for steam users.

1. Proton 5.0 works great with patched DLLs, you do not need to sed exe anymore.
2. wine with patches provided here didn't work for me ( nvidia 1660, arch ) but proton does.
3. Here's a link to proton (5.0.1+libs, just unpack) I used: https://drive.google.com/open?id=1H4Dljhp5L7d8lI7YVqid8MTkaMM_kOTF
4. Here's a link to my run script: https://gist.github.com/annmuor/88009be669db8c53a31b99e6c5835a07
5. You do need latest vulkan and it's the most tricky part here.

Thanks all who made it working!

[liberodark]

Yeah but doom eternal with Vulkan is pretty bad perf on wine without dxvk too
dont have test without esync...

[dxgldotorg]

@AllKind this is the wrong place for this conversation. Either wait 24 hours or get a refund.

I guess the constant hacking of Proton trying to get it to work resulted in the executable seeing over 5 different versions of the libraries. Try to maintain the same kernel32, ntdll, etc. binaries as you poke around.

[Joshua-Ashton]

Yeah but doom eternal with Vulkan is pretty bad perf on wine without dxvk too

DXVK is unrelated.

[liberodark]

Yeah but doom eternal with Vulkan is pretty bad perf on wine without dxvk too

DXVK is unrelated.

yes that's what i say ! but it's crazy to have such a really bad performance ...

[APoniatowski]

doom eternal released an update... still the same though. don't know how the patch would affect all the work done so far

[AllKind]

@dxgldotorg I played it on Windows 1 hour after launch. Just had the windows update updating the AMD chipset drivers after. Next day after a reboot I was "locked out". Hard to imagine the testing in linux (dual boot) affected the Windows version... However "<Removed by moderator>" just popped up. If the problem continues, I'd might have a way out :)
Sorry for offtopic talk...

[makusu2]

We're all in the same boat of bad performance, correct? No one's has any better luck?

[liberodark]

need to compare AMD and NVIDIA no idea for me is on 60 and 25 fps

[Voxed]

We're all in the same boat of bad performance, correct? No one's has any better luck?

I was running the DRM-free version with solid 100fps using AMD hardware.

[liberodark]

you have aco ?

[Voxed]

Had to disable aco for vulkan 1.2.135 to be used.

[ashkitten]

well, this might be better than before, i think? after pressing play it shows the id logo in a small window and exits like before, though.

log (55MB)

[ashkitten]

is there any way to see the terminal output from the game when launching from steam?

[liberodark]

for need to wait update from game / vulkan & proton / wine

[jrgp]

For me, the game crashes with this, when trying to open with Steam play and when using this script from above: https://gist.github.com/annmuor/88009be669db8c53a31b99e6c5835a07

I'm 3950X / 1080ti. Has anyone else seen this?

[ryester27]

Does anyone know how to run a Steam game using the system's wine instead of Proton?

I'm interested in what the quickest way is, as well. Want to also start testing the wine repo over in the mfplat ticket

[RibalGZ]

well, this might be better than before, i think? after pressing play it shows the id logo in a small window and exits like before, though.

Same here, both DRM and DRM-free

[UVCRocketRunner]

@annmuor I think I'm going to attempt this fix. Do I need to make a separate Proton folder for the one you provided, or just drop it into 5.0?

[wundrweapon]

Finally I got it running, hell yeah. Have an issue with alt-tabing but who cares.
So, overall, a quick instruction for steam users.

1. Proton 5.0 works great with patched DLLs, you do not need to sed exe anymore.

2. wine with patches provided here didn't work for me ( nvidia 1660, arch ) but proton does.

3. Here's a link to proton (5.0.1+libs, just unpack) I used: https://drive.google.com/open?id=1H4Dljhp5L7d8lI7YVqid8MTkaMM_kOTF

4. Here's a link to my run script: https://gist.github.com/annmuor/88009be669db8c53a31b99e6c5835a07

5. You do need latest vulkan and it's the most tricky part here.

Thanks all who made it working!

Confirmed on Void Linux! Only works on DRM-free exe, though… :confused:

[kazetsukaimiko]

For me, the game crashes with this, when trying to open with Steam play and when using this script from above: https://gist.github.com/annmuor/88009be669db8c53a31b99e6c5835a07

This happens if you select Proton 4.2-9 or below. (Unable to initialize SteamAPI)

[ashkitten]

anyone who has it working, can you give your system info please?

i have not been able to get it working, with:

• OS: NixOS (nixos-unstable)
• GPU: rx 5700
• Driver: Mesa 19.3.3 (LLVM 9.0.1)
• Kernel: 5.4.25

[grand248]

Hi guys,
Can someone please explain how to get the latest vulkan in Manjaro.
Thank you in advance.

[kazetsukaimiko]

Can someone please explain how to get the latest vulkan in Manjaro.

https://www.archlinux.org/packages/extra/x86_64/vulkan-icd-loader/
Has been flagged as out of date for over a month. Is anyone familiar with the Arch release process that can escalate via the proper channels?

[dylandn]

@liberodark Unfortunatly gentoo is not too reactive, I have to hope in valve I think

We could try emerging the latest from git.

ps We both born in '75, named dylan, run gentoo, and play doom? omg

[grand248]

@annmuor
I have extracted the provided proton to ~/.local/share/Steam/steamapps/common/Proton 5.0/
When I run that script I get the below error:

bash ~/Documents/doom.sh
/home/grand/Documents/doom.sh: line 6: ~/.local/share/Steam/steamapps/common/Proton 5.0/dist/bin/wine: No such file or directory

I have confirmed that the file and directory does exist.

Thank you

[wundrweapon]

@ashkitten here you go
@grand248 use the PKGBUILDs from Tk-Glitch, though as someone who has never messed with Arch package making I can't explain the process

[mozo78]

Here's mine:
https://pastebin.com/Kqi9jasB
https://i.imgur.com/aaZtDmD.png

[rabidlassie]

Anyone with Arch-based distro can use this repo to update vulkan-headers and vulkan-icd-loader to latest 1.2.135: https://github.com/Tk-Glitch/PKGBUILDS

@ashkitten I've got it working only to be greeted by DRM screen as @Voxed posted. I've installed newest available vulkan-headers and vulkan-icd-loader, then got it working using Proton 5.4-GE-1 which can be found from here: https://github.com/GloriousEggroll/proton-ge-custom/releases

Here is my system info: https://gist.github.com/rabidlassie/7c3ab9a232a152aa9e7a684aec86f1ee

Also the DRM screenshot (it opens from a browser):

[ZacJoffe]

@grand248 I had the same issue with the script. See my solution here. Note I still am unable to get the game running on my system but I don't have the latest vulkan-headers.

[wundrweapon]

I didn't even get that image when I ran on the Denubloat exe, it just crashed

[ashkitten]

@rabidlassie thanks for pointing out that Proton-5.4-GE-1 works, i got much farther with that than the build i compiled myself. it doesn't actually open in browser for me, just gives me a popup with a link to the support page with that on it (https://support.codefusion.technology/de_d90127jd781/?e=88500006&l=english)

[rabidlassie]

@ashkitten yeah that link opens up the page I've posted

@wundrweapon probably related to vulkan versions, can you post your log?

[wundrweapon]

@rabidlassie which log is that and where would I find it

[rabidlassie]

@wundrweapon there you go: https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601503268

[wundrweapon]

Oh, it doesn't even launch to make a log, it just says it can't initialize the Steam API; tells me I need to make sure the right account is connected and whatnot. I wonder why?

[rabidlassie]

@wundrweapon did you try to launch the game with Steam client or command-line? If you tried command-line you can go into the Steam client, right-click DOOM Eternal -> Properties -> Set Launch Options -> write down this:
PROTON_LOG=1 %command%

[ashkitten]

so the current status is it works, but denuvo always trips?

[rabidlassie]

I might try with @annmuor 's Proton dist since he got it working. Might be something going wrong with Proton 5.4-GE-1. I am not sure though. Downloading the game again, just in case.

[rabidlassie]

Also I had an update, Steam's Proton version got bumped up to 5.0-5. Still throws DRM error though :(

[ashkitten]

Also I had an update, Steam's Proton version got bumped up to 5.0-5. Still throws DRM error though :(

there's no release on github... did they include the relevant fixes in that?

[wundrweapon]

can you post your log?

Yikes, over 500k lines o_O
A direct search for vulkan only results in some SOs successfully loading

[JeffCarpenter]

nbd if you use a pastebin

[kisak-valve]

Hello @rabidlassie, if Denuvo is already in the agitated state, it'll need a day to reset before evaluating another Proton build.

Hello @wundrweapon, Proton logs tend to compress well. If Github doesn't like the size of the log, consider throwing it in an archive.

[UVCRocketRunner]

Since Steam now has Proton 5.0.5, I'll ask again: should I add @annmuor 's Proton dist to the 5.0 folder, or make a separate one?

[wundrweapon]

consider throwing it in an archive.

Why didn't I think of that? Here's the archive
log.zip

[Berinth]

Here's my log now with Proton 5.0.5. Much smaller than that of @wundrweapon
steam-782330.log

[UVCRocketRunner]

Oh, yes, I suppose I might as well throw up the log with Proton 5.0.5 for completion's sake.
steam-782330.log

[Weilbyte]

@rabidlassie do you have the DRM-free exe to try it on?
Anywho I tried @annmuor 's workaround and the game's screen just flickers. Arch (5.5.8-arch1-1), 1050Ti, latest vulkan. Cant throw in a log atm.

[Vladimir-A]

System.
Proton: 5.0-5.
vulkan-icd-loader and vuikan-headers - 1.2.135.
I tried launch both DRM and DRM-free. After "GPU Vendor Warning" the game crashed, and now I get a link to https://support.codefusion.technology...
Proton-5.4-GE-1 don't work without specific manipulations.

[ryester27]

With 5.0-5 & DRM version, I see the "AMD doesn't support HDR yet" error now, but silently crashes right after. Using steam-native, vulkan-icd-loader 1.2.135, and aco disabled. Haven't touched anything else.

steam-782330.zip

[grand248]

5.0-5:
Fix crash in some games introduced in Proton 5.0-4.
Fix networking error in Granblue Fantasy: Versus.
Support for latest OpenVR SDKs.
Add support for new Vulkan extensions used by some recent titles.

[UVCRocketRunner]

Worth noting, there seems to have been an update to the Nvidia driver yesterday. I was cruising the web trying to figure out if I need to install/update vulkan-icd-loader and such, and saw this webpage:

https://www.archlinux.org/packages/?name=nvidia

Checking Flatpak on my Fedora system, there is a new package available, but it is still 440.64.

UPDATE: Yeah, still doesn't work, but it was probably worth a shot.

[rabidlassie]

@kisak-valve alright, thank you

@Weilbyte I do actually, but I haven't tried it with Proton because my Steam account is linked to my Bethesda account, it will probably try to automatically log-in once I opened the game. I don't want to take that risk.

[dylanmc1975]

@liberodark Unfortunatly gentoo is not too reactive, I have to hope in valve I think

We could try emerging the latest from git.

ps We both born in '75, named dylan, run gentoo, and play doom? omg

LOL

dylan is a nickname my name is Luca but the other things are real eheh

Tell me if u get lucky with git, tomorrow maybe I will try

[rabidlassie]

@Vladimir-A you have nofsync on, perhaps that is the issue?

@wundrweapon @ryester27 you both have stack overflow, not sure what causes this.

[Vladimir-A]

@rabidlassie I tried launch with fsync and without fsync, for example From Software games don't works with fsync. Same logs.

[grand248]

I don't understand how the Proton team didn't pre-test such a big title game?

[Berinth]

I don't understand how the Proton team didn't pre-test such a big title game?

Probably because they don't have a playable copy until release day, I'm guessing. Bethesda certainly have no incentive to help out such a small portion of the user base who run an OS that they don't even support.

[Voxed]

Here's to hoping they will drop Denuvo soon like with Rage 2. Especially since the game came cracked out of the box.

[smclenithan]

Updated log with Proton 5.0-5
steam-782330.log

GPU: 8 GB GTX 1070
Driver: 440.44
OS: Pop!_OS 19.10
Proton version: 5.0-5

[grand248]

I don't understand how the Proton team didn't pre-test such a big title game?

Probably because they don't have a playable copy until release day, I'm guessing. Bethesda certainly have no incentive to help out such a small portion of the user base who run an OS that they don't even support.

Proton is Steam though right? For sure Bethesda would provide Steam the release copy prior to release date.

[ryester27]

I don't understand how the Proton team didn't pre-test such a big title game?

Probably because they don't have a playable copy until release day, I'm guessing. Bethesda certainly have no incentive to help out such a small portion of the user base who run an OS that they don't even support.

Proton is Steam though right? For sure Bethesda would provide Steam the release copy prior to release date.

woulda coulda shoulda. This is still an open-source project

[Berinth]

I don't understand how the Proton team didn't pre-test such a big title game?

Probably because they don't have a playable copy until release day, I'm guessing. Bethesda certainly have no incentive to help out such a small portion of the user base who run an OS that they don't even support.

Proton is Steam though right? For sure Bethesda would provide Steam the release copy prior to release date.

Valve aren't the press, and they don't do any QA/compliance testing for software on their platform. I don't see why Bethesda would need to unless they also distribute review keys through Steam. But I'm literally just speculating at this point.

[folknor]

Please stop discussing nonsense in this ticket. This isn't a forum, it's a technical bug report ticket. Help solve the problem or shut up.

[wundrweapon]

Yeah, uh, we know

[mozo78]

Arch received vulkan-icd-loader 1.2.135-1 officially last night. There's no more need to compile it :)

[Yjnar]

Is the DRM-free .exe still needed with Proton 5.0-5 and vulkan-icd-loader 1.2.135-1 on Arch?

[gardotd426]

We won't know until later today, Denuvo blocks you for 24 hours if you try
too many configurations. So the people with the Steam version seem to be
waiting to get unblocked to try again, if I understand correctly

On Sat, Mar 21, 2020, 4:41 AM Yjnar [e-mail] wrote:

Is the DRM-free .exe still needed with Proton 5.0-5 and vulkan-icd-loader
1.2.135-1 on Arch?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602014658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y332CETCBZYP6XOOHZKTRIR4SFANCNFSM4LP25FOQ
.

[mozo78]

Yes, it's needed :)
@Kron4ek
The Proton builld on your GitHub page is still 5.0-4. The game crashes with it.

[Kron4ek]

@mozo78 Valve didn't update their github Proton repo yet, so i can't compile Proton 5.0-5.

The Proton builld on your GitHub page is still 5.0-4. The game crashes with it.

It works for me. I mean that i reuploaded my Proton 5.0-4 build, i compiled it with the required patches, so the Doom Eternal works on it.

[thebozzcl]

Has anybody here managed to compile Vulkan-Loader on Ubuntu? The latest version in apt is 1.1.126.0-2, so I assume that's one of the problems I need to solve. I thought I followed the instructions properly, but it doesn't seem Doom Eternal is recognizing them.

I noticed that some of the tests in Vulkan-Loader are failing for me, so that's at least part of the reason it's failing for me.

[mozo78]

@mozo78 Valve didn't update their github Proton repo yet, so i can't compile Proton 5.0-5.

The Proton builld on your GitHub page is still 5.0-4. The game crashes with it.

It works for me. I mean that i reuploaded my Proton 5.0-4 build, i compiled it with the required patches, so the Doom Eternal works on it.

I just tried the game and it crashed. With Winev2 it works :)
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view

[Kron4ek]

@mozo78 Don't know why it doesn't work for you, i just dowloaded it again from my github page directly (just to be sure in the file integrity) and the game works for me.

But i'm recompiling my Improved build right now, maybe it will work for you.

Also you can try these game arguments:

+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

[igo95862]

Arch Linux updated vulkan loader: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/vulkan-icd-loader&id=f04a0e735e553b1d749730865fe758f38ef6b966

Does that change anything?

[C0rn3j]

Am trying on Arch Linux, beta steam (tried both runtime and native), vulkan-icd-loader 1.2.135 and nvidia 440.64 on a GTX 1080 Ti, trying proton 5.0-5.

Trying to launch the Denuvo game doesn't even load into a black screen, it just stops executing. steam-782330.7z

Trying to launch the DRM-free EXE along with the original loader loads into a black screen then crashes. Someone in the piracy threads mentioned Bethesda removed the original folder and patched the files so they won't work with the exe, so that may be why.

From what I'm reading here I should at least be able to launch the DRM game into SOMETHING, but I get nothing, did I miss something?

[Yjnar]

Am trying on Arch Linux, beta steam (tried both runtime and native), vulkan-icd-loader 1.2.135 and nvidia 440.64 on a GTX 1080 Ti, trying proton 5.0-5.

Trying to launch the Denuvo game doesn't even load into a black screen, it just stops executing. steam-782330.7z

Trying to launch the DRM-free EXE along with the original loader loads into a black screen then crashes. Someone in the piracy threads mentioned Bethesda removed the original folder and patched the files so they won't work with the exe, so that may be why.

From what I'm reading here I should at least be able to launch the DRM game into SOMETHING, but I get nothing, did I miss something?

My system and setup is pretty much identical and I get identical results.

[wiltaylor]

@C0rn3j If you have a copy of the exe it still works. I was blocked by Denovo in windows because I tried a heap of configs with wine but switching the exe out with the DRM free one worked fine.

[C0rn3j]

@wiltaylor
Can you confirm that I've got the correct files?
I didn't manage to save them before Bethesda removed them, so I nicked them off the internet.

[0] % sha256sum idTech* DOOM*      
3d7eae19cc71b64ad911fa46495085d67b7ef2afedba34f4b25b080da9b3bffb  idTechLauncher.exe
a35a9931f38baf0bf49bc017dd5fa5a24b988a17a35a91da19f33d0114bcadef  idTechLauncher.exe.drmfree
6858296bb6e65e95c51b71ec0f91ca7b94b48e65c15083d3fbed7c57a79dffcb  DOOMEternalx64vk.exe
65c1939ca88d613bb78d5bdf3d6804bc171fde708f4f0f0c11daf3a4ad492b40  DOOMEternalx64vk.exe.drmfree

[wiltaylor]

@C0rn3j yep same hashs I have for DOOMEternalx64vk.exe

I only have the DRM free idTechLauncher.exe on my windows system though. Files came down via steam like normal.

[Yjnar]

I have same hashes also @C0rn3j

[C0rn3j]

@wiltaylor Tried launching with just the EXE changed(kept the current launcher), no change, still crashes.

steam-782330.log

Tried a clean prefix for good measure(rm -rf ~/.local/share/Steam/steamapps/compatdata/782330/pfx), didn't help.

[mozo78]

+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

I tried it in a clean prefix and it's actually working. Sorry about that :)

[Kron4ek]

@mozo78 no problem :)

[McMarius11]

for me it also does not work,
nvidia 440.64 vulkan-icd-loader 1.2.135
steam-782330.log
starts and crashes

it would be awesome if someone could upload a working Proton build

[999eagle]

Okay I compiled Tk-Glitch's proton with the patch applied (https://github.com/Tk-Glitch/PKGBUILDS/commit/52d0e915a7c88acaf544ad1c9b7eb9fcc23645cb) and the unmodified Steam version of DOOM Eternal is running with this. Used launch options: +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

DOOM seems to run fine now with DRM!

EDIT: Here's my binary proton build: https://ufile.io/x58gs3ia
EDIT2: See below for step-by-step instructions to run DOOM Eternal.

[tuxayo]

@999eagle and anyone else who managed to make it work: ProtonDB reports are very welcome: https://www.protondb.com/app/782330

[999eagle]

@McMarius11 will do

@tuxayo yup, I'll add my report

[999eagle]

@McMarius11 uploaded and edited my comment with the binary.

[FTL-Space-Warp]

@999eagle Is it possible to have a fool-proof, step by step guide? Or should the inexperienced just wait for valve to solve the issue? Do I risk making a mess?

[tuxayo]

uploaded and edited my comment with the binary.

For some reason my ISP seems to block ufile.io but not uploadfiles.io... So full link here if that helps someone else: https://uploadfiles.io/x58gs3ia

[oscarcp]

@999eagle Is it possible to have a fool-proof, step by step guide? Or should the inexperienced just wait for valve to solve the issue? Do I risk making a mess?

I'm still in library hell in Arch ddue to the package database not upddating and some other dependenciees so my advice is: patience, it will come eventually, not too long now

[999eagle]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to ~/.steam/root/compatibilitytools.d/
2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)
3. Restart Steam
4. Add these launch options to DOOM Eternal in Steam: +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
5. Choose Proton-tkg 5.4.r10.g7c7868f4 as the Proton version to use for DOOM Eternal
6. Rip and Tear!

[tuxayo]

Hopefully we will get at least a beta build to not have to rely on distributing binaries to each other.

https://github.com/Tk-Glitch/PKGBUILDS/commit/52d0e915a7c88acaf544ad1c9b7eb9fcc23645cb#commitcomment-37957962

Reporting feedback in the above commit of succeeding running Doom Eternal should help to get confidence on the releasability of the patch.

[hansdampfinger666]

@999eagle Danke, küsse deine Augen!

[kdwinter]

Has anyone gotten it to run on an AMD gpu? If so, which mesa version was used? I keep running into FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required. despite using vulkan-icd-loader 1.2.135 and the latest mesa-git build.

[zaggynl]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to `~/.steam/root/compatibilitytools.d/`

2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)

3. Restart Steam

4. Add these launch options to DOOM Eternal in Steam: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1`

5. Choose `Proton-tkg 5.4.r10.g7c7868f4` as the Proton version to use for DOOM Eternal

6. Rip and Tear!

Don't have the compatibilitytools.d folder in ~/.steam/root/, created it, after Steam restart the tool showed up.

On attempt to run:

======================
Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/az/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+com_skipIntroVideo', '1', '+com_skipKeyPressOnLoadScreens', '1', '+com_skipSignInManager', '1']
Options: {'logcommandtoprefix', 'nonvapi', 'winedxgi', 'winetricks'}
======================
ERROR: ld.so: object '/home/az/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/az/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/az/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

[dylanmc1975]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to ~/.steam/root/compatibilitytools.d/
2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)
3. Restart Steam
4. Add these launch options to DOOM Eternal in Steam: +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
5. Choose Proton-tkg 5.4.r10.g7c7868f4 as the Proton version to use for DOOM Eternal
6. Rip and Tear!

A question, do you use vulkan-icd-loader 1.2.135 or a previus version?
Later I will try, but I'm not sure it may be work

[999eagle]

@zaggynl I have no idea why it still depends on that path... The file exists in ~/.steam/root/compatibilitytools.d/proton_tkg_5.4.r10.g7c7868f4/dist/lib/wine/ntdll.dll.so, not sure why the build doesn't use that one.

[999eagle]

@dylanmc1975 I'm using vulkan-icd-loader 1.2.135, but the Steam beta should include that

[Feluchs]

@kdwinter I use ubuntu 19.04 with steamvr mesa drivers and an rx580 and so far the game works.

[oscarcp]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to `~/.steam/root/compatibilitytools.d/`

2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)

3. Restart Steam

4. Add these launch options to DOOM Eternal in Steam: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1`

5. Choose `Proton-tkg 5.4.r10.g7c7868f4` as the Proton version to use for DOOM Eternal

6. Rip and Tear!

UPDATE WARNING: If you're using GNOME or GNOME-based desktop DO NOT ALT-TAB or leave the window. It will crash the game.

Confirmed to work, some notes on my side:

• I'm trapped in library hell and I broke my steam installation. I had to reinstall everything, fortunately the games were still there

Libraries I installed (you might not need them, I put them here for completion, steam runtime should have some of them already)

• lib32-nvidia-vulkan-utils 440.66.03-1
• nvidia-vulkan 440.66.03-1
• opencl-nvidia-vulkan 440.66.03-1
• nvidia-vulkan-utils 440.66.03-1
• lib32-opencl-nvidia-vulkan 440.66.03-1
• lib32-vulkan-icd-loader 1.2.135-1
• vulkan-icd-loader 1.2.135-1
• vulkan-headers 1:1.2.135-1
• vulkan-extra-layers 1.1.130+10614+a70d5d17e-1

[dylanmc1975]

@dylanmc1975 I'm using vulkan-icd-loader 1.2.135, but the Steam beta should include that

I hope, gentoo doesn't :)

[aleksbenmaza]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to `~/.steam/root/compatibilitytools.d/`

2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)

3. Restart Steam

4. Add these launch options to DOOM Eternal in Steam: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1`

5. Choose `Proton-tkg 5.4.r10.g7c7868f4` as the Proton version to use for DOOM Eternal

6. Rip and Tear!

Game still won't launch, even though I don't have the wine popup showing up anylonger.

How can I take a look to log file ?

[oscarcp]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to `~/.steam/root/compatibilitytools.d/`

2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)

3. Restart Steam

4. Add these launch options to DOOM Eternal in Steam: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1`

5. Choose `Proton-tkg 5.4.r10.g7c7868f4` as the Proton version to use for DOOM Eternal

6. Rip and Tear!

Game still won't launch, even though I don't have the wine popup showing up anylonger.

How can I take a look to log file ?

In the launch options of the game put PROTON_LOG=1 %command%

[zaggynl]

@FTL-Space-Warp

1. Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to `~/.steam/root/compatibilitytools.d/`

2. Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)

3. Restart Steam

4. Add these launch options to DOOM Eternal in Steam: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1`

5. Choose `Proton-tkg 5.4.r10.g7c7868f4` as the Proton version to use for DOOM Eternal

6. Rip and Tear!

Game still won't launch, even though I don't have the wine popup showing up anylonger.

How can I take a look to log file ?

Add PROTON_LOG=1 %command% to launch options in steam, start game, read ~/steam-782330.log

edit: forgot the %command% bit, sorry.

[jalabb]

@zaggynl @999eagle I have the same issue with the /home/sophie/ path.
The compatibilitytools folder is at ~/.steam/steam/compatibilitytools.d/ for me though.

[zaggynl]

Tried setting WINEPATH with WINEPATH=/home/az/.steam/root/compatibilitytools.d/proton_tkg_5.4.r10.g7c7868f4/dist/lib/wine in launch options but no joy.

[RumenBlack]

I am running Pop_os 19.10 and I haven't been able to install the vulkan-headers 1.2.135.
I was able to install 1.2.131 but that doesn't seem to be enough. Does anyone know how I could install the 1.2.135 on Pop_oS 19.10 (or Ubuntu 19.10?)

[McMarius11]

/home/mcmarius11/.steam/steam/compatibilitytools.d/proton_tkg_5.4.r10.g7c7868f4/

@zaggynl @999eagle I have the same issue with the /home/sophie/ path.
The compatibilitytools folder is at ~/.steam/steam/compatibilitytools.d/ for me though.

/home/USERNAME/.steam/steam/compatibilitytools.d/proton_tkg_5.4.r10.g7c7868f4/
it should look like this

for me the game still crashes,
do i need the latest nvidia 440.66.03?

[Kron4ek]

wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

This is because @999eagle compiled the TkG Proton build on Arch (am i right?), so GLIBC 2.31 is required for this build to work.

On the systems with older GLIBC you will get this kind of errors.

[dpanter]

I haven't been able to install the vulkan-headers 1.2.135.

Easiest way is to use the Steam beta client as it includes 1.2.135 now.

[Feluchs]

@RumenBlack Are you running the steam client beta? I am running the game with ubuntu mate 19.04 and the custom proton version just fine.

[Berinth]

@999eagle 's proton version crashes for me on Pop_os the same as it always did.
steam-782330.log

[OrdinaryMagician]

No luck with any of this either. Updated everything, built that patched proton, but still getting a crash. I can't get any logs out of this, I HAVE passed PROTON_LOG=1 to it, I even tried running steam itself with that, but I can't find the logs anywhere.

[oscarcp]

No luck with any of this either. Updated everything, built that patched proton, but still getting a crash. I can't get any logs out of this, I HAVE passed PROTON_LOG=1 to it, I even tried running steam itself with that, but I can't find the logs anywhere.

Arent they on your home folder as steamapp-{gameID}.log ?

[OrdinaryMagician]

My bad, turns out my globally set WINEDEBUG=-all envvar (for when I run other stuff with wine) prevents the logs from working.

steam-782330.log

[dpanter]

Following 999eagle's post, I get an error window popup:
_"Sorry, something went wrong, for solutions please visit "_
which points to a page at Bethesda saying
_"Currently your game purchase cannot be re-validated successfully, please wait 24 hours and try again."_

Smells like Denuvo... guess I'll try again tomorrow then.

[kdwinter]

@kdwinter I use ubuntu 19.04 with steamvr mesa drivers and an rx580 and so far the game works.

Still getting the FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required. error despite now also updating to the Steam client beta. Odd. Also using a RX580, fwiw.

[RumenBlack]

I haven't been able to install the vulkan-headers 1.2.135.

Easiest way is to use the Steam beta client as it includes 1.2.135 now.

I'm using the steam beta client right now but when I run vulkaninfo it still says I have 1.2.131

I've tried the custom wine/protons posted here, but I get a black screen that crashes out after a few seconds.

[Feluchs]

@kdwinter I use ubuntu 19.04 with steamvr mesa drivers and an rx580 and so far the game works.

Still getting the FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required. error despite now also updating to the Steam client beta. Odd. Also using a RX580, fwiw.

@kdwinter Have you tried to turn it off an on again? I rebooted my system in between.

[999eagle]

@Kron4ek yes, I've compiled this build on Arch, so GLIBC 2.31 is required. No idea why my build path is still in the binaries though.

[doitsujin]

@kdwinter RADV+ACO does not work currently, you'll have to use either LLVM (RADV_PERFTEST=llvm if your build has it enabled by default) or a different driver.

The proprietary Vulkan driver delivers by far the best performance in this game so you'll want to use that if you know how to install it, but do not fuck up your system by installing all the amdgpu-pro packages, it's not necessary.

[dpanter]

I'm using the steam beta client right now but when I run vulkaninfo it still says I have 1.2.131

Vulkaninfo uses the systemwide installation, Steam beta uses its own runtime. For example, my system:
~/.local/share/Steam/ubuntu12_32/steam-runtime/usr/lib/x86_64-linux-gnu/libvulkan.so.1.2.135

[kdwinter]

@kdwinter RADV+ACO does not work currently, you'll have to use either LLVM (RADV_PERFTEST=llvm if your build has it enabled by default) or a different driver.

The proprietary Vulkan driver delivers by far the best performance in this game so you'll want to use that if you know how to install it, but _do not_ fuck up your system by installing all the amdgpu-pro packages, it's not necessary.

That was indeed the problem, thanks!

[Yjnar]

Game works with major performance issues with the Nvidia 440.66.03 vulkan dev driver with a GTX 1080ti. Any ideas to improve performance? I'm on Arch and have the latest vulkan-icd-loader package installed (1.2.135-1)

[aleksbenmaza]

game's dedicated log does not seem to be created but steam's error.log contains this after failing to launch the game :
`
CreatingProcess"
Game update: AppID 782330 "", ProcID 30492, IP 0.0.0.0:0
Starting app 782330

Adding process 30492 for game ID 782330
GameAction [AppID 782330, ActionID 2] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 782330, ActionID 2] : LaunchApp changed task to Completed with ""
Adding process 30493 for game ID 782330
Adding process 30494 for game ID 782330
Adding process 30495 for game ID 782330
Adding process 30496 for game ID 782330
Game removed: AppID 782330 "", ProcID 30492
Uploaded AppInterfaceStats to Steam
Exiting app 782330
No cached sticky mapping in ActivateActionSet.
`

[FTL-Space-Warp]

I followed 999eagle's instructions (I am on arch) and the steam version of the game works, but runs very poorly (15-25 fps).

[oscarcp]

Game works with major performance issues with the Nvidia 440.66.03 vulkan dev driver with a GTX 1080ti. Any ideas to improve performance? I'm on Arch and have the latest vulkan-icd-loader package installed (1.2.135-1)

It definitely has perfomance issuees, but take in mind that we're patching the hell out of it. I have arch and a 2060 and I can barely have it on high (let's remember that there are 4 higher settings above that) at 30-40 fps

[user1-github]

@kdwinter RADV+ACO does not work currently, you'll have to use either LLVM (RADV_PERFTEST=llvm if your build has it enabled by default) or a different driver.

The proprietary Vulkan driver delivers by far the best performance in this game so you'll want to use that if you know how to install it, but _do not_ fuck up your system by installing all the amdgpu-pro packages, it's not necessary.

@doitsujin You can actually just extract the pro-vulkan driver in your home directory and use it without the need to install it at all. (when I say without the need to install it, I mean without package management involved). I made a tutorial on how to do this:
https://www.reddit.com/r/linux_gaming/comments/fddt2n/tutorial_how_to_use_amds_pro_vulkan_driver_or_the/

[aleksbenmaza]

seems like we shall have to wait for another stable release to enjoy this master piece.

[Yjnar]

@oscarcp Yeah I figured the patches do have an impact on performance. Good job so far everyone involved!

[zer0x64]

Just pointing out that Proton 5.0-5 just came out and seems to come with the missing vulkan extensions!

However, that still doesn't seem to work "out-of-the-box", using the steam-runtime beta client and Proton 5.0-5

[RumenBlack]

@RumenBlack Are you running the steam client beta? I am running the game with ubuntu mate 19.04 and the custom proton version just fine.

Maybe I'll try a different DE, I've heard people are having issues with gnome.

[oscarcp]

@RumenBlack Are you running the steam client beta? I am running the game with ubuntu mate 19.04 and the custom proton version just fine.

Maybe I'll try a different DE, I've heard people are having issues with gnome.

So far the only issue that I have in GNOME is the overlay, if anything switches context out of DOOM's windows it will crash espectacularly

[APoniatowski]

I can report, with @999eagle 's solution works. I tested with no launch options, it gets to bethesda's intro video and froze 1 second into the video, causing a crash. but with the launch options she provided, it works 100%. Mouse smoothing is a pain, but one can fix that easily with launch options or in-game settings.
I will play around with the launch options to see which ones one can leave out. But with the steps she provided, it works.

[FTL-Space-Warp]

@APoniatowski by 100% you mean that you have no performance issues?

[ReaperOfSouls1909]

gotta love when people use slow sites for downloads

[MuchiMuchiPink]

@oscarcp interesting, I have most options on High or Ultra and get 60fps with some minor ditches here and there on a RX580 using mesa-git.

[VincentGuinaudeau]

I have most options on High or Ultra and get 60fps with some minor ditches here and there on a RX580 using mesa-git.

@MuchiMuchiPink With steam version or drm-free ? Also are you using radv-llvm, radv-aco or admgpu-pro ?

[elovin]

@999eagle Did you use the DRM-free version ?

[ReaperOfSouls1909]

https://drive.google.com/file/d/1pXLZLXaOTDwhP2T-8043De059yr7xxEc/view?usp=sharing protontkg arch install pkg

[OrdinaryMagician]

Well, got the game to launch, but the performance is atrociously bad (even with everything on lowest) and I learned the hard way that I can't have the steam overlay running. Though, the FPS skyrocket when the game is paused, so it might be that my i5-6400 just isn't any good anymore.

[999eagle]

@elovin No, I'm just using the default unmodified Steam version

[mozo78]

Well, got the game to launch, but the performance is atrociously bad (even with everything on lowest) and I learned the hard way that I can't have the steam overlay running. Though, the FPS skyrocket when the game is paused, so it might be that my i5-6400 just isn't any good anymore.

Nope, I'm with 9900K/1080Ti and we are in the same boat. The game run with very low FPS...

[kisak-valve]

Hi, it may be worthwhile to mention #3267. The shortened version of that discussion is that there may be an upstream regression that makes Denuvo unhappy with these unofficial Proton builds, but is fine with the mainline build of Proton. The failure scenario in that issue report is that the game would work for 5 game starts per day, then go into the agitated state.

This may not directly apply to this game, but it would be something worth keeping an eye on.

[ReaperOfSouls1909]

4790k 1070 here custom pds kernel 5.6 newest and 100+ FPS maxes out 1080p

[elovin]

@ReaperOfSouls1909
Could you please give us more information about your setup (what driver version did you use, what wine/proton version, drm free or not)?

[zaggynl]

gotta love when people use slow sites for downloads

https://zaggy.nl/nextcloud/s/W96Z7BBy6oirJpY

[mozo78]

4790k 1070 here custom pds kernel 5.6 newest and 100+ FPS maxes out 1080p

It's because of pds kernel may be?

[ReaperOfSouls1909]

Proton 5.0.5 440.64 nvidia dkms tkg both drm and drm free work

Sent from my iPhone

On Mar 21, 2020, at 10:39 AM, elovin [e-mail] wrote:


@ReaperOfSouls1909
Cloud you please give us more information about your setup (what driver version did you use, what wine/proton version, drm free or not)?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[MuchiMuchiPink]

@madewokherd I bought the game from the bethesdalauncher, using the drm-free binary, radv-llvm.
I play through Lutris with @liberodark wine as a custom runner.

[gardotd426]

Anyone on Arch-based systems with an AMD card wanting the 19.50 version of the pro vulkan drivers, as @doitsujin suggested to get the best performance, here's a prebuilt version:
vulkan-amdgpu-pro-19.50_967956-1-x86_64.pkg.tar.xz.zip

[MuchiMuchiPink]

@gardotd426 thanks I'll check that out.

[gardotd426]

@MuchiMuchiPink make sure you direct the game to use that vulkan driver with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json

[gardotd426]

But since you use the Bethesda launcher and not Steam the Launcher might be 32-bit, which is the case with Origin, so you have to also declare a 32-bit vulkan driver, so something like: VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/amd_icd64.json, or you can install lib32-amdvlk and use the open 32-bit amdvlk for the launcher, so that would be VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json, but I would just try using the 64-bit one first, no use doing any of that business unless you need it.

[zer0x64]

Good it working using @999eagle proton version. Getting playable FPS, ~20-30, using default graphics settings and a GTX 970.

Arch Linux 64 bits, hardened kernel, Latest Nvidia proprietary driver(DKMS), steam beta.

EDIT: Playing in medium gives a smooth experience in my case

[APoniatowski]

@FTL-Space-Warp so far it looked smooth, no slowdowns yet (below 30fps), besides the mouse smoothing (which is annoying). I will do some more testing, but for now, I have other priorities to attend to.

[APoniatowski]

@kisak-valve 5 game starts? okey dokey. Will keep an eye out for that, as I already started it once.

I almost installed windows, just to be able to play. Gotta love the open source community. Pumped out a workaround, faster than any dev studio can produce one.

[MuchiMuchiPink]

@gardotd426 no, i don't play through the launcher. I just start the DOOMEternalx64vk.exe with a 64bit wineprefix, but thanks :)

[gardotd426]

@MuchiMuchiPink okay then, but I just checked on my bethesda launcher and it IS in fact 32-bit, it appears, so if anyone by chance has the Bethesda version and uses the launcher and is trying to use the pro version of AMD's vulkan driver, you do in fact have to set both 32 and 64-bit in VK_ICD_FILENAMES, so VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json
The prepackaged amdgpu-pro vulkan driver I uploaded above is only the 64-bit, but all you'd need to do is install lib32-amdvlk (or even just try the mesa 32-bit vulkan loader).

[dylanmc1975]

With @999eagle hints and proton, I got this error on proton log
And I realy don't know how to do :(

Unhandled exception: page fault on read access to 0x00000010 in 64-bit code (0x000000014007fbaf). 16179.948:0031:0032:fixme:dbghelp:elf_search_auxv can't find symbol in module

[VincentGuinaudeau]

@dylanmc1975 search in this log for the nearest FATAL ERROR above (might be a couple hundred lines up). And make sure you have the +in_terminal 1 parameter.

[tuxayo]

Just for the record, @zaggynl 's mirror matches the original file of @999eagle
( https://zaggy.nl/nextcloud/s/W96Z7BBy6oirJpY )
md5sum: feec62ea77baa5b37bbe6f92946a42ea

[user1-github]

So is Vulkan loader 1.2.135 still a requirement? I want to test the drm free version with proton 5.0-5 on PlayOnLinux and I'm using Ubuntu 20.04 daily builds. libvulkan is currently at 1.2.131 on Ubuntu 20.04.

[dylanmc1975]

@VincentGuinaudeau I've put PROTON_LOG=1 %command% on launch options, but I have no fatal errors in the steamlog

[VincentGuinaudeau]

use PROTON_LOG=1 %command% +in_terminal 1

[dylanmc1975]

@VincentGuinaudeau 17067.935:002f:0030:warn:debugstr:OutputDebugStringA "Unspecified Vulkan error: Error( VK_ERROR_INITIALIZATION_FAILED )

The only error I got, I think that is my missing vulkan libs 1.2.135

[McMarius11]

it WORKS!!!!!
the DRM-Free does not work for me, i used the normal version. now it runs
edit: now it does not work anymore :/

[kisak-valve]

Hello @dylanmc1975, 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.

[mozo78]

Proton 5.0.5 440.64 nvidia dkms tkg both drm and drm free work
…
Sent from my iPhone
On Mar 21, 2020, at 10:39 AM, elovin @.*> wrote:  @ReaperOfSouls1909 Cloud you please give us more information about your setup (what driver version did you use, what wine/proton version, drm free or not)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Unfortunately it doesn't help. Just installed nvidia-dkms-tkg - no joy. What DE do you running? I'm with Plasma.

[ninjaguardsheep]

Up and running using @999eagle proton build.

Steam game executable with the DRM.

openSUSE Tumbleweed
Mesa 20.0.1
AMD Vega 56

Stable 60fps with vsync on, graphics settings on high.

Thanks all!

[fls2018]

Proton 5.0.5 440.64 nvidia dkms tkg both drm and drm free work
…
Sent from my iPhone
On Mar 21, 2020, at 10:39 AM, elovin _@_.*> wrote:  @ReaperOfSouls1909 Cloud you please give us more information about your setup (what driver version did you use, what wine/proton version, drm free or not)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Unfortunately it doesn't help. Just installed nvidia-dkms-tkg - no joy. What DE do you running? I'm with Plasma.

I don't actually own the game yet so can't test however on thing to keep in mind is 440.64 isn't vulkan 1.2, where as 440.66.03 is 1.2.133 which is the same vulkan version as the Doom Eternal Game Ready Windows driver.

[aleksbenmaza]

@McMarius11

it WORKS!!!!!
the DRM-Free does not work for me, i used the normal version. now it runs

how do you choose the exe to run ?

[zaggynl]

Anyone got it working on Ubuntu 18.04 yet?

[aleksbenmaza]

Anyone got it working on Ubuntu 18.04 yet?

I did not ...

[aleksbenmaza]

@999eagle

how come your home folder (I guess it is) appears in my log ?

Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/aleksbenmaza/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+in_terminal', '1', '+com_skipIntroVideo', '1', '+com_skipSignInManager', '1']
Options: {'nonvapi', 'winetricks', 'winedxgi', 'logcommandtoprefix'}
======================
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

[dylanmc1975]

Hello @dylanmc1975, 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.

@kisak-valve

https://gist.github.com/dylanmc1975/f017873abfc82a9af619adc45667ab80

[kisak-valve]

Thanks @dylanmc1975, since you copied the system info before the s-r-t-info diagnostics finished I can only speculate, but double check that media-libs/mesa is built with USE=vulkan.

[MacroHard-sys]

Anyone got it working on Ubuntu 18.04 yet?

Tried everything here with DRM version, latest attempt with 999eagle post, and no. Crash crash crash crash crash crash crash. Sick of it at this point.

[mozo78]

Proton 5.0.5 440.64 nvidia dkms tkg both drm and drm free work
…
Sent from my iPhone
On Mar 21, 2020, at 10:39 AM, elovin _@_.*> wrote:  @ReaperOfSouls1909 Cloud you please give us more information about your setup (what driver version did you use, what wine/proton version, drm free or not)? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Unfortunately it doesn't help. Just installed nvidia-dkms-tkg - no joy. What DE do you running? I'm with Plasma.

I don't actually own the game yet so can't test however on thing to keep in mind is 440.64 isn't vulkan 1.2, where as 440.66.03 is 1.2.133 which is the same vulkan version as the Doom Eternal Game Ready Windows driver.

I just installed 440.66.03. It's slightly better but I can hardly reach 24 FPS...

[dylanmc1975]

Thanks @dylanmc1975, since you copied the system info before the s-r-t-info diagnostics finished I can only speculate, but double check that media-libs/mesa is built with USE=vulkan.

No, I see now no vulkan support, now I'm recompiling it also with opencl.
But I wonder how doom 2016 works, but maybe was not the vulkan version, I still don't remember

[jerbmega]

Can confirm that @999eagle's build of wine-tkg is working properly.

Gentoo Linux, RX 5700 XT, using AMDGPU-PRO 19.50 with this game as that's reportedly the fastest driver on it. Ultra-Nightmare settings and so far the GPU isn't breaking a sweat.
Using the DRM executable.

[mozo78]

1080Ti - 24 FPS on Low settings :D :D :D

[aleksbenmaza]

@999eagle

how come your home folder (I guess it is) appears in my log ?

Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/aleksbenmaza/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+in_terminal', '1', '+com_skipIntroVideo', '1', '+com_skipSignInManager', '1']
Options: {'nonvapi', 'winetricks', 'winedxgi', 'logcommandtoprefix'}
======================
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

moreover, I tried using your patch with other games, none of them did run.

[MuchiMuchiPink]

@dylanmc1975 doom 2016 still has opengl apis, while Eternal is exlusively vulkan

[dylanmc1975]

Can confirm that @999eagle's build of wine-tkg is working properly.

Gentoo Linux, RX 5700 XT, using AMDGPU-PRO 19.50 with this game as that's reportedly the fastest driver on it. Ultra-Nightmare settings and so far the GPU isn't breaking a sweat.
Using the DRM executable.

Hi, which opencl you have?
I'm using amd-gpu, sure is the fastest diver?

[gblanchard]

@999eagle

Are you able to share the patches for proton so we can compile ourselves?

[PraetorianSC4]

@999eagle

how come your home folder (I guess it is) appears in my log ?

Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/aleksbenmaza/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+in_terminal', '1', '+com_skipIntroVideo', '1', '+com_skipSignInManager', '1']
Options: {'nonvapi', 'winetricks', 'winedxgi', 'logcommandtoprefix'}
======================
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/aleksbenmaza/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

That's probably why its crashing? Mine starts up, I get a black screen, but then the game crashes. I tried with the 5.4.x Proton as well as 5.0.5 proton. Both cases, with Steam version of the game it crashes. Though with 5.0.5, it takes me to the DRM page of the game not being revalidated and that I must wait 24 hours. So that's a wash. Super jelly of all you guys who got it to work.

[fls2018]

1080Ti - 24 FPS on Low settings :D :D :D

Funnily enough NMS has an issue with it's Nvidia vulkan performance which before HG fixed it a temp solution was to spoof as an AMD using this vulkan layer:

https://github.com/volca02/spoof_vendorid

Worth a shot.

[TheTee82]

@fls2018

1080Ti - 24 FPS on Low settings :D :D :D

Funnily enough NMS has an issue with it's Nvidia vulkan performance which before HG fixed it a temp solution was to spoof as an AMD using this vulkan layer:

https://github.com/volca02/spoof_vendorid

Worth a shot.

Thanks.
My 1080 got actually spoofed as an AMD card - there was a warning about AMD working on HDR on launch.
However the issue still persists: Sound stuttering, cinematics very slow and not catching up to the music and ingame gameplay way below 30FPS on low setting (everything disabled).

[jerbmega]

Hi, which opencl you have?

Not sure why it's relevant, but I'm not using anything proprietary for OpenCL, just Mesa.

I'm using amd-gpu, sure is the fastest diver?

From what I've heard, AMDVLK and RADV are both significantly slower, and RADV/ACO crashes on launch.

[999eagle]

@aleksbenmaza @PraetorianSC4 you need at least GLIBC 2.31 because I compiled my build on Arch, sorry. I'm not sure why my build directory still shows up in the binaries though.

@gblanchard I linked the exact commit where the patch was added. I compiled proton-tkg with the winevulkan_fshack_opts.mypatch community patch and everything else with default configuration.

[gblanchard]

@999eagle Thanks!

[gblanchard]

@999eagle For the record though it works with your patches on gentoo with GLIBC 2.30

:man_shrugging:

[ashkitten]

Hi, it may be worthwhile to mention #3267. The shortened version of that discussion is that there may be an upstream regression that makes Denuvo unhappy with these unofficial Proton builds, but is fine with the mainline build of Proton. The failure scenario in that issue report is that the game would work for 5 game starts per day, then go into the agitated state.

This may not directly apply to this game, but it would be something worth keeping an eye on.

@kisak-valve that thread seems to suggest that deleting the compatdata directory will reset denuvo's state. is that true? it doesn't seem to be in my case.

[mozo78]

1080Ti - 24 FPS on Low settings :D :D :D

Funnily enough NMS has an issue with it's Nvidia vulkan performance which before HG fixed it a temp solution was to spoof as an AMD using this vulkan layer:

https://github.com/volca02/spoof_vendorid

Worth a shot.

Yes, it squeezing 3-4 FPS more but it's still unplayable. Thank you :)

[kisak-valve]

Hello @ashkitten, my understanding is that the state needs to reset on some Denuvo server.

[ashkitten]

can anyone confirm that proton 5.0-5 works?

[PraetorianSC4]

@ashkitten

It leads to Denuvo registration failures for me. 5.4.x gives me a blackscreen (with @999eagle 's patched wine build), but ultimately crashes.

R7 3800X | GTX 1080Ti | Manjaro 5.4.4 | 440.64 | Vulkan Headers/ICD-Loader: 1.2.135

[tehradamant]

Tried everything I could find (including drm free exes). The only thing that worked was 999eagle's proton build and the official exe. But still experiencing abysmal performance (20 fps on all lows on a 1070 gtx) on Arch 5.5.11tkg and nvidia driver 440.66.03. Also sound is cracking in the game.

[TheTee82]

can anyone confirm that proton 5.0-5 works?

@ashkitten
The build provided by @999eagle ( https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602028651 ) worked fine at least to get to ingame state.
However for some it doesn't work and for some others it works unplayably slow (this is my case running a 1080).

But you could give it a try. Maybe you're lucky.

[MacroHard-sys]

999eagle's build did not work

deb 18.04
steam beta
glibc 2.31
nvidia 440

ryzen 5
1060 3gb
asus b350
8gb

Still just goes to that stupid DRM pop up. something tells me it would work without DRM now. Somehow I'm glad I think I'd be more upset if it ran but then gave unplayable fps.

Good luck and thanks guys/gals I think I'm gonna bail out for attempts and wait for a proper valve release proton that works as good as 2016 does. Gonna go reinstall because now rig randomly freezing and giving system error reporting on boot up. Awesome.

[TheTee82]

Still just goes to that stupid DRM pop up. something tells me it would work without DRM now.

@MacroHard-sys
That's because you tried too many different proton builds during 24h
Had the same yesterday. Today all was fine due to the crappy denuvo finally purging my id from their locked database. So just wait... or try the drm free version :wink:

[Berinth]

I'm in Denuvo jail at this point, too. I got the DRM-free exe and dropped it in to the game folder after backing up the original exe, but it seems to crash even sooner. Is there anything else I need to do to get the DRM-free exe to work?

[VincentGuinaudeau]

@Berinth If like me you have the FATAL ERROR: Z:\home\[...]\.local\steamam\steamapps\common\DOOMEternal\base\disclayout.cfg is unexpected, check manifest, I resolved this one by also coping all files inside DOOMEternal/base/ from the drm-free version, expect for the files ending with .streamdb and not the folders. That's nine files total.

But I did'nt try to launch it via steam. I launch directly from the terminal with a command like
STEAM_COMPAT_DATA_PATH=~/.local/share/steam/steamapps/compatdata/782330 ~/.steam/steam/steamapps/common/Proton\ 5.0/proton run ~/.local/share/steam/steamapps/common/DOOMEternal/DOOMEternalx64vk_DRMFREE.exe +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

[d3rhans]

@999eagle You build works for me (kind off)

1. Dowloaded the build and placed it in ~/.steam/compatibilitytools.d/
2. Set steam to opt for beta and restarted steam
3. Set the proton version to use to your build in steam
4. Set the launch options as you suggested (+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1)

Game starts, is more or less playable. On medium graphics settings I get between 25 and 40 FPS.

I run Fedora 31 Workstation, kernel 5.5.7-200.fc31 with NVIDA driver 440.64. Hardware: Ryzen 1700, RTX 2060, 16GB RAM.

Given that the game basically runs with proton (at least in some setups), I'm rather confident that this will work flawlessly soon.

Thank you @999eagle and everybody else involved for your effort!

[cabinboy1031]

The fix by @999eagle works for me, though no matter what quality settings i pick the framerate seems to be capped at around 15-20 fps. Hopefully theres a new official proton patch for it soon, but right now im going to enjoy the game. Does the Denuvo-free exe make the workaround play better?

Fedora 31
Intel-i5 6600K
Nvidia GTX970
16GB Ram

[Ahmed-E-86]

If you want to update Vulkan Loader to the latest version on Ubuntu 18.04, and above, use these commands:

wget -qO - http://packages.lunarg.com/lunarg-signing-key-pub.asc | sudo apt-key add -
sudo wget -qO /etc/apt/sources.list.d/lunarg-vulkan-bionic.list http://packages.lunarg.com/vulkan/lunarg-vulkan-bionic.list
sudo apt update
sudo apt dist-upgrade

[Berinth]

@Berinth If like me you have the FATAL ERROR: Z:\home\[...]\.local\steamam\steamapps\common\DOOMEternal\base\disclayout.cfg is unexpected, check manifest, I resolved this one by also coping all files inside DOOMEternal/base/ from the drm-free version, expect for the files ending with .streamdb and not the folders. That's nine files total.

But I did'nt try to launch it via steam. I launch directly from the terminal with a command like
STEAM_COMPAT_DATA_PATH=~/.local/share/steam/steamapps/compatdata/782330 ~/.steam/steam/steamapps/common/Proton\ 5.0/proton run ~/.local/share/steam/steamapps/common/DOOMEternal/DOOMEternalx64vk_DRMFREE.exe +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

I'm on Pop_os so my directories are a little different. But I adapted that command and it returns this: no such file or directory: ~/.steam/debian-installation/steamapps/common/Proton\ 5.0/dist/bin/wine
even though I have checked at that spot and wine does exist there

[VincentGuinaudeau]

@Berinth I think I also got this error yesterday, but don't remember for sure. Maybe check if their is a symlink in the path, and change your path accordingly so it's doesn't use the symlink. If this doesn't work I have no idea.

[kisak-valve]

Hello @Berinth, try using an absolute path (/home/username) instead of ~.

[mozo78]

Guys, can you file a bug at NVIDIA? I'm not that good in english so I ask you for this. Give us a link here and we'll confirm the problem once the topic is created.

[Berinth]

Hello @Berinth, try using an absolute path (/home/username) instead of ~.

I tried that- same result. My home partition lives on a separate drive than my root partition, but it's mounted at /home. Could that be throwing it for a loop?

Edit: I'm an idiot. Was accidentally running the wrong script. The script runs now, but the game still doesn't run

[wundrweapon]

Just used @999eagle's setup. Void Linux, just about everything up-to-date, including Vulkan loader and headers (why it says 1.2.133 I have no idea; I'm using 135). Worked without a hitch. i3wm workspace switching can be finnicky but other than that, hey: it works. I'll admit to being immensely disappointed in the framerate but I figure that will handle itself with some graphics setting adjustments and when they remove Denubloat down the line. Rip and Tear! :metal:

EDIT: forgot to mention, kinda important, when the campaign mission started it warned me it couldn't connect to Steam and that I'd be more or less running offline? I hope that's just DRM being aggro from my testing last night but I seriously have no idea what the true cause is

[FTL-Space-Warp]

while using 999eagle's solution i noticed Doom eternal's ingame info panel says I'm using vulkan 1.1.119 despite the fact that I have vulkan-icd-loader version 1.2.135-1 installed and I'm using the steam beta, I'm doing this on Arch with the DRM version of the game

spectacle removes the focus from the game, making it freeze, that's why it shows 0fps and a black screen

[rabidlassie]

Someone on ProtonDB reported that bleeding edge GPU drivers with Proton 5.0-5 works absolutely fine. Can anyone confirm that? I am still stuck in Denuvo hell, so I can't test Proton as well as @999eagle 's build.

[dylanmc1975]

Now works like a charm! thanks to @999eagle

AMD Ryzen 5 1600X
16 GB Memory
Radeon RX 480
Gentoo Linux
Kernel 5.5.9

@kisak-valve I was missing a vulkan support on my machine, thanks

[mozo78]

Someone on ProtonDB reported that bleeding edge GPU drivers with Proton 5.0-5 works absolutely fine. Can anyone confirm that? I am still stuck in Denuvo hell, so I can't test Proton as well as @999eagle 's build.

There is no newer driver than 440.66.03 I think. I use them and I can't get more than 25-30 FPS.

[oscarcp]

while using 999eagle's solution i noticed Doom eternal's ingame info panel says I'm using vulkan 1.1.119 despite the fact that I have vulkan-icd-loader version 1.2.135-1 installed and I'm using the steam beta, I'm doing this on Arch with the DRM version of the game

spectacle removes the focus from the game, making it freeze, that's why it shows 0fps and a black screen

This are my stats, it's working also with 1.2.133 instead of 1.2.135 (i took a photo becasue if I try to screenshot if crashes)

[tehradamant]

Is it just me or does it seem like people with bad performance are mostly geforce 10xx users? Seems fine for AMD cards and for 20xx series

[tizzir]

It seems like a number of people who have managed to run the game at a higher framerate have been using the PDS scheduler. I can confirm that using the PDS scheduler on the xanmod kernel does not provide a higher framerate when paired with the new TKG proton. However, I'm currently locked out and unable to test any other configurations with PDS.

Would someone who has the game booting with stock proton 5.0-5 be able to test a TKG kernel with PDS to see if it results in better performance? It might be helpful if we can narrow down why some people are seeing acceptable performance and some are not.

I'm using a 1070 fwiw.

[mozo78]

In this tred a user complains with GTX970 too as I recall.

[tizzir]

Is it just me or does it seem like people with bad performance are mostly geforce 10xx users? Seems fine for AMD cards and for 20xx series

I believe @ReaperOfSouls1909 mentioned that they achieve 100+fps using a 1070

[elovin]

The default DRM version works fine with:

Ryzen 3700X
Vega 56

ArchLinux (zen kernel)
mesa-git
steam-beta
proton-tkg build with the patch mentioned above

steam lauch options (remember when first starting the game do not use the skipSignInManager ..):
RADV_PERFTEST=llvm +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

Also the performance is playable with around 60fps on high and WQHD resolution

[jrgp]

With @999eagle's solution, I'm able to start the game and play it, which is a huge deal as nothing in this thread last night worked. But, performance is bad (low FPS).

As with others in this situation, I'm on a 1080ti (with Ryzen 3950x). Latest Ubuntu Focal with all packages updated and custom 5.6.0-rc6 kernel.

Maybe the game relies on ray tracing or some similar new tech that the 10 series geforce cards don't have?

Would upgrading the system vulkan packages any further potentially fix this? The suggested lunarg-vulkan repo above didn't have any updated packages for my system.

[winteriscariot]

Is it just me or does it seem like people with bad performance are mostly geforce 10xx users? Seems fine for AMD cards and for 20xx series

@tehradamant it is not fine for my 2060 so i don't think that logic pans out. in the Fortress of Doom I'm getting 20-30fps on my 2060 @ 1440p; in windows it's pegged at 144fps

the difference between those who get high performance and those who don't seems to be amd vs nvidia

[tuxayo]

@GloriousEggroll should you integrate this commit and tag a release? https://github.com/Tk-Glitch/PKGBUILDS/commit/52d0e915a7c88acaf544ad1c9b7eb9fcc23645cb

We have a handful of people managing to the run the game thank to that. Having it in your build would allow wider testing.

(someone correct me if the custom proton builds need something else)

[mozo78]

Is it just me or does it seem like people with bad performance are mostly geforce 10xx users? Seems fine for AMD cards and for 20xx series

I believe @ReaperOfSouls1909 mentioned that they achieve 100+fps using a 1070

I think it's a mistake or he will be The Only One :)

[ReaperOfSouls1909]

Is it just me or does it seem like people with bad performance are mostly geforce 10xx users? Seems fine for AMD cards and for 20xx series

I believe @ReaperOfSouls1909 mentioned that they achieve 100+fps using a 1070

I think it's a mistake or he will be The Only One :)

nah not the only one lol

[mozo78]

Some video or screenshots are welcome :)

[Birdman7]

I tried @999eagle's fix plus updated drivers, still nothing. Note that I am running a GTX 950. Maybe I'm dumb and need an upgrade?

[MagicRB]

I tried proton 5.0, drm free version and it runs, but it's closer to a slideshow than a game. I'm running a GTX 1060 btw

[pastapojken]

FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required for me with latest mesa-git, icd-loader & 999eagle's proton, I'm using a R9 290 with the amdgpu driver. I tried both with & without RADV_PERFTEST=llvm, still nothing...
steam-782330.log
DRM free version doesn't run, can't actually test the denuvo one as I've messed around too much and have to wait my 24h...

[boehmseb]

I might have found a solution for NVIDIA users encountering bad frame rates when using the proton build provided by @999eagle:

Find the file user_settings.py coming with the zip and comment out the line "PROTON_NVAPI_DISABLE": "1". Now i get decent framerates of >70 at Full HD and Ultra Nightmare Settings on a RTX 2080 Ti and ~40 FPS when rendering at 4k (I got ~20FPS with any settings before).

Note: after disabling the option, I got a warning about outdated drivers (you saw this screenshot a few times in this thread) but could safely ignore it.

[ryester27]

@999eagle's Proton build works fine for me with the DRM version. Didn't even need the extra command line arguments that were in the instructions, but did need RADV_PERFTEST=llvm.

Arch Linux
Ryzen 2600
RX 560
1080p high preset (medium texture pool)
40-55fps

By the way, were the first 2 startup logo videos suppose to have sound to them? Everything is silent until I reach the main menu

[CatalinPuscoci]

Do we have any idea why nvidia users are getting lower performance? That's the idea I'm getting so far...

[zaggynl]

Tried upgrading vulkan packages via https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602076507 but game does not start via normal Proton 5.05 and custom 5.04.
Any workaround for the glibc issue apart from upgrading to Ubuntu 19.10 or unreleased 20.04?

Normal Proton 5.05 results in: http://i.imgur.com/Q5cps5h.png and large logfile:
steam-782330_zaggynl.log.zip

Custom 5.04:

======================
Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/az/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+in_terminal', '1', '+com_skipIntroVideo', '1', '+com_skipKeyPressOnLoadScreens', '1', '+com_skipSignInManager', '1']
Options: {'logcommandtoprefix', 'winetricks', 'winedxgi', 'nonvapi'}
======================
ERROR: ld.so: object '/home/az/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/az/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/az/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Which is caused by different Glibc as per previous comments?

[gort818]

I got it working with @999eagle's build.
Arch
vega56
with amdgpu pro vulkan driver
high settings 1440p 90-100 fps

Ultra Nightmare 100 fps

[jalabb]

With @999eagle 's build and launch options, and the Steam Beta, and the updated stuff from that comment the game still won't run at all. I just get a black screen and then back to the desktop.
I don't see what I'm missing...
steam-782330.log

Could it be because I'm on Xubuntu, not Arch?

[FTL-Space-Warp]

@boehmseb I tried it and i saw no noticeable difference. I should also mention that the graphics feel low quality, everything is a bit blurry, even on high settings (with or without boehmseb's fix). Most noticeable in the main menu.

[boehmseb]

@boehmseb I tried it and i saw no noticeable difference. I should also mention that the graphics feel low quality, everything is a bit blurry, even on high settings (with or without boehmseb's fix). Most noticeable in the main menu.

I have to admit that after playing some more it seems like I happened to be in a "good" spot on the map in my first test. However, on my machine there is a noticeable difference that makes the game at least playable for me.

[mozo78]

@boehmseb
Thanks for you efforts but this didn't help me too :(

[ryester27]

@poke86 you're going to have the same problems as others using Ubuntu, so look through this thread for Ubuntu fixes

[MasterCATZ]

@999eagle

I am using ubuntu 19.10 , as far as I know everything is up to date
it dies after it prompts for winetricks

error.log

Vulkan Instance Version: 1.2.131

5.5.11-050511-generic
GL_RENDERER: AMD Radeon R9 200 Series (HAWAII, DRM 3.36.0, 5.5.11-050511-generic, LLVM 9.0.1)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 20.1.0-devel (git-5cc3ab0 2020-03-21 eoan-oibaf-ppa)

[MagicRB]

vulkan is old, you need to update manually

[MagicRB]

https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602076507

[tehradamant]

Tried @boehmseb fix and it didn't improve things much for me. I think it got like maybe 3-4 extra fps for silky smooth cinematic 24 fps. It felt a bit smoother than before but i'm not sure.

[TheTee82]

@boehmseb I tried your fix but it doesn't really improve anything. I get the outdated driver message though so I guess the fix was applied.
But performance is not looking fine at all.
This is with everyt hing set to Low and disabling any effects (blur, etc.):

I noticed however, the ingame-menu is running really smooth and fast with 144 FPS but as soon as I resume it's back to 10-20 FPS tops.
I have a strong feeling I'm missing something essential here.

[MasterCATZ]

forgotten to run sudo ldconfig
Vulkan Instance Version: 1.2.135

however starting doom 2016 with proton_tkg_5.4.r10.g7c7868f4
it is showing vulkan 1.2.128
error.log

so how do i get steam to use the version ubuntu has ?

real shame seeing all these comments about poor performance , 2016 had god like performance I could play with over 60fps maxed settings with my R9 290 @ 400mhz ...

[UVCRocketRunner]

Probably off-topic, but what kind of installation of Steam are all of you using? I've been using the Flatpak package, but I think I might have to use RPM instead, because I literally cannot follow @999eagle 's instructions due to the folder I need to extract the .tar to being a broken link instead. I think I'll just move my games and reinstall Steam so I can attempt her fix.

[pastapojken]

In case someone else has the same moronic issue as me: vulkan-radeon fucks with amdvlk. So remove vulkan-radeon :) ( caused the game to return FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required )

[TheTee82]

@UVCRocketRunner

Probably off-topic, but what kind of installation of Steam are all of you using?

Using my distros native default installation which served me fine until now.

multilib/steam-manjaro 1.0.0.61-7 (2.7 MiB 3.0 MiB) (Installed)
    Valve's digital software delivery system

[MagicRB]

I cannot get any reasonable performance from DOOM, tried 4 different wines, updated everything and disable nvapi...

[dylanmc1975]

Played 2 hours, no issues :)

``
/0 bus Motherboard
/0/0 memory 15GiB System memory
/0/1 processor AMD Ryzen 5 1600X Six-Core Processor 3600
/0/100 bridge Family 17h (Models 00h-0fh) Root Complex
/0/100/0.2 generic Family 17h (Models 00h-0fh) I/O Memory Management Unit
/0/100/1.3 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/1.3/0 bus 300 Series Chipset USB 3.1 xHCI Controller
/0/100/1.3/0.1 storage 300 Series Chipset SATA Controller
/0/100/1.3/0.2 bridge Advanced Micro Devices, Inc. [AMD]
/0/100/1.3/0.2/0 bridge 300 Series Chipset PCIe Port
/0/100/1.3/0.2/0/0 eth0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/1.3/0.2/1 bridge 300 Series Chipset PCIe Port
/0/100/1.3/0.2/1/0 bridge ASM1083/1085 PCIe to PCI Bridge
/0/100/1.3/0.2/4 bridge 300 Series Chipset PCIe Port
/0/100/3.1 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/3.1/0 display Ellesmere [Radeon RX 480]

proton_tkg_5.4.r10.g7c7868f4
Kernel 5.5.9
amdgpu

[zaggynl]

@dylanmc1975 can you add your steam system info?

[mrAndersen]

@dylanmc1975 +1, please add vulkan\os info

[brettalcox]

@999eagle worked for me. (i'm on Arch with 1.2.135 vulkan and GeForce 1060). Played through the first level fine, now the loading screen for second level always crashes....

[mrAndersen]

Any ubuntu ppa for vulkan 1.2 btw? Can't find any =(

[MagicRB]

Another reason why to go team red

[MagicRB]

@brettalcox what vulkan version does doom think you have? Mine thinks I have 1.2.119, I think. What driver version do you run, what kernel and did you do anything aside from using @999eagle 's wine?

[drsaeva]

@UVCRocketRunner

....wat? follow 999eagle's instructions, but make the directory yourself and extract the tar there. it works fine, aside from perf issues.

[brettalcox]

@MagicRB not sure how to determine what version Doom thinks I have, but kernel 5.5.10-arch1-1 and 440.64 Nvidia. And nothing else. Running it out of Steam too fyi

[rabidlassie]

Got it working with @999eagle 's build. Alt+Tab and taking screenshots completely break the game. Might be related to Steam Overlay, will test it.

There are some scenery that I can easily get 60+ FPS but majority of the game plays around 30-45 FPS.

I have also installed Vulkan 1.2.135 but game plays with 1.2.133, like others. System info also points out to 1.2.133.

System Info

EDIT: Sorry for photo rotations :(

Using "Low" preset:

Using "Ultra-Nightmare" preset:

[UVCRocketRunner]

@UVCRocketRunner

....wat? follow 999eagle's instructions, but make the directory yourself and extract the tar there. it works fine, aside from perf issues.

Well, I tried that just now, and I assume I'm supposed to be able to select her Proton build separately, because I can still only use 5.0.5 and I'm still at square one.

[MagicRB]

@brettalcox enable debug info in doom, settings, video

[brettalcox]

@MagicRB says it's using 1.1.119

[blazini36]

I can't get this running for the life of me. I did @999eagle directions, I compiled vulkan-loader 1.2.135, but I'm not 100% sure it installed correctly, if not I'm on Manjaro's 1.2.132. Same thing pretty much no matter what I do, get the "AMD does not have HDR support" popup then it closes. I'm launching it from steam with the options. Not sure where the log is stored but the system is:
Manjaro-Gnome
kernel=5.6.0-2-MANJARO
RX 5700xt
Ryzen 3600

[wundrweapon]

For those who want to take screenshots, I've found that scrot works fine. I have a keybind in my i3config to scrot -mz (along with a couple other settings for file name/location but that's off-topic). I can confirm that that will take a screenshot with no crashing

[dylanmc1975]

I can't get this running for the life of me. I did @999eagle directions, I compiled vulkan-loader 1.2.135, but I'm not 100% sure it installed correctly, if not I'm on Manjaro's 1.2.132. Same thing pretty much no matter what I do, get the "AMD does not have HDR support" popup then it closes. I'm launching it from steam with the options. Not sure where the log is stored but the system is:
Manjaro-Gnome
kernel=5.6.0-2-MANJARO
RX 5700xt
Ryzen 3600

If you want to be sure, launch vulkaninfo.
The only way to know if it's installed correctly

[HellToupee1]

Works for me using proton-tkg with winevulkan_fshack_opts.mypatch
Vulkan Instance Version: 1.2.135
Nvidia Driver 440.66.03

Taking screenshots with steam using F12 did not freeze the game for me.

Performance however is poor,

[MagicRB]

vulkaninfo says i've got 1.1.119, i'll double check my setup

[MagicRB]

wait, my api version is 1.1.119

[rassie]

I think I've managed to compile proton-tkg with winevulkan_fshack_opts.mypatch for Ubuntu 18.04, however I can't get it work yet. What makes matters more complicated is that my copy is from Bethesda.net, so I'm trynig to set it up via non-Steam game integration. If anyone has managed to get non-steam configuration running, please tell!

[thebitstick]

Can confirm it works on my machine

OS: Fedora 32
GNOME: 3.36 X11
AMD Radeon RX 470
Latest Steam Beta
DRM Game
Proton from @999eagle
With these options: +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

[d3rhans]

@thebitstick how is your performance ingame?

I just checked and it seems the game/proton/steam is using vulkan 1.1.119, at least the ingame performance metrics suggest so. The version installed on my system is 1.2.131 however.

Any idea how to change that? And might that cause the performance problems?

[GloriousEggroll]

Doot Eternal via steam + +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
Fedora 31, the rest is in the screenshot. no hacky bs:
mesa-git, standard llvm shipped with fed 31 + vulkan-loader 1.2.135
I have not gotten it to work with ACO, but there are a few more things I need to try.
I will have a GE build available as soon as i finish sorting some other minor kinks:

[thebitstick]

@d3rhans 60+ FPS. Running a 60 Hz Ultrawide monitor so I have no complaints.
Vulkan just updated via dnf to mesa-vulkan-drivers-20.0.2-1.fc32.x86_64.

[dennis1248]

The Steam version of the game runs on my AMD Navi 10 card. It's performance at high-settings is decent enough, it's playable, not great through. On high settings (I am using what the game defaulted to) at 3440x1440 it runs around 50-80fps depending on the scene. I played through the first level with only minor issues, I noticed some minor graphical artifacting in certan particle effects.

I am running the Steam Beta client and using the custom Proton build linked here:
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602028651

Using MESA the game just crashes after the tray icon appears,
Log here

With AMDVLK-pro the game does run.
How-to here

Using the following launch options:
VK_ICD_FILENAMES=/home/dennis/.drivers/amd-vlk-pro/amd_icd64.json %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

I did not experience the issue some people have reported of game crashing on GNOME (Xwayland) after ALT+TABing.

Full system specs:
Ryzen 7 3800x
AMD RX 5700
16GB RAM
Fedora Workstation 32 Beta

MESA 20.1
AMDGPU-pro 19.50 (The Vulkan component of it at least)
GNOME 3.36

[ReaperOfSouls1909]

beat the game on arch Nvidia driver newest Vk beta kernel 5.6 PDS gnome DE has no crashing no issues used proton 5.0.5

[gblanchard]

Confirmed that commenting out this line under user_settings.py in the patched proton for nvidia users gets playable framerate now. I used to get 15...now over 60+

    #Disable nvapi and nvapi64
#     "PROTON_NVAPI_DISABLE": "1",

[rabidlassie]

@ReaperOfSouls1909 can you post your system info?

• Steam -> Help -> System Information

@gblanchard didn't work for me. Can you post your system info as well?

[ReaperOfSouls1909]

Can’t install fedora 31 going to get it working there

Sent from my iPhone

On Mar 21, 2020, at 10:41 PM, Burak S [e-mail] wrote:


@ReaperOfSouls1909 can you post your system info?

Steam -> Help -> System Information
@gblanchard didn't work for me. Can you post your system info as well?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[gblanchard]

AMD Ryzen 9 3950X 16-Core Processor
"Gentoo Base System release 2.7" (64 bit)
Kernel Name:  Linux
Kernel Version:  5.4.14-gentoo-x86_64
Driver:  NVIDIA Corporation GeForce GTX 1660/PCIe/SSE2
Driver Version:  4.6.0 NVIDIA 440.44

Using patched proton 5.4.r10 + the beta steam client.
My audio is a little glitchy though...but playable.

[rabidlassie]

From NVIDIA X Server Settings I've set PowerMizer Setting to Maximum Performance and OpenGL Image Setting to High Performance. Had a solid FPS increase but still having hard time hitting stable 60 FPS at Ultra Nightmare.

[jjbarr]

I commented out the nvapi_disable and it didn't do much. Bought me a few frames but my framerate still isn't what it should be, according to windows reports from comparable setups. According to the DE performance metrics my GPU utilization is %25 percent which is apparently in the red. Dunno if there's something up with my system or if this is really a game issue.

ED: Gah! That's not utilization! That's render time.

My GPU is eating 28ms/frame on average.

[d3rhans]

Confirmed that commenting out this line under user_settings.py in the patched proton for nvidia users gets playable framerate now. I used to get 15...now over 60+

    #Disable nvapi and nvapi64
#     "PROTON_NVAPI_DISABLE": "1",

Tried that, stabilized by FPS around 60 on medium settings. I get some graphic glitches from time to time though, but nothing serious.

[tizzir]

@ReaperOfSouls1909

beat the game on arch Nvidia driver newest Vk beta kernel 5.6 PDS gnome DE has no crashing no issues used proton 5.0.5

Are you able to compare this performance to that of a kernel using a scheduler other than PDS?

[d3rhans]

Just a side note for NVIDIA users: I had to update to driver 440.66.03 to get Vulkan 1.2 running (instead of 1.1.119). No influence on the performance though.

[GloriousEggroll]

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2

go kill the thingies.

[gardotd426]

Amazing. Hey @GloriousEggroll, you said mesa-git is required, but that's only if you're going to be using RADV/LLVM, right? Or do you need mesa-git underneath even if you're using vulkan-amdgpu-pro?

[GloriousEggroll]

Amazing. Hey @GloriousEggroll, you said mesa-git is required, but that's only if you're going to be using RADV/LLVM, right? Or do you need mesa-git underneath even if you're using vulkan-amdgpu-pro?

I haven't tested with vulkan-amdgpu-pro, so I don't know.

[rabidlassie]

@tizzir I have compiled a custom kernel with PDS and still had the same results. My previous kernel was 5.4.24-1.

[PopeRigby]

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2

go kill the thingies.

Still not working for me with mesa-git

[ashkitten]

i was getting some graphical artifacts with radv, so i tried vulkan-amdgpu-pro and it worked much better (plus ~30% fps boost!). however, it seems like vulkan-amdgpu-pro thinks vsync enabled means it should cap fps at 60, when my refresh rate is actually 144. does this happen to other people using vulkan-amdgpu-pro? (or amdvlk, it happens with that too). freesync does not work properly without vsync enabled, so this is really frustrating.

[dennis1248]

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2

go kill the thingies.

Tried running it with Vulkan-AMDGPU-pro, it just crashes during start the same way it does with vanilla Proton.

Log in case it's useful.

[brettalcox]

@GloriousEggroll doesn't work with vulkan 1.2.135 / nvidia 440.66.03, just crashes after the GPU out of date warning. The only thing that has worked for me so far is @999eagle

[MasterCATZ]

@GloriousEggroll

error.log

not launching any idea what else I have broken >?
its a PC copy manually added into steam
Ubuntu 19.10 Kernel 5.5
Vulkan Instance Version: 1.2.135 but when I play doom 2016 it still says 1.2.128
Vulkan version 1.2.131 guess its time to see about updating this

tried using just the launcher
error.log

tried
https://drivers.amd.com/drivers/linux//19.50/amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz
extracted "vulkan-amdgpu-pro_19.50-967956_amd64.deb".
placed "amdvlk64.so" and "amd_icd64.json" from "opt" folder. in steampath/amdvlk/

Steam launch options set as VK_ICD_FILENAMES=/steampath/amdvlk/amd_icd64.json %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

error.log

[parkerlreed]

Crashes shortly after the AMD no support HDR splash

RADV_PERFTEST=llvm PROTON_LOG=1 %command%

steam-782330.log

Using the new GE version from @GloriousEggroll

vulkan-icd-loader 1.2.135-1
mesa-aco-git 20.0.0.20200226.7a965bd4c38-7

[parkerlreed]

Is it possible the Denuvo exe is causing this? The Steam version doesnt have the other version that Bethesda left in there.

[parkerlreed]

mesa-git 1:20.1.0_devel.121420.500842399a3-1
vulkan-radeon-git 1:20.1.0_devel.121420.500842399a3-1

steam-782330.log

[parkerlreed]

Tried the DRM free exe from Bethesda and got farther to a black screen but still crashes :/

[jldez]

@GloriousEggroll Doesn't work either. Crash shortly after out of data nvidia driver warning. Says I need 442.74, but I can't get that version on ubuntu, don't I? I tried to cheat with changing the required version in the launcher.cfg, but it still crashes.

[PraetorianSC4]

@GloriousEggroll likewise, same issue as @jldez. Manjaro, 440.64. There's some kind of a driver mismatch issue wherein it keeps detecting 337.88. Unknown reasons.

Unfortunate that it doesn't work for all.

[MasterCATZ]

LD_PRELOAD=/usr/lib32/libudev.so.1 STEAM_RUNTIME=1 steam

yielded some different results
FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required.
so I guess this is a mesa thing ?

steamterminal.txt

[rabidlassie]

@jldez 442.74 is for Windows, its Linux counterpart is 440.66.03. You can get the driver here.

[parkerlreed]

Steam runtime should already use any system libraries that are newer.

@MasterCATZ Why preload a 32bit lib for a 64bit game?

[MasterCATZ]

because the elf errors in the logs were driving me nuts

[parkerlreed]

@MasterCATZ

You completely screwed the launch command. Did you forget the %command%?

 Z:\ZFS3WAY\SteamLibrary\steamapps\Manual\DOOM.Eternal\DOOMEternalx64vk.exe VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlk/amd_icd64.json %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

There's an environment variable AFTER the exe

[MasterCATZ]

I was using the idTechLauncher.exe that time it then launches that

[parkerlreed]

Which proton are you using? I cant even get it to show the command line output with the GE 5.4.

RADV_PERFTEST=llvm PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

I get nothing in the terminal running Steam

[MasterCATZ]

same result no logs,
proton is not even being started ,
the log file should be in home folder, steam - ID# .log
even this resulted in nothing
WINEDEBUG=+timestamp,+pid,+tid,+seh,+debugstr,+module

for now I need to work out this
FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required

[parkerlreed]

Check to make sure you have the latest driver. Mesa 20.1 git. That seems to be a hard requirement.

vulkaninfo | grep -i 8bit

[MasterCATZ]

Mesa 20.1.0-devel (git-5cc3ab0 2020-03-21 eoan-oibaf-ppa)

so I guess I just wasted the entire weekend and $100 , why could they not have used same engine as 2016 ..

aio@aio:~$ vulkaninfo | grep -i 8bit
ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd32.json
ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file amd_icd64.json
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
WARNING: radv is not a conformant vulkan implementation, testing use only.
VkPhysicalDevice8BitStorageFeatures:
storageBuffer8BitAccess = false
uniformAndStorageBuffer8BitAccess = false
storageBuffer8BitAccess = false
uniformAndStorageBuffer8BitAccess = false

#
VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlk/amd_icd64.json STEAM_RUNTIME=1 steam
Running Steam on ubuntu 19.10 64-bit
STEAM_RUNTIME is enabled by the user
Pins up-to-date!
/home/aio/.steam/ubuntu12_32/steam
[2020-03-22 16:59:27] Startup - updater built Mar 20 2020 18:24:57
[2020-03-22 16:59:27] Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
[2020-03-22 16:59:27] Verifying installation...
[2020-03-22 16:59:27] Verification complete
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
------ Initializing File System ------
Current search path:
- C:/users/steamuser/Saved Games/id Software/DOOMEternal/base/
- Z:/ZFS3WAY/SteamLibrary/steamapps/Manual/DOOM.Eternal/base/
------ File System initialized.
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
----- Registering decl types -----
----- Starting decls parse jobs -----
Added structured log listener print-redirect
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
WARNING: idBroadcastManager::Register called with out of range system ID [65535]
------ Command Line ------
Z:\ZFS3WAYSteamLibrarysteamapps\Manual\DOOM.EternalDOOMEternalx64vk.exe RADV_PERFTEST=llvm WINEDEBUG=+timestamp,+pid,+tid,+seh,+debugstr,+module PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
2020-03-22T16:59:44.515+10:00 LOG: Command Line: Z:\ZFS3WAYSteamLibrarysteamapps\Manual\DOOM.EternalDOOMEternalx64vk.exe RADV_PERFTEST=llvm WINEDEBUG=+timestamp,+pid,+tid,+seh,+debugstr,+module PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

idLib::SetProduction( PROD_PRODUCTION )
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
Initialized stack tracer
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.

:@

just explored /etc/vulkan/icd.d

dead links to amd_icd64.json + amd_icd32.json

that used to point to
/etc/alternatives/amd_icd64.json
/etc/alternatives/amd_icd32.json

that pointed to /opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd32.json etc
guess I better fix that now

[parkerlreed]

Odd that is reporting true for me

ker@wolfcola ~]$ DISPLAY=:0 vulkaninfo | grep -i 8bit                ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
VK_KHR_8bit_storage                     : extension revision 1
VkPhysicalDevice8BitStorageFeatures:
storageBuffer8BitAccess           = true
uniformAndStorageBuffer8BitAccess = true
storageBuffer8BitAccess                            = true
uniformAndStorageBuffer8BitAccess                  = true

[MasterCATZ]

Progress , I got to a splash screen , so it seems links to links to links were broken at some stage , unsure how my vulkan games have been running now ...
I feel $100 richer now

RADV_PERFTEST=llvm PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

proton_tkg_5.4.r10.g7c7868f4
terminalproton_tkg_5.4.r10.g7c7868f4.txt
error.log

[UVCRocketRunner]

After having to reinstall Steam and much distraction, I finally got 999's Proton fix to work--after a second launch attempt, anyways.

I didn't screencap after turning on the perf monitor, but I believe my vulkan-icd-loader isn't on the latest version, which might explain the crackly audio I got. So, two last simpleton questions: how do I update the icd-loader to the latest version, and for that matter, should I update my Nvidia driver to the bleeding-edge version?

(EDIT: hooray for cellphone photo orientation...hopefully it's right-side-up in full-view...)

(EDIT 2: Just as reminder of basic specs: Fedora 31, i7-3770K, GTX 1050Ti (440.64-2 driver))

[EldarAgalarov]

I installed:

Vulkan Headers and Loader 1.2.135
Nvidia driver 440.66.03 beta
MESA 20.1
Proton 5.4 GE-2

And i'm getting just black screen. Game not launching but not crashing too. What to do?

[UVCRocketRunner]

Is it your first attempt? You may have to just get it to crash/kill it, then just try again, like I did.

[zaggynl]

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2

go kill the thingies.

Thanks!

Had another go but no joy.
-Removed kisak-mesa ppa, installed oibaf ppa as it has newer mesa, upgraded packages, noted restore commands and package names for when things go boom, rebooted.
-Ran Doom Eternal with:
RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

Without PROTON_NO_ESYNC=1 it would complain:
612.339:0036:0037:err:esync:esync_init Failed to open esync shared memory file; make sure no stale wineserver instances are running without WINEESYNC.

vulkaninfo head:
Vulkan Instance Version: 1.2.70

vulkaninfo | grep -i 8bit:

VK_KHR_8bit_storage                 : extension revision  1
VK_KHR_8bit_storage                 : extension revision  1

Log: https://gist.githubusercontent.com/zaggynl/6a4ab3b3a48b2fb1808ac0ada15ff0f7/raw/3d4c9d466bb3ba7cb79afbe789bc3df63b671ba6/zaggynl%2520another%2520doom%2520eternal%2520attempt

Steam system info: https://gist.githubusercontent.com/zaggynl/2e3e46c2d6588608d2dcae8f24583251/raw/aaaea3be8e4dbc555fa5457f63655248bfbe425f/zaggynl%2520sysinfo%25202020-03-22

My notes so far:

Install oibaf ppa for latest mesa bits
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
REMOVE EXISTING PPAs, I HAD KISAK-MESA:
sudo apt install ppa-purge
sudo ppa-purge ppa:kisak/kisak-mesa
NOTE PACKAGES REMOVED!
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
NOTE PPA PURGE COMMAND FOR OIBAF: sudo ppa-purge ppa:oibaf/graphics-drivers

Get latest vulkan on Ubuntu 18.04
From: https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602076507
wget -qO - http://packages.lunarg.com/lunarg-signing-key-pub.asc | sudo apt-key add -
sudo wget -qO /etc/apt/sources.list.d/lunarg-vulkan-bionic.list http://packages.lunarg.com/vulkan/lunarg-vulkan-bionic.list
sudo apt update
sudo apt dist-upgrade

Download latest tar.gz rom:
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2
Place extracted Proton-5.4-GE-2 folder into:  ~/.steam/root/compatibilitytools.d/
Create compatibilitytools.d if does not exist
Restart Steam
Select Proton-5.4-GE-2 as specific compabitility tool
Set Doom Eternal launch options to:
RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1 
(ACO not supported yet, ESYNC disabling because broken, log for log, rest to skip crap)
Start game

[m0nt3sh0t]

Using Kernel 5.5.8
Mesa 20.1.0-devel (git-d9d549ff88)
Vulkan Instance Version: 1.2.135
GloriousEggroll 5.4-2

I get nothing, just sits at playing for about a minute than closes. Last thing in the Proton Log is
Application tried to create a winow but no driver could be loaded.

steam-782330.log

[mozo78]

m NVIDIA X Server Settings I've set PowerMizer Setting to Maximum Performance and OpenGL Image Setting

Yes, this helps a bit and adds additional 5-6 FPS. Now a can play with 35 FPS on 1080 Ti :)

[MasterCATZ]

to even make it worse a patch was just released that has got windows users crashing in game ...

I still keep crashing as soon as sound kicks in , I see a flash of a menu button and it stays on black screen with the loading symbol half done , currently having steam re-download the game and starting fresh

[mozo78]

Gyus,
Here's the bug report on NVIDIA site. Please, confirm the low performance problem, thanks:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394

[OrdinaryMagician]

Running alright with 5.4-GE-2 over here, still got the issue where alt-tabbing or using the steam overlay freezes with a black screen, though, but the game's playable otherwise.

Gotta admit the performance issues are a bit of a pain sometimes, but I generally only get drops down to 20 FPS so it's still... "playable".

[oscarcp]

Confirmed that commenting out this line under user_settings.py in the patched proton for nvidia users gets playable framerate now. I used to get 15...now over 60+

    #Disable nvapi and nvapi64
#     "PROTON_NVAPI_DISABLE": "1",

I can confirm that it makes a difference, in m case all framedrop/stutters from the game have vanished, the FPS it shows is the FPS I get

[e-user]

Related issue for those who are stuck with the Flatpak version of Steam, like me: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/989

tl;dr if you're using Steam from Flatpak, it gets vulkan-loader from org.freedesktop.Platform.GL and org.freedesktop.Platform.GL32 and so updating your OS' version of vulkan-loader is futile.

[mute55]

Kernel 5.5.10
Nvidia 440.64
Vulkan Instance Version: 1.2.135
Proton-tkg 5.4.r10.g7c7868f4
i7 5930k & GTX TITAN X (Maxwell)

I was getting 10-20 fps on low, with PROTON_NVAPI_DISABLE i get around 40~ with drops down to 20. I know my card is old but I feel as though performance should be a little better considering i'm at 1080p and running on low.

Possible cause, ingame metrics shows vulkan version 1.1.119, despite vulkaninfo showing 1.2.135.
Any ideas anyone? I'm not using flatpak steam, and i'm using steam beta.

[gblanchard]

Gyus,
Here's the bug report on NVIDIA site. Please, confirm the low performance problem, thanks:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394

This is not a bug with NVIDIA. Keep in mind that what we are doing here isn't technically supported.

I'm running this game @ ~70fps on a smaller video card than yours. It's all a matter of which library you are running and versions.

[xDShot]

Controller input is messed up. Sticks behave randomly.

[mozo78]

Gyus,
Here's the bug report on NVIDIA site. Please, confirm the low performance problem, thanks:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394

This is not a bug with NVIDIA. Keep in mind that what we are doing here isn't technically supported.

I'm running this game @ ~70fps on a smaller video card than yours. It's all a matter of which library you are running and versions.

Here are the newest packages. Do you tell me I have to install older libraries to get any decent performance? It is NVIDIA problem. All AMD users have good performance.

[jsfdez]

Trying the custom Proton and removing the line "PROTON_NVAPI_DISABLE": "1", the performance is not good :(

[parkerlreed]

All AMD users have good performance

I'm pretty sure it's not launching for the majority of us.

[parkerlreed]

Also for everyone that has gotten it to work, are you using the Denuvo exe or not?

[jsfdez]

Also for everyone that has gotten it to work, are you using the Denuvo exe or not?

Steam unmodified version.

[parkerlreed]

mesa-git 1:20.1.0_devel.121471.f02ae698674-1
vulkan-radeon-git 1:20.1.0_devel.121471.f02ae698674-1

RADV_PERFTEST=llvm PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

New mesa-git update. Still nothing.

Steam Native
steam-782330.log

Steam Runtime
steam-782330.log

System
system.txt

Seems to be the same as ever for me

36368.922:0035:0036:warn:seh:virtual_unwind exception data not found in L"DOOMEternalx64vk.exe" Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x000000014093f5bd).

[xDShot]

Random hangs with mesa radv git.

[RalfVB]

I couldn't get the game to run on Kubuntu 18.10 whatever suggestion I tried, so I upgraded to a daily beta of Kubuntu 20.04 and installed the latest 440 Nvidia drivers.

With Steam set to beta and the custom Proton build, I'm happy to report the game now runs. I'm using the Denuvo exe.

It's playable enough, but there are some fullscreen resolution issues and performance isn't too good, even with all graphics settings turned down. I'm playing it on an i7 with GTX1050ti.

Amazing game. Hope the remaining issues are resolved soon.

[werman]

@xDShot

Random hangs with mesa radv git.

Try closed source admgpu-pro vulkan driver - it didn't hang in several hours of gameplay.

[TimoFreiberg]

mesa-git 1:20.1.0_devel.121471.f02ae698674-1
vulkan-radeon-git 1:20.1.0_devel.121471.f02ae698674-1

RADV_PERFTEST=llvm PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

New mesa-git update. Still nothing.

Steam Native
steam-782330.log

Steam Runtime
steam-782330.log

System
system.txt

Seems to be the same as ever for me

36368.922:0035:0036:warn:seh:virtual_unwind exception data not found in L"DOOMEternalx64vk.exe"
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x000000014093f5bd).```

Same for me. What GPU are you using? I'm on a Radeon RX 5700.
I'm using Proton-5.4-GE-2, I assume you're using that, too?

[xDShot]

Appears no hangs with amdvlk provided by Arch team (https://www.archlinux.org/packages/extra/x86_64/amdvlk/), although 20% less FPS than on mesa radv.

UPD: Nope. Just got freeze as well.

[parkerlreed]

@TimoFreiberg RX 480 and yes I am trying the 5.4 GE 2

[elovin]

@TimoFreiberg @parkerlreed
This might be obvious but did you create a Bethesda.net account and then link it to your steam account ? The first time you start the game you should not use the +com_skipSignInManager 1 option otherwise the game wont start at all because you need to add an account first.

[parkerlreed]

That was just an attempt at anything working. Same result without it

I get the AMD HDR not supported and then nothing else. Crashes.

[TimoFreiberg]

Thanks for the tips @elovin, I get the same error log without the +com_skipSignInManager 1 argument though.

@parkerlreed I don't see anything about AMD HDR not supported in my logs, where do you see that error?

[parkerlreed]

@TimoFreiberg It should be a window that comes up. Check your Vulkan installation if it doesn't

I get the crash after hitting that play (maybe 8 seconds).

[elovin]

What vulkan icd loader version are you using ? If you use the steam runtime it will use the vulkan loader from the runtime in this case you have to use the steam beta to get the latest vulkan loader from the steam runtime.

[ccasar]

Has anyone of you tried the Proton build linked in https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602028651?

The game runs fine for me with that build but crashes immediately once I try the Proton GE build.

[parkerlreed]

@elovin Already on Steam beta. Plus my system icd loader is on the newest as well.

[parker@wolfcola ~]$ pacman -Q vulkan-icd-loader 
vulkan-icd-loader 1.2.135-1

[TimoFreiberg]

@parkerlreed ah, that popup, i disabled it with the recommendation from the release notes here: https://github.com/GloriousEggroll/proton-ge-custom/releases

This kind person here also recommended the proton-tkg build uploaded by @999eagle instead of Proton-5.4-GE-2:
https://www.reddit.com/r/linux_gaming/comments/fmsoc2/gloriouseggrolls_proton54ge2_released/fl6v52i/

A shame, I wanted to avoid downloading random stuff from file upload sites, I'll probably compile it myself.

[parkerlreed]

@TimoFreiberg I mean I wasn't going to worry about disabling the popup until I can figure out why it's crashing.

[elovin]

@TimoFreiberg you can build it yourself if you are on arch linux or use an arch linux docker container
download the proton-tkg PKGBUILD and add winevulkan_fshack_opts.mypatch to the _community_patches option in the proton-tkg.cfg file. You can examine both the files before you build them to trust them. Then just extract the tar ball if you dont want to install it system wide.

[parkerlreed]

I assume try this version? https://github.com/Tk-Glitch/PKGBUILDS/releases/tag/5.4.r0.g676dd026

[elovin]

@parkerlreed No that version was uploaded 8 days ago you have to pull the latest git master version add the patch and then build it.

Follow these instructions and add winevulkan_fshack_opts.mypatch to the _community_patches option in the proton-tkg.cfg file otherwise follow the defaults of the build script and when it asks you to use the community patch type y/yes.

[MuchiMuchiPink]

The performance is significantly better with vulkan-amdgpu-pro. All I did was downloading the Ubuntu package, extracted amd_icd64.json, amdvlk64.so, edited the json pointing to the correct location of the binary and use this for VK_ICDFILE enviroment. With RADV I had some drops and glitches, all gone now.

[parkerlreed]

We have life with the tkg build from above. Currently testing the Mesa git RADv and will see how that goes.

[Bleuzen]

I got the drm (steam) version running yesterday with the Steam beta and Proton build by @999eagle (https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602028651).

Today I decided to try Proton-5.4-GE-2, because performance was really bad yesterday and I did want to try if this GE build makes a difference..
and yes, it really makes a big difference. But not in performance or another good way. The game doesn't even launch anymore.

I now get this when I try to launch the drm version:

When I click on the link, I get this website:

It says it failed to revalidate my purchase and I should try again in 24 hours.

This now also happens with the build I used yesterday, so I guess this is Denuvo blocking it.
So I tried the drm free exe, but this one doesn't launch with both Proton builds (999eagle and GE builds). I get a fullscreen blackscreen for some seconds but then it crashes.

Now I can't play anymore :/
... or should I better say, watch the Doom Eternal movie in 'smooth' 24 fps.

This is my log from the drm free exe, which is crashing after a short blackscreen:
steam-782330.log

Anyone has an idea what the problem may be and how to get this running?
Strange thing is, the normal drm version did run yesterday, but I can't currently use it because of Denubloat.

[DistantThunder]

Confirmed working on my end with the Steam / Denuvo version with following setup:

Base system

• Operating System: Arch Linux
• KDE Plasma Version: 5.18.1
• KDE Frameworks Version: 5.67.0
• Kernel Version: 5.5.4-zen1-1-zen
• OS Type: 64-bit
• Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
• Memory: 31,3 Gio

Graphics

• mesa-git: 20.1.0_devel.121471.f02ae698674-1
• GPU id: 0 (AMD RADV/ACO VEGA10 (LLVM 9.0.1))
• ⚠️ Vulkan Instance Version: 1.2.135 ⚠️ /Obtained with latest vulkan-icd-loader and lib32-vulkan-icd-loader packages/

Procedure

Obtain a patched Proton version:

• https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2

  • From other builds floating around, I was particularly missing:
    
    
    
    • VK_KHR_get_surface_capabilities2
      
      

      Integrate it

    
    

• Follow standard procedure to integrate with Steam runtime:

  • On my end, uncompressed to ~/.local/share/Steam/compatibilitytools.d/
• Restart Steam if it was already running

• Purchase + Download the game if not done already

  Run the game with it

• Select "Proton-5.4-GE-2" in the Steam per game settings for DoomEternal

  Mind that it appears ACO compiler backend is not yet suitable here

• ⚠️⚠️⚠️ For RADV vulkan implementation on Mesa, at least up to above mentioned commit on master branch, ACO does not expose a number of Vulkan extensions mandatory for running the game. You have to resort to the "old" LLVM compiler by unsetting aco compiler backend: This achieved on my end by having the game launching like this:

  • RADV_PERFTEST="" %command%
• You may set whatever options suits you in the launch parameters
• Run the game

The above is what worked for me, mileage may vary for everyone.

Using RADV, performance is acceptable and most of the time smooth for me, as long as you don't dip below 60 fps. When that happens, for some reason, the rendering becomes sluggish and though the game reports 60fps, it actually feels like it dropped to 30. This is with triplebuffering vsync enabled and my compositor being turned off.

I still feel like overall the game should run better and be smoother.

:information_source: N.B. :

• Your Alt-tabbing experience may vary, for myself, I'm able to switch desktops without too much trouble but had a black screen when specifically alt-tabbing from the game on the same desktop

[parkerlreed]

@Bleuzen That 5.4 GE 2 doesnt seem to work for anyone. Use the build you were using and try some of the other drivers if on AMD

[Bleuzen]

@parkerlreed
I switched back from Proton-5.4-GE-2 to the proton_tkg_5.4.r10.g7c7868f4 build that worked yesterday. But I can't use the drm version anymore because I got blocked by Denuvo for the next 24 hours.
So now I try to get the drm free exe to work, but this does nothing but show a blackscreen and crashes.

I'm on Nvidia with a GTX 1060 and driver version 440.64.

I also edited my last post to include a log of the drm free version crashing.

Edit: I already tried removing my wine prefix (...SteamLibrary/steamapps/compatdata/782330/) and letting it recreate after switching back to the proton_tkg_5.4.r10.g7c7868f4 build.
DRM free version still crashes.

[Voxed]

@Bleuzen Need more confirmation but I think the DRM free exe no longer works with the current game update. Crashes for me aswell.

[tizzir]

@Voxed

Have you tried the solution mentioned by @VincentGuinaudeau?:

@Berinth If like me you have the FATAL ERROR: Z:\home\[...]\.local\steamam\steamapps\common\DOOMEternal\base\disclayout.cfg is unexpected, check manifest, I resolved this one by also coping all files inside DOOMEternal/base/ from the drm-free version, expect for the files ending with .streamdb and not the folders. That's nine files total.

But I did'nt try to launch it via steam. I launch directly from the terminal with a command like
STEAM_COMPAT_DATA_PATH=~/.local/share/steam/steamapps/compatdata/782330 ~/.steam/steam/steamapps/common/Proton\ 5.0/proton run ~/.local/share/steam/steamapps/common/DOOMEternal/DOOMEternalx64vk_DRMFREE.exe +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1

It looks like you can no longer drop the DRM-free exe into an existing install without also copying over some game content.

[MacroHard-sys]

Back again..... baaaaack again....

Get the same DRM reeeeeeee message with that GE 2 build.

I'm starting to think I've been ruined because I messed with the DRM free with steam, that maybe I'm perma listed, even though I bought the darn game? If that's the case valve is getting the longest phone call they ever had.

Thoughts anyone?

[DistantThunder]

@MacroHard-sys
No, it's most likely just the next full 24h since you were banned.

For some reasons, different Wine versions or even the same Wine version appears as different computers to the DRM, which triggers the activation threshold. It's truly cancer.

[MacroHard-sys]

@MacroHard-sys
No, it's most likely just the next full 24h since you were banned.

For some reasons, different Wine versions or even the same Wine version appears as different computers to the DRM, which triggers the activation threshold. It's truly cancer.

Ok, because it's given me that every single attempt since release day. Made one curious. Thanks. Really slowing this down because then in theory nothing else I try today will work. Then one attempt tomorrow until nothing else works. Rinse repeat.

[linduxed]

I too can't get past the SteamAPI, just like @LarsBremen and @jrgp. The discussion in the Gist by @annmuor where @SalmonSeasoning was trying stuff out, that discussion also did not help me.

I'm still stuck on just getting the "Unable to initialize SteamAPI" window.

[Voxed]

@tizzir I'll look into that, thanks.

[dpanter]

Alright!
Game is running, been testing a bit now that my Denuvo 24 hour timeout is over. _Thanks Denuvo, I love you too._

• Siduction (Debian sid based), KDE 5.17.5
• Xrender compositor (auto disables when running the game)
• Intel 8700k, CPU scaling governor: performance
• Nvidia 1080ti, 440.64-2
• Steam beta client
• Proton-5.4-GE-2

Nvidia settings:

• ForceCompositionPipeline enabled. Disabling has no effect on fps.
• Powermizer settings - no effect on fps. Set to Auto.
• OpenGL image settings - High Performance made a real impact and the game ran much smoother.

Doom Eternal tweaks

• PROTON_NVAPI_DISABLE 1 or 0, no effect on fps
• Using the normal Steam game exe
• Launch options: +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 (not needed)
• Edited launcher.cfg to get rid of driver warnings.
• I'm using dual monitors, main monitor native res is 3440x1440, eventually decided to go with 2560x1080 and no resolution scaling.
• Motion blur settings had no effect on fps.
• Fullscreen, Medium setting preset, vsync off, HDR off, Chromatic abb on, DOF on, DOF AF off.

In my opinion... Playable
Not amazing performance of course... Fps goes above 60 when nothing much is going on but doesn't seem to dip below 40 in hectic fights. There's a definite performance hit when the action heats up, but at least nothing major that breaks gameplay. Setting higher graphics presets totally murders performance during intense action and if you can't hit the enemies due to low fps and stutter... well. _You die, obviously._

Notes
Works with Steam overlay enabled, with noticeable performance degradation. Game feels much more choppy. Can still turn Doomguy around with the mouse when the overlay is activated.

ALT+TAB hangs the game, music/ambient sounds keep playing with a black screen, same with and without Steam overlay.

There's a massive amount of warnings in the Doom console, no idea if those are relevant.

Fps in the first room with the 3 zombies ranges from 45 to 120+. Ugh.

[Voxed]

@dpanter Any tips for not tripping Denuvo? Got in yesterday only to get instantly locked out again.

[dpanter]

Any tips for not tripping Denuvo?

Not really, other than the current theory that it might trigger from using different Proton versions. I've restarted Doom Eternal something like 50 times today, not triggered it again. Isn't Denuvo like totally awesome and so much the best thing ever? Yummy.

[mozo78]

The different Wine/Proton versions are triggering Denuvo. Keep it in mind.

[ahoneybun]

I tried the custom Proton version from @999eagle and the launcher option and that works!

OS: Pop!_OS 19.10
GPU: AMD RX 580

[brettalcox]

Thought it was corrupted save file, but 2nd save also crashes every time Mission #2 starts loading

[Tbird761]

Anyone know if an official Proton beta update is coming from Valve some time soon? I'm not comfortable running binaries from unofficial sources.

[jas0n098]

Denuvo doesn't like Wine Staging, which proton-ge is based on, so if you want to avoid tripping Denuvo stick to normal Proton

[jldez]

Sorry for basic questions below. I'm not used to play with these things and usually wait for more stable solutions. However, this is DOOM and thus important and urgent.

1. So, how can I install nvidia-driver-440. I'm using ubuntu 18.04 and the latest version available with apt-get is 435. I tried getting 440.64 from https://www.nvidia.com/en-us/drivers/unix/ , then running the script in terminal. However, it fails and tells me I need to have nothing running on GPU. Does it mean I need to run this with no desktop GUI? How do I do that?

2. Is it confirmed that the mesa-git thing is mandatory? And are there risks to break things? I'm kind of scared to install that, because I have a good record of breaking ubuntu and drivers when messing around with these king of things.

[ahoneybun]

@jldez

1. I would recommend this archive:

https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

There it's two commands to install it and then a reboot.

1. I didn't need the latest though I'm on 19.10 so I have a newer version then you do when compared to 18.04 LTS.

[rodhull]

I am running Ubuntu 19.10 w/ latest proprietary Nvidia driver (440.64) from the proprietary drivers PPA, Steam beta, and tried both GE's latest patched Proton build, and also 999eagle's build. I have whatever the latest vulkan packages from https://packages.lunarg.com/vulkan/lunarg-vulkan-bionic.list provide (only looks like 1.2.131, not 1.2.135 but I thought the .135 version is bundled with the Steam beta?)

Anyway, I STILL can't get it to start, with it telling me it needs "VK_EXT_full_screen_exclusive" (with either of the patched Proton builds - which I thought both include a fix for this requirement - but this is still the crash point for me - how come?):

Application Info
-------------------------
App    : DOOMEternal - 1.0.2
Engine : idTech - 7.1.1
-------------------------
Instance Extensions
-------------------------
 + VK_KHR_surface
 + VK_KHR_win32_surface
 + VK_KHR_get_surface_capabilities2
Initialized stack tracer
FATAL ERROR: Please update your driver: VK_EXT_full_screen_exclusive is required.
wine: Unhandled exception 0x80000003 in thread 29 at address 0000000140822626 (thread 0029), starting debugger...

[maarvw]

Having no luck with any of these solutions sadly. I'm using Linux Mint 19.3 (ubuntu-based) with an Nvidia GTX 1070.
Proton 5.0-5 gets me to a black screen which crashes after a few seconds.
Proton-5.4-GE-2 gives me this window:

clicking #str_launch_button_label, i get the same blackscreen problem.
@999eagle's custom proton doesn't even start anything, gives me this log:

Proton:`` 1552061114 proton-tkg-5.4.r10.g7c7868f4 SteamGameId: 782330 Command: ['/home/marvin/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+in_terminal', '1', '+com_skipIntroVideo', '1', '+com_skipKeyPressOnLoadScreens', '1', '+com_skipSignInManager', '1'] Options: {'nonvapi', 'winedxgi', 'logcommandtoprefix', 'noesync', 'winetricks'} ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored. wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

this is apparently because I don't have the latest GLIBC libraries, but those don't seem to be released for my OS yet. Anyone know any workarounds for this?

[MacroHard-sys]

@maarvw I tried this .deb package, no idea if it worked because I'm in DRM hell. give it a shot and report. https://debian.pkgs.org/sid/debian-main-amd64/libc6_2.30-2_amd64.deb.html

[kisak-valve]

Hello @rodhull, please check if you've opted into Steam's client beta. The 2020-03-20 client provides the 1.2.135 vulkan loader.

[rodhull]

Yes, I have done that I think from the Settings - Account area (see above) - Steam updated itself straight after I did this, and I have no further client updates.

[maarvw]

@MacroHard-sys I'm not too experienced with that sort of stuff, are there any risks associated with that? and I don't think the amd64 package would be the right one for me, I don't have any amd products in my computer. Or maybe I'm just being stupid

[mathew2214]

@MacroHard-sys I'm not too experienced with that sort of stuff, are there any risks associated with that? and I don't think the amd64 package would be the right one for me, I don't have any amd products in my computer. Or maybe I'm just being stupid

when it comes to linux packaging, AMD64 and x86_64 are almost always interchangeable. you should be fine using AMD64 packages on an Intel x86_64 system.
i know for a fact Debian's packages with the AMD64 label are compatible with x86_64 as well.

[MacroHard-sys]

@MacroHard-sys I'm not too experienced with that sort of stuff, are there any risks associated with that? and I don't think the amd64 package would be the right one for me, I don't have any amd products in my computer. Or maybe I'm just being stupid

Legit concern I suppose. Not 100% sure. It's from debian.pkgs.org so, I figured it was safe. If someone else could chime in that'd be great.

[jldez]

Thank you @ahoneybun , I got the 440 version.
If anyone wants to know how to get the nvidia-driver-440:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
reboot? (not sure if necessary)
sudo apt-get install nvidia-driver-440
reboot

However, I still have the same problem as others. Using the proton 5.4 ge-2 thing, I get the screen

It still thinks that I have the 337.88 version. But nvidia-smi confims I have 440.64. (It says I need 442.74, but this is the windows equivalent someone told). After pressing either yes or play, nothing happens.

[maarvw]

alright, I'll try it. Last I heard version 2.31 was required though? that link is for 2.30

[MacroHard-sys]

alright, I'll try it. Last I heard version 2.31 was required though? that link is for 2.30

Someone further up said they had it going with 2.30, I couldn't find a 2.31.

[Birdman7]

Almost nothing I've tried on this board worked. Time to pirate Windows 10.

[alosarjos]

Just found this video:

https://www.youtube.com/watch?v=lpHdJ_i1T_k&feature=youtu.be

So I guess we need to wait for a mesa update too?

[DistantThunder]

@MuchiMuchiPink

Did you do that on Arch ? Are you using the regular kernel driver ? I tried that but the game just won't run with the amd pro vulkan driver.
Even though I can have DXVK titles, and native apps like VKCUBE & Shadow of the Tomb Raider run fine with it.

[jldez]

@Birdman7 My love for DOOM < my hate of windows ;)

I'm just going to wait for a stable solution. Good luck to the competent people working on this and thank you!

[ahoneybun]

Thank you @ahoneybun , I got the 440 version.
If anyone wants to know how to get the nvidia-driver-440:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
reboot? (not sure if necessary)
sudo apt-get install nvidia-driver-440
reboot

However, I still have the same problem as others. Using the proton 5.4 ge-2 thing, I get the screen

It still thinks that I have the 337.88 version. But nvidia-smi confims I have 440.64. (It says I need 442.74, but this is the windows equivalent someone told). After pressing either yes or play, nothing happens.

You don't have to reboot at that point:

sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get update
sudo apt-get install nvidia-driver-440
sudo systemctl reboot

I'm not sure about NVIDIA but I do see the HDR message with my AMD GPU but I can just click OK to that one.

[mathew2214]

i dont understand what's going wrong in my case.
ive updated mesa to 20.10, im using proton-ge-custom 5.4-ge-2
ive disabled the HDR warnings
ive disabled aco for this game
ive opted into steam client beta
here's my sysinfo and proton log
https://gist.github.com/mathew2214/dcde50c78274a7629c6ae74277c426b5

UPDATE: how strange, steam claims my mesa version to be 19.3. yet glxinfo -B correctly shows that its 20.1.0.

[digikin]

I can confirm that on Ubuntu 20.04 will work.
Nvidia Driver: 440.66.03
VulkanInfo: Vulkan Instance Version: 1.2.131

1. Install the patch from @999eagle here
2. Make a dir and move it to ~/.steam/root/compatibilitytools.d/
3. Opt into to steam beta Steam>Setting>Account>Beta participation
4. Change steam play to the patched proton version Steam>Settings>Steam Play>Enable Steam Play/Run other titles with
5. Set Launch Options Library>Doom>Settings(Gear Icon)>Properties>Set Launch Options
+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
6. Set the game to only use that version Library>Doom>Settings(Gear Icon)>Properties>Force the use of a specific Steam Play compatibility tool

$cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Focal Fossa (development branch)"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

$vulkaninfo
==========
VULKANINFO
==========

Vulkan Instance Version: 1.2.131


Instance Extensions: count = 18
====================

$lshw -c video
WARNING: you should run this program as super-user.
  *-display                 
       description: VGA compatible controller
       product: TU102 [TITAN RTX]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:65:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:107 memory:d7000000-d7ffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:b000(size=128) memory:c0000-dffff
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.
$ nvidia-smi
Sun Mar 22 12:32:02 2020       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.66.03    Driver Version: 440.66.03    CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  TITAN RTX           Off  | 00000000:65:00.0  On |                  N/A |
| 41%   35C    P0    65W / 280W |    660MiB / 24217MiB |     27%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1832      G   /usr/lib/xorg/Xorg                            45MiB |
|    0      2707      G   /usr/lib/xorg/Xorg                           206MiB |
|    0      2932      G   /usr/bin/gnome-shell                         299MiB |
|    0      6251      G   ...ic/.local/share/Steam/ubuntu12_32/steam    21MiB |
|    0      6262      G   ./steamwebhelper                               3MiB |
|    0      6280      G   ...uest-channel-token=17622251660803828376

[jldez]

With your steps @digikin, I get this screen:

Then crash

However, I'm on ubuntu 18.04. And for the vulkan version, I though that using the beta updates from steam would include the correct vulkan version? Or I misunderstood?

[digikin]

From what I understand the Vulkan support comes from the Nvidia drivers.
NVIDIA provides full Vulkan 1.2 support and functionality on NVIDIA GeForce and Quadro graphics card with one of the following Turing, Volta, Pascal, Maxwell (first and second generation) and Kepler based GPUs
@jldez For some reason I couldn't get it to work on 18.04. The Nvidia Driver 440.66.03 requires the higher kernel. With April coming next month I thought this was a good opportunity to move to 20.04LTS.
sudo do-release-upgrade -d
I am very happy with 20.04!!

[GirardR1006]

Good evening everyone, seems there has been quite an activity on this issue.
My small contribution:

With an Arch Linux fully upgraded with latest NVIDIA drivers and vulkan loader and the custom prefix linked here (with all relevant launch option enables) https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602028651 the game launches.

However I have huge performances issues (might come from my old GPU but since lot of people here noticed performance drop this could be related).

Steam log: https://we.tl/t-2N2iqK5acs
Steam system info: https://gist.github.com/GirardR1006/bac21ceb93c5e45570658f6d2c343bec

[MacroHard-sys]

From what I understand the Vulkan support comes from the Nvidia drivers.
NVIDIA provides full Vulkan 1.2 support and functionality on NVIDIA GeForce and Quadro graphics card with one of the following Turing, Volta, Pascal, Maxwell (first and second generation) and Kepler based GPUs
@jldez For some reason I couldn't get it to work on 18.04. The Nvidia Driver 440.66.03 requires the higher kernel. With April coming next month I thought this was a good opportunity to move to 20.04LTS.
sudo do-release-upgrade -d
I am very happy with 20.04!!

going to try this with my toaster later, how is your performance?

[mozo78]

Good evening everyone, seems there has been quite an activity on this issue.
My small contribution:

With an Arch Linux fully upgraded with latest NVIDIA drivers and vulkan loader and the custom prefix linked here (with all relevant launch option enables) #3654 (comment) the game launches.

However I have huge performances issues (might come from my old GPU but since lot of people here noticed performance drop this could be related).

Steam log: https://we.tl/t-2N2iqK5acs
Steam system info: https://gist.github.com/GirardR1006/bac21ceb93c5e45570658f6d2c343bec

Hello,
See this comment here:
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602175041

[anotherbugmaster]

Hi everyone. If anyone has performance issues, try to disable Steam FPS counter. I know, it sounds silly, but I just increased my FPS from 20-30 to 55-60, and I have RTX 2070.

Here's a thread on reddit where some guys have discovered that thing.

The only problem I have now is crackling sound.

Full specs:

CPU: i5 9600k
GPU: Nvidia RTX 2070
RAM: 32 GB
OS: Arch Linux
Proton: 5.4 from @999eagle

[maarvw]

@MacroHard-sys when trying to use dpkg on that .deb file, i get errors saying it would damage locales. The whole text was in german as that's the language my PC is set to so I won't bother posting it here. I think it might just be impossible to get running on my current OS. Looks like I would need to switch to Arch or use another newer ubuntu. Mint 19.3 seems to be based on ubuntu 18.04 and I've seen people here saying it only works on 20.x and up.

[elovin]

I can confirm that amdgpu-pro has much better performance than RADV
(tested with amdgpu 19.50 vs mesa-git using Vega 56 and Ryzen 3700X) but since amdgpu-pros vulkan part does not support freesync it does not look as smooth (even tough its around 60 vs 100 fps AVG).

[tehradamant]

Tried Proton GE (doesn't launch), tried compiling TKG build, tried disabling fps counter and overlay too. No change in fps at all.

[d3rhans]

I tested some more, here is the state of things:

• Still using the proton build by @999eagle, everything else doesn't work for me so far
• Performance is not good. I'm currently playingon 1280x720 with medium settings. FPS is arround 60, but actually the settings don't seem to matter much, as I get only a slight decrease with settings to "Ultra" and FullHD resolution
• CPU and GPU don't seem to be utilized fully
• Vulkan Version and NVIDIA driver version don't seem to matter much with Vulkan 1.2.133 provided by NVIDIA driver 440.66.3 I have the same results as with Vulkan 1.1.119 provided by NVIDIA driver 440.60
• I've just learned (this was probably already discussed here, I don't follow up all the comments) that NVIDIA released a driver 442.75 for Doom Eternal, which is not available for Linux. Maybe we have more luck after the next NVIDIA driver update.

Played for a few hours, there are some minor graphic glitches and some less minor sound glitches (mostly music playback). Otherwise the game runs stable.

(Fedora Workstation 32beta, Kernel 5.6 git, HW: Ryzen 1700, RTX2060, 16GB RAM)

[Birdman7]

@d3rhans So basically, Team Red have better luck in this case than Team Green? Just feeling around for things to note.

[mozo78]

Hi everyone. If anyone has performance issues, try to disable Steam FPS counter. I know, it sounds silly, but I just increased my FPS from 20-30 to 55-60, and I have RTX 2070.

Here's a thread on reddit where some guys have discovered that thing.

The only problem I have now is crackling sound.

Full specs:

CPU: i5 9600k
GPU: Nvidia RTX 2070
RAM: 32 GB
OS: Arch Linux
Proton: 5.4 from @999eagle

I tried with DRM Free exe and in this way I don't use Steam at all so there's no Steam FPS counter. No matter what, I always get 26-28 FPS...

[d3rhans]

@Birdman7 maybe, seems a bit like it. But we will only now, when NVIDIA releases an updated driver for Linux at some point. But as I stated earlier, the game basically works with proton so I'm confident this will work flawlessly with Steam+Proton soon.

[Voxed]

I was finally able to get the steam game to run on TkG-r10 but not GE. I was also able to switch from GE to TkG without tripping Denuvo, however this could just be a one time thing.

What I did to try to avoid getting another 24 hour re-validation timeout:

• Backup Steam/steamapps/compatdata/782330 and Steam/userdata directories in-case of Denuvo trip. I don't know if these backups will work but according to pcgamingwiki the offline tokens are stored in the userdata directory.
• Using protontricks enable "Hide Wine version from applications" under Staging.

All unconfirmed but I was able to avoid getting sent to Denuvo hell for a third time.

[dbarbi1]

FYI, seems to be working well for me using only @999eagle's instructions.

• OS: Fedora 32beta
• CPU: AMD Ryzen 1800x
• GPU: AMD Vega 56

Seems to run well enough for me with fps in the 70 to 90s range. Settings are High at 1440 with a few other minor personal preference tweaks (lower motion blur, no vsync as i have freesync). I also disabled steam overlay and fps count as per some other comments though I did so on my first play so dont know what if any effect it had.

[jonlee836]

When the game launches it briefly appears as a really small window in the top left then stops launching.

I have a fully upgraded arch linux system with all dependencies mentioned above and enabled proton.

• GPU: nvidia 1050ti
• CPU: i7-9700K 3.60ghz
• 32g dd4

[zaggynl]

Upgraded to Ubuntu 20.04,
shuffled packages around where needed,
tried the non-GE build, at least I get DRM now:
"Currently your game purchase cannot be re-validated successfully, please wait 24 hours and try again." so I guess progress.

[Birdman7]

Upgraded to Ubuntu 20.04,
shuffled packages around where needed,
tried the non-GE build, at least I get DRM now:
"Currently your game purchase cannot be re-validated successfully, please wait 24 hours and try again." so I guess progress.

@zaggynl I'm practically in the same position as you. So it's good to know we're close to solving this conundrum. The only difference is that I used Proton-5.0-GE

[MasterCATZ]

it looks like if you hop between protons this will cause it trip DRM

999eagle's proton_tkg_5.4.r10.g7c7868f4
not clicking on the winetweaks menu and fresh install with amdpro
VK_ICD_FILENAMES=/pathtofile/amdvlkpro/amd_icd64.json STEAM_RUNTIME=1 steam

RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1

editing launcher.cfg to all 0

it seems to work , only issue is getting sound to go through the right sound card and popping / crackling sounds

and 1/4 the FPS I got in doom 2016

[Tk-Glitch]

Just for information, even though it's likely going to get burried (I'll count on the few seeing it to share if needed).

The PROTON_NVAPI_DISABLE option is unique to Proton-tkg and is NOT supported by GE or vanilla Proton. Trying to use it with those will have zero effect. The build @999eagle has uploaded being a Proton-tkg build, that one will be affected by the option.

Also, even if that option is known to fix other issues here and there (and create some here and there, too), I have changed Proton-tkg defaults to prevent the specific bad interaction that's been experienced by some (most?) Nvidia users.
That way, people building Proton-tkg from now on won't need to play with the internal option for it anymore to play Doom Eternal (the community patch isn't required anymore as well, btw, and building Proton-tkg as is with no edits is enough for a working Doom Eternal).

However that doesn't fix what seems to be a deeper issue that's specific to Nvidia.

On Nvidia, and Nvidia only, the game seemingly loads a huge amount of stuff into system memory, putting unusually high load on the PCI-E bus and ultimately leading to low perf with low GPU and CPU usage.

It's not the first game hitting this issue specifically on Nvidia GPUs (R6S and earlier versions of Grim Dawn are coming to mind). I would assume the faster your RAM/PCI-E bus, the less affected you will be, but you're unlikely to get the expected performance anyway.

[mozo78]

Can you technically explain this to NVIDIA developers?
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394
So now we can use Tkg without need to fiddle with nvapi?

[Tk-Glitch]

@mozo78 The linux drivers team has been made aware already.

Indeed, from now on you can build Proton-tkg as is to get a configuration that works for Doom Eternal. The problem is that it's not a universal fix and some games will selectively need nvapi explicitly disabled, but all the known cases are relying onto DXVK and thus can use a different approach that DXVK provides. For Vulkan native titles however, DXVK has no effect obviously and we don't have an easy way to bypass nvapi on a per case basis, that's why I changed the defaults. Best balance, I guess.

[jldez]

Updated to 20.04. But it was not smooth at all. Managed to fix most packages, however, nothing changed for me. Still got the same screen for the gpu driver. Still thinks I have 337.88.

[mozo78]

@mozo78 The linux drivers team has been made aware already.

Indeed, from now on you can build Proton-tkg as is to get a configuration that works for Doom Eternal. The problem is that it's not a universal fix and some games will selectively need nvapi explicitly disabled, but all the known cases are relying onto DXVK and thus can use a different approach that DXVK provides. For Vulkan native titles however, DXVK has no effect obviously and we don't have an easy way to bypass nvapi on a per case basis, that's why I changed the defaults. Best balance, I guess.

Thank you very much! I'll try it ASAP!
Did you tell NVIDIA for the problem? The doesn't seem aware of our bug report at all...

[brettalcox]

FYI, fixed my issue of mission always crashing by validating game files again. Steam found some issues and redownloaded them

[ReaperOfSouls1909]

no tkg proton doesnt work at all for me

[mozo78]

The latest Tkg doesn't work for me either :(
PreliminaryRenderSetup
...registered window class
Initialized stack tracer
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.

[Tk-Glitch]

And it worked with the earlier build 999eagle shared?
If it did, Josh's patch must be busted then and I'll rollback to my previous version that worked.

[dpanter]

Alright, replaced the 1080ti with my Radeon VII.
After forgetting to remove xorg.conf for a couple of minutes (doh!), I was soon up and running with the same specs as before apart from the new GPU of course.

Default amdgpu.ppfeaturemask: 0xffffbfff
xserver-xorg-video-amdgpu 19.1.0-1
mesa-vulkan-drivers 20.0.2-1 (LLVM 9.0.1)
amdvlk 2020.Q1.3
amdgpu-pro-19.50-967956-ubuntu-18.04

Performance with the same medium settings as before, but at 3440x1440 - at least twice as high. Triple digits all round.

Setting everything to max/Ultra Nightmare saw numbers coming down to a smidge above 50 during intense combat, no major dips, no stutter at all. I will probably tweak it a little or simply go down one preset level. Maybe update to mesa-git. Definitely undervolt again... but for a quick test... _dayym._

The Radeon VII is a god damn boss.

Screenshot with RADV - driver Mesa 20.0.2 - Vulkan 1.2.128 from the first room with the 3 zombies, 3440x1440 every setting maxed. Fps ranges from 60-120

Screenshot with AMDVLK - driver 2.0.137 - Vulkan 1.2.133 same room. Performance in general seems to be 5-10 fps higher than radv. Pretty much at 60 now in hectic battle.

Screenshot with AMDGPU-PRO - driver 2.0.122 - Vulkan 1.1.129 Couldn't really tell any difference from AMDVLK, seems very much the same performance.

These screenies are taken from Steam overlay by the way. Did I mention that ALT+TAB also works? _Nice._

Imgur Disabling Steam overlay sends the fps into orbit, this screenshot is with AMDGPU-PRO and almost 120 fps. Triple digits in combat anyone? _Unreal._

[wundrweapon]

@Tk-Glitch obviously I'm a different person, but the game stopped working with your build this morning. I haven't tested after this afternoon's update, but 999eagle's build worked both before and after it

[Tk-Glitch]

@wundrweapon Thanks for confirming. I'll get rid of the newer/broken patch then.

[UVCRocketRunner]

@Tk-Glitch Does this high memory load explain the crackly audio/stuttery performance?

EDIT: Also, should I switch to whatever you've built, or just keep playing with 999eagle's Proton build and wait for Nvidia or Valve to release an update?

[Tbird761]

The Radeon VII is a god damn boss.

Screenshot from the first room with the 3 zombies, 3440x1440 every setting maxed. Fps ranges from 60-120

I'd be interested to see what happens if you try the Vulkan driver from AMDGPU-PRO instead of using RADV/Mesa. (You can test it without formally installing the driver.)

[Tk-Glitch]

@UVCRocketRunner I haven't shared any prebuilt release yet, and I'll probably wait for Wine 5.5 to do so, but currently if you get the game to run with what you have, keep that setup for a while and enjoy the game if you get acceptable performance.
The Nvidia performance issues won't be fixed by switching Proton builds anyway, and it needs to be addressed either by Nvidia or by ID/Bethesda.

[dpanter]

I'd be interested to see what happens if you try the Vulkan driver from AMDGPU-PRO instead of using RADV/Mesa. (You can test it without formally installing the driver.)

Updated post with AMDVLK test, 5-10 fps faster than radv. :)

[Tbird761]

I'd be interested to see what happens if you try the Vulkan driver from AMDGPU-PRO instead of using RADV/Mesa. (You can test it without formally installing the driver.)

Updated post with AMDVLK test, 5-10 fps faster than radv. :)

That's interesting also. Some have said that the Vulkan driver extracted from the AMDGPU-PRO bundle behaves a bit differently (faster) than AMDVLK even. Would you be willing to test it? Like I said, it doesn't have to actually be installed.

If you're interested:

https://drivers.amd.com/drivers/linux/19.50/amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz

How to use it without installing anything:

tar xf amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz
cd amdgpu-pro-19.50-967956-ubuntu-18.04
mv vulkan-amdgpu-pro_19.50-967956_amd64.deb ..
cd ..
ar x vulkan-amdgpu-pro_19.50-967956_amd64.deb
tar xf data.tar.xz
cd opt
cp amdgpu-pro/ /opt/

You can just delete the "amdgpu-pro" folder from /opt after you're done if you don't want to keep it.

The launch argument would be:
VK_ICD_FILENAMES="/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json" %command%

[d3rhans]

There was an update to the game via steam just a moment ago. Since then I have a much improved performance, FPS is between 50 (very crowded outside places) and 100+ (indoor, few or no demos around) on 1920x1080 with medium settings. So I definetly reached playable :)

[digikin]

I just want to say, that this Linux community is awesome!

[mozo78]

And it worked with the earlier build 999eagle shared?
If it did, Josh's patch must be busted then and I'll rollback to my previous version that worked.

Yes, it is working with 999eagle's build :) When you remove the borked patch, will you left the nvapi setting? I'm eager to try it :)

[Birdman7]

I just want to say, that this Linux community is awesome!

Sharing the struggle is better than doing it alone. Here's to finding a quick universal fix I guess.

[wundrweapon]

As of today's game update, I'm now getting occasional crashes with no explanation. Game just went poof after an hour or two, twice

[MasterCATZ]

mean while that update got mine working

[dpanter]

Some have said that the Vulkan driver extracted from the AMDGPU-PRO bundle behaves a bit differently (faster) than AMDVLK even. Would you be willing to test it?

Thanks for the link and info, thought I had it installed but turns out I did not. Updated post above with AMDGPU-PRO screenie. Performance was very similar to AMDVLK, no easily distinguishable difference at least.

[Birdman7]

Seems we're getting close to a wide-spread solution, All I need now to ensure playability is for me to get a new GPU.
Oh and DRM Removal too.

[Tbird761]

Some have said that the Vulkan driver extracted from the AMDGPU-PRO bundle behaves a bit differently (faster) than AMDVLK even. Would you be willing to test it?

Thanks for the link and info, thought I had it installed but turns out I did not. Updated post above with AMDGPU-PRO screenie. Performance was very similar to AMDVLK, no easily distinguishable difference at least.

Thank you for testing that for me/us. =) I'm running a Radeon VII as well and eagerly await a Proton update that will let me start playing Doom Eternal. It looks like I can expect good performance.

[dpanter]

Thank you for testing that for me/us. =) I'm running a Radeon VII as well and eagerly await a Proton update that will let me start playing Doom Eternal. It looks like I can expect good performance.

Very nice! I think you'll like this then, I just ran some tests with Steam overlay disabled. We're talking triple digits, in combat. _Bro._

Updated post above with Steam overlay disabled screenshot.

[ashkitten]

i get consistently 30% higher fps with vulkan-amdgpu-pro than with radv or amdvlk on my rx5700. the the main issue for me is that vsync caps the framerate at 60 while my actual refresh rate is 144hz

[Phobos001]

I'm on Linux Mint 19.3
I have AMDGPU-PRO 19.50 with Proton 5.4 GE-2 and I get

"Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x000000014093f5bd)."

What should I do to fix this issue? Do I need to wait for a new Proton version? I can't use the TKG build because I can't download GLIBC or libc6 to fix the incorrect home folder error. Or am I missing something? Thank you for your time, I wish I could offer some help myself :(

steam-782330.log

[MacroHard-sys]

if someone could be so kind? I seem to be out of DRM hell, attempting brings up driver warning, but then crash after pressing play.

https://raw.githubusercontent.com/MacroHard-sys/proton-log/master/steam-782330.log

ubuntu 18.04, steam beta, nvidia 440 driver, 5.2ge

[parkerlreed]

@MacroHard-sys Use the tkg proton from 999 above. 5.4 GE 2 is crashing that exact same way for most of us here

[maarvw]

@parkerlreed doesn't seem to be possible with those specs unfortunately. I have essentially the same some my Linux Mint is based on Ubuntu 18.04 and haven't had any luck with any of the proton versions posted here

[MacroHard-sys]

now I get this:

======================
Proton: 1552061114 proton-tkg-5.4.r10.g7c7868f4
SteamGameId: 782330
Command: ['/home/n13/.steam/steam/steamapps/common/DOOMEternal/idTechLauncher.exe', '+com_skipIntroVideo', '1', '+com_skipKeyPressOnLoadScreens', '1']
Options: {'logcommandtoprefix', 'winetricks', 'winedxgi', 'nonvapi'}
======================
ERROR: ld.so: object '/home/n13/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/n13/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/n13/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: failed to initialize: /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/wine/ntdll.dll.so: cannot open shared object file: No such file or directory

Oh yea, I need 20.04?

[maarvw]

@MacroHard-sys now you're at the same problem you tried to help me with earlier :/

[GloriousEggroll]

I was able to replicate the crash on my latest build after wiping the prefix and testing on both my desktop and laptop. running some tests, will provide another update if denuvo doesn't lock me out.

[jldez]

I may be just me. But I would think twice before upgrading to 20.04. It was not a smooth upgrade at all and my gnome is very buggy right now. In the end, it did not fix anything for the game either.

[MasterCATZ]

mine worked as Ubuntu 19.10
but mine also did not try using sophie's git build dir

I guess mine knows of another location for missing files like ntdll.dll.so ?
maybe create a symlink to another proton lib folder ? , file defiantly is supplied

@MacroHard-sys , @Phobos001

something like
mkdir -p /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4
ln -s ~/.steam/root/compatibilitytools.d/proton_tkg_5.4.r10.g7c7868f4/dist/lib /home/sophie/projects/git/tkg-pkgbuilds/wine-tkg-git/proton_dist-5.4.r10.g7c7868f4/lib/

[FogLizard]

Today the game ran on Linux fine.
Tried single-player, getting about 30 fps in 4k with Vega 64 on almost full ultra-nightmare settings, with dynamic resolution enabled it bumps up to 50s.

Using Proton 5.4 GE-2, compiled latest mesa-git driver and steam beta-client

Specs:
4790k 4.6 GHz all cores OC + 4.4 GHz uncore OC
2200 MHz 32 GB DDR3 dual channel
Vega 64 ~1650 MHz GPU Core OC + 1045 MHz HBM2 OC
NVMe SSD

[Tk-Glitch]

@FogLizard You might want to give AMDGPU-PRO vulkan lib a go. It gives me a near locked 144fps experience @ 1440p ultra-nightmare with my 5700XT, which is a good chunk higher than what mesa gets.

[FogLizard]

@Tk-Glitch I've noticed that my game performance is bottlenecked by CPU actually, I've bumped the clock to 4.8 GHz and squeezed 5 more fps on average. I'd rather stick to my open source drivers, just a preference, but thanks for the advice. As long as it stays above 50, as it does now most of the time without significant drop of resolution, it's good enough.

[Tk-Glitch]

I wouldn't have thought that 4790K would be that limiting on such a game. Oh well. AMDVLK also reportedly gives much better results than RADV, similarly to DOOM 2016.

[SalmonSeasoning]

Followed @999eagle's instructions on Arch with KDE Plasma (Kernel Version: 5.5.10-arch1-1).

EDIT: I seem to have resolved this by removing the Proton error message check thingy from the Launch Options. Here is my new Launch Options: +in_terminal 1 +com_enableCrashHandler 2 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1 With this, Proton 5.0-5 still appeared to not work, Proton 5.4-GE2 actually froze the fuck out of Steam, and 999eagle's modified Proton package brought up the oh-so-great support page message.

Complete failure, did not launch AT ALL for me.
I tried the following Proton versions with varying success:

• Proton 5.0-5: The game would pop up the NVIDIA GPU warning, but would silently crash past that pop up. Only achieved the pop up by changing configuration file in the first place to show NVIDIA warning.
• Proton 5.4-GE2: Got past the standard NVIDIA GPU warning. Then got the warning that the NVIDIA GPU drivers were out of date. Clicked to play and it brought up a broken crash report menu.
• "proton_tkg_5.4.r10.g7c7868f4" from 999eagle: Broke everything. Immediately silently crashed and resulted in both of the other two versions of Proton to change their behavior and they now silently crash (at least as of this session) as well.

$ pacman -Q vulkan-icd-loader vulkan-headers nvidia wine-staging
vulkan-icd-loader 1.2.135-1
vulkan-headers 1:1.2.135-1
nvidia 440.64-5
wine-staging 5.4-1

Steam version of the game. It was touched a bit by previous patch attempts, but I verified the game files through Steam. I am opted in for Steam Beta. If you want logs, tell me where they would be stored. I've searched in DOOMEternal folder and I can't find anything but a super corrupted "LastCrashInfo.txt" which is attached.

LastCrashInfo.txt
sysinfo.txt

[ashkitten]

@Tk-Glitch do you also have the issue with vulkan-amdgpu-pro locking framerate to 60 with vsync enabled? is that only me?

[Tk-Glitch]

@ashkitten No such issue on my end, however I have some subtle tearing even with vsync enabled. But nope, vsync locks me to 144fps, which is correct for my 144Hz display.

[grand248]

Hey guys,
So i'm a Nividia user running Manjaro, proton_tkg_5.4.r10.g7c7868f4 and Steam beta and getting 20-30fps.
I noticed the game is running vulkan 1.1.119, but I have installed vulkan 1.2.135-1, I wonder why if this is why Nividia users are having performance issues, thoughts anyone?

pacman -Qs vulkan local/lib32-nvidia-440xx-utils 440.64-1 NVIDIA drivers utilities (32-bit) local/lib32-vulkan-icd-loader 1.2.135-1 Vulkan Installable Client Driver (ICD) Loader (32-bit) local/lib32-vulkan-intel 19.3.5-1 Intel's Vulkan mesa driver (32-bit) local/lib32-vulkan-radeon 19.3.5-1 Radeon's Vulkan mesa driver (32-bit) local/nvidia-440xx-utils 440.64-1 NVIDIA drivers utilities local/vulkan-headers 1:1.2.135-1 (vulkan-devel) Vulkan header files local/vulkan-icd-loader 1.2.135-1 Vulkan Installable Client Driver (ICD) Loader
Linux community is awesome btw!
Cheers

[silviucc]

Just a small side note. I would not read too much into the version of Vulkan that the game reports. For me, it shows the exact same version on Windows 10 and I have the driver version that the game otherwise recommends.

[Tk-Glitch]

@grand248 That is expected and can be safely ignored.

[ashkitten]

@ashkitten No such issue on my end, however I have some subtle tearing even with vsync enabled. But nope, vsync locks me to 144fps, which is correct for my 144Hz display.

are you using x11 or wayland?

[igo95862]

Could it be that Nvidia has some specific code path that does not work well with Linux driver? Can you hide that your gpu is Nvidia? I think DXVK does that.

[Tk-Glitch]

For Navi GPU users who would like to use RADV/LLVM (since ACO is missing the required storage_8bit / storage_16bit capabilities for now) instead of AMDGPU-PRO or AMDVLK, I have just made a patch/hack for mesa-git that will allow the game to run: https://github.com/Tk-Glitch/PKGBUILDS/blob/master/community-patches/mesa-git/gfx10_always_report_subgroup_shuffle_support.mymesapatch

[mozo78]

@Tk-Glitch
Did you reverted the borked patch already? Can we try Tkg again?

[Tk-Glitch]

Yes. I have tested the game myself to be sure this time.
edit: answering the post below -> yes. I invite you to read the commit log on my repo to lower the undesirable spam in here ;)

[mozo78]

And nvapi setting is still there?

[Ryhon0]

Proton-tkg 5.4.r10, steam-runtime beta and Nvidia 440.64-2 on Linux 5.5.8-1-MANJARO works fine but hangs whenever it loses focus (e.g. by alt-tabbing). Tested on GNOME and KDE Plasma

[Tk-Glitch]

@Ryhon0 Using windowed-fullscreen instead of the default fullscreen fixed that on my end on Plasma. The downside being that you can't minimize it, of course.

[igo95862]

For Navi GPU users who would like to use RADV/LLVM (since ACO is missing the required storage_8bit / storage_16bit capabilities for now) instead of AMDGPU-PRO or AMDVLK, I have just made a patch/hack for mesa-git that will allow the game run: https://github.com/Tk-Glitch/PKGBUILDS/blob/master/community-patches/mesa-git/gfx10_always_report_subgroup_shuffle_support.mymesapatch

Still crashes on my Navi. However, I am using GE proton. Should I use yours?

[e-user]

Finally got it to run on Fedora 31 Silverblue by switching to Steam native, as opposed to Flatpak. @999eagle's TKG Proton build gives me crackling sound, whereas Proton 5.4-GE-2 does not. Both versions however give me horrendous performance as seen on the screenshot. Contrary to what the screenshot states, the Vulkan Loader version in use is 1.2.131.1.
To get to those 30fps, I had to drop the resolution to 1280x720 and lower the quality settings to "Low" overall. I'm not even considering to play the game in this state and hope that newer Proton builds and/or NVidia drivers will resolve the performance issues which must clearly be driver related. Maybe as a side note, my GPU is accessed via Thunderbolt, i.e. it's an eGPU, but that hasn't caused any issues ever before.

Bottom line, this is the first time in my life I'm envying owners of AMD GPUs.

[Tk-Glitch]

@igo95862

Still crashes on my Navi. However, I am using GE proton. Should I use yours?

Some people have reported crashing issues with GE's build that didn't happen with the tkg build 999eagle has posted, so I guess it's worth a shot. I have no experience with the GE build (nor any intent to debug it 🐸 ) so I don't know what could be broken in there. At least I can attest the game works flawlessly on my end with a fresh proton-tkg build (either with AMDGPU-PRO or RADV/LLVM with the mesa patch above on a 5700XT).

@e-user It probably won't change much to your life to know it, but proton-tkg will use your system's FAudio libs, while GE ships its own. So if your distro provides old/broken FAudio, you might get sound issues on -tkg.

[Ryhon0]

@Ryhon0 Using windowed-fullscreen instead of the default fullscreen fixed that on my end on Plasma. The downside being that you can't minimize it, of course.

Sadly running in the windowed-fullscreen didn't fix the hanging for me. I've tried playing the campaign but the framerate is very low on my 1050Ti. I get 60fps in menus and tutorial rooms and 15-20fps in normal environments where as on Windows I get around 55fps

[e-user]

@e-user It probably won't change much to your life to know it, but proton-tkg will use your system's FAudio libs, while GE ships its own. So if your distro provides old/broken FAudio, you might get sound issues on -tkg.

I don't have any version of libFAudio installed on my system, right now. Are you sure this is related?

[Tk-Glitch]

Considering I experience zero crackling and the game definitely loads FAudio libs here, I would assume so. Maybe you get some weird fallback.

[MasterCATZ]

what was actually causing my login crashes was steam overlay turned on
big face-palm makes sense it died every time the steam logo popped up
proton_tkg_5.4.r10.g7c7868f4
it is running this sweet unsure whats changed in the last 12 hrs but my old r9 290's capped @ 60fps everything maxed , this morning it felt really laggy
just need to find a way to uncap its fps limiter ...

[mozo78]

@Tk-Glitch
The latest build of yours run without problems, thank you :)
Unfortunately your NVAPI setting doesn't change low performance in any way :(

[Tk-Glitch]

I have explained the issue previously and made myself pretty clear that even if the nvapi call is respected, the root problem is still there and is only fixable by either Nvidia or ID Software as far as our understanding of it goes.
Depending on your RAM speed/PCI-E gen/mobo topology/CPU combo, you might see a (pretty small) perf increase on the CPU front at best, but that's about it.

[mozo78]

Yes, I'm aware the problem is in NVIDIA driver but I hoped it will increase FPS a bit.
And my setup is pretty fast:
Intel 9900K
ASUS ROG STRIX Z390-E GAMING
ASUS GeForce GTX 1080 Ti
2x Kingston KHX3000C15/16GX (32GB)
And it makes no difference. All I get is 24 FPS :D

[Tk-Glitch]

Yeah you aren't CPU-limited in any way shape or form with that 9900K so that won't make a diff indeed. You could check the PCI-E bus load in nvidia-settings while the game is running, just for the lulz. Your average game will usually hit 2-4% usage, for comparison.

[mozo78]

I can't check it for the game will crash if I Alt+Tab. I may try to log nvidia-smi but it's really futile. We are waiting for NVIDIA to step in. It's sad there are no news from them. Even a post would be nice, but there's nothing from them :(

[Tk-Glitch]

It's only been a couple days. Give it a week or two.

[mozo78]

It's nothing left to do but waiting :)

[igo95862]

@Tk-Glitch I compiled your proton but my game still crashes.

Unhandled exception: divide by zero in 64-bit code (0x0000000141ec920c).

[Monsterovich]

@Tk-Glitch I compiled your proton but my game still crashes.

I have the same issue.

Unhandled exception: divide by zero in 64-bit code (0x00007f62aa74f06b).

[thedopefish]

After fiddling with stuff for a couple hours over the weekend, I finally got the game to run. A quick test shows 50-60fps on High settings. I'll give it some more playtime after work and see if any issues show up.

Intel Core i5-4670
NVIDIA GTX 970
Steam beta client

Ubuntu 18.04
kernel 5.0.0-23-generic
nvidia driver 440.66.03
Proton-5.4-GE-2

@ thedopefish

After fiddling with stuff for a couple hours over the weekend, I finally got the game to run. A quick test shows 50-60fps on High settings. I'll give it some more playtime after work and see if any issues show up.

Intel Core i5-4670
NVIDIA GTX 970
Steam beta client

Ubuntu 18.04
kernel 5.0.0-23-generic
nvidia driver 440.66.03
Proton-5.4-GE-2

What did you do to have the game run ?