The game starts, opens the system tray of wine, then closes abruptly.
Doom Eternal not starting
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3655.
@APoniatowski posted on 2020-03-20T00:48:54:
soon...
Game crashes on start
-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?
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.
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.
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
nope... missing executable (idtechlauncher.exe). last ditch effort now is reinstalling the game
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.
aaah, figured.
However, I did run it with proton, before trying the compatibility tool. still crashed unfortunately
Is there a file called DOOMEternalx64vk.exe?
@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.
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 :(
@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."
@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
@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.
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.
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.
@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?
@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
@gardotd426 regou're right, so here goes:
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
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
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
The game uses Vulkan, so wined3d/dxvk makes absolutely no difference whatsoever.
FWIW I am using an AMD card.
tried WINED3D
now... same result, unfortunately.
@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?
I'm experiencing the exact same symptoms on AMD hardware.
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
@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.
@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.
@doitsujin lol it's always something, isn't it. Hopefully that will fix it once you get it figured out.
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:
``` Adding process 27762 for game ID 782330Terminal spew
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.
´´´
@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.
@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.
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.
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
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]
Here is my log as well. Same issues mentioned above.
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.
Same issue as all the others:
GPU: AMD RX480
Driver: AMDGPU-Pro-19.50-967956
Vulkan Instance Version: 1.2.131
Kernel: 4.15.0-91 (Linux Mint 19.3)
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.
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
I get this message when starting the game using Proton 3.16-9
Log when forcing proton 5.0-4: 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
Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.
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?
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
Out of curiosity, which version of the NVIDIA driver do you have installed?
440.64-0ubuntu0~0.18.04.2
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.
Steam log on proton-5.4.GE-1, i am using:
elementary OS 5.0
GPU: gtx 1050ti driver 440.64
steam-782330.log
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
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
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:
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
I have the exact same issues with the bethesdalauncher version and lutris.
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:
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?
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?
Crash reports are enabled with +com_enableCrashHandler 2
is there any way of bypassing the launcher and run the actual executable/binary?
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)
Just tried 440.66.03, it doesn't change anything.
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.
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.
https://www.vg247.com/2020/03/20/doom-eternal-denuvo-free-exe/
We need to try use this leaked executable file.
Same as above but with the Denuvo-free binary, see my previous comment.
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
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.
@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 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 theseh: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
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!
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 notifications@github.com 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
moduleFull log:
steam-782330.log
https://github.com/ValveSoftware/Proton/files/4359487/steam-782330.logI 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
.
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
@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.
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.
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...
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.
@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.
@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.
additional steps taken:
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
@Guy1524
Can you fix it like MK11 :)
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
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.
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 notifications@github.com 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 MemoryidLib::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
.
ran what @rkfg did with +in_terminal 1
, log looks bigger now.
steam-782330.log
@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.
Finally some good news. Hope this doesn't take long to solve.
@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.
But VK_KHR_get_surface_capabilities2
is present in all drivers already. It's there for Mesa too.
Not as far as Wine is aware, is the issue.
On Fri, Mar 20, 2020 at 10:55 AM mozo78 notifications@github.com 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
.
@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
Ah, I see. Thanks :)
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.
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
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?
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.
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.
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?
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.
The PR is for Valve's wine fork, not proton, though...?
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
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.
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?
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.
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).
@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.
@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.
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.
@pastapojken I'm using Arch Linux, i compiled the latest vulkan-icd-loader manually.
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.
So, do we need vulkan-icd-loader 1.2.135 installed or patched Proton will suffice?
@mozo78 you'll need the latest loader/headers installed, presumably for added features that the game makes use of
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
Thank you. It gets harder and harder...
@Kron4ek have you tried running the game with +com_skipSignInManager 1
in Steam launch options?
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
Better use :
+com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
So, do we need vulkan-icd-loader 1.2.135 installed or patched Proton will suffice?
need to use vulkan-icd-loader & patch
@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.
Im speak for launch without steam-runtime im not use this.
@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 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.
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.
@Kron4ek good video :D
@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
.
@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.
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 notifications@github.com 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
.
can someone link me to vulkan-icd-loader aur
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
@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.
sudo pacman -S nvidia nvidia-utils lib32-nvidia-utils nvidia-settings vulkan-icd-loader lib32-vulkan-icd-loader
wrong version numbers that way
Vulkan-icd-loader-1.2.135-PKGBUILD.zip
found one
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
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
ok
same problem, any quick way to run this?
you need last vulkan-icd-loader
pacman -S vulkan-icd-loader
?
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.
pacman -S vulkan-icd-loader
?
no use this pkgbuild
Vulkan-icd-loader-1.2.135-PKGBUILD.zip
@Niedzwiedzw no, that doesn't give an up-to-date enough version.
You have to download the zip above
@werman how did you get it to run?
oh is not authorized to share wine tkg ? @ValveSoftware
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.
ok im make version without that
@gardotd426 At what step do you have issues?
Someone needs to clearly explain how to get it to run, this thread is an absolute mess right now.
@werman:
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.
@ReaperOfSouls1909 how do i do that? :O
@Niedzwiedzw
https://wiki.archlinux.org/index.php/Makepkg
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
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.
have some error in your pkgfile @ReaperOfSouls1909 better share compiled version
@liberodark, taking a look at the wine build you shared, it contain a legally problematic workaround and and has been removed.
not my script @oscarcp made it if there is an error im not the one to go to
but no have share any files bad or illegal juste is tkg have better solution.
Im go to make pure wine version @kisak-valve
Had to disable ACO for Vulkan 1.2.135 to be used.
Otherwise the game runs great after all the workarounds.
@kisak-valve have updated the link look is only wine tkg pre compiled with a patch for doom
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?
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:
sed -i 's/vkAcquireFullScreenExclusiveModeEXT/vkGetImageSparseMemoryRequirements2/g' DOOMEternalx64vk.exe
sed -i 's/VK_EXT_full_screen_exclusive/VK_EXT_shader_stencil_export/g' DOOMEternalx64vk.exe
As i said before, the game often crashes or hangs before entering the main menu, so multiple game restarts may be required.
@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?
The pre compiled version of wine is here : https://drive.google.com/file/d/1_pPRwztcq_Vp6IKGAXo-XIrnicizZqlk/view?usp=sharing only wine
@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?
The DRM free version, you need the tkg patch to get it to work.
i will compile wine-tkg with that patch and upload the install file for arch
precompiled version for arch : https://drive.google.com/open?id=1Gvvq5rxvSZmeLOaZZeGcm95FBT9mtOrq
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?
no just need to wait for drm when the pr is merge is ok
@gardotd426: unknown at this time. I don't think anyone has gotten far enough yet with the drm version of the game.
i'm still working on getting the incredibly janky proton build process to work so i can build with patches from that pr
but bethesda launcher is other probable issue
Probably just rename files ?
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.
@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.
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.
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.
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.
@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:
@wundrweapon I wasn't able to launch game with Mesa, but I didn't really tried
@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?
But need vulkan-headers 1.2.135 too @ReaperOfSouls1909 you have this in pre compiled ?
@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.
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.
@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.
OK HAVE FOUND BETTER SOLUTION :D
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!
@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)
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.
@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
@kisak-valve, that makes much more sense, thank you for the clarification.
@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.
im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharing
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?
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
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?
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
Yes but what did you do to get it to compile with VK_EXT_full_screen_exclusive support?
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?
Yeah use this version make a backup of your proton version.
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?
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
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.
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
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?
@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
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?
@annmuor vulkan-icd-loader from the Arch repos is not new enough, 1.2.135 version is required.
yeah you need : 1.2.135
@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
You'll also need a version of Proton with my VK_KHR_get_surface_capabilities2 + VK_EXT_full_screen_exclusive patches.
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
@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.
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
@Kron4ek You'll need to run make_vulkan
in dlls/winevulkan
before building
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[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
no need headers run the game in headers 1.2.332
no have found the 1.2.335 :(
@Joshua-Ashton Thank you, i didn't know that this is required.
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 .. :(
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.
ah so sorry :( @dylanmc1975
How do I make make_vulkan
happen in @Tk-Glitch proton-tkg build?
@liberodark Unfortunatly gentoo is not too reactive, I have to hope in valve I think
You rocks guys Thank You !!
I have the same issues as @annmuor I build the required vulkan-icd-loader and tried @liberodark wine bottle and still get the crashes..
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
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
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
Still haven't gotten anywhere since this
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.
@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.
Update here i used @liberodark wine as a new runner in Lutris and now it works. Thanks everyone.
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 :)
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
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
@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.
Does anyone know how to run a Steam game using the system's wine instead of Proton?
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.
@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.
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.
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!
@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.
After finally getting the DRM-version not to crash I got a nice greeting from Denuvo.
Refund it is.
@Voxed what'd you do to get that far?
@PraetorianSC4 I have the same. I didnt change anything, just upgrade beta steam. And get this shit from Denuvo
@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
@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.
@Voxed: radeon gpu yeah? Unlikely to work for me, nvidia card over here.
I've already done all of the following:
No luck thus far. Majorly disappointing.
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 ¯\_(ツ)_/¯
@AllKind Denuvo doesnt want you to have fun, you could always try to get the drm free version.
@Voxed , but It's a purchased version on Windows from steam???
@AllKind this is the wrong place for this conversation. Either wait 24 hours or get a refund.
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...
yes @mozo78 is not pretty good and im on nvidia
Better without hdr and vsync
Yes, now it's 24 :D
im send you better wine release work not need to patch the exe :D
https://drive.google.com/file/d/197kenSrONBQJvdo4Jd8YSTdOn4f5Bv5T/view?usp=sharingThis 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
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:
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.
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.
Yeah, the improvement that is required is actually to Proton/Wine's libvulkan shim.
Finally I got it running, hell yeah. Have an issue with alt-tabing but who cares.
So, overall, a quick instruction for steam users.
Thanks all who made it working!
Yeah but doom eternal with Vulkan is pretty bad perf on wine without dxvk too
dont have test without esync...
@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.
Yeah but doom eternal with Vulkan is pretty bad perf on wine without dxvk too
DXVK is unrelated.
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 ...
doom eternal released an update... still the same though. don't know how the patch would affect all the work done so far
@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...
We're all in the same boat of bad performance, correct? No one's has any better luck?
need to compare AMD and NVIDIA no idea for me is on 60 and 25 fps
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.
you have aco ?
Had to disable aco for vulkan 1.2.135 to be used.
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.
is there any way to see the terminal output from the game when launching from steam?
for need to wait update from game / vulkan & proton / wine
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?
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
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
@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?
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:
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)
anyone who has it working, can you give your system info please?
i have not been able to get it working, with:
Hi guys,
Can someone please explain how to get the latest vulkan in Manjaro.
Thank you in advance.
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?
@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
@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
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):
@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.
I didn't even get that image when I ran on the Denubloat exe, it just crashed
@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)
@ashkitten yeah that link opens up the page I've posted
@wundrweapon probably related to vulkan versions, can you post your log?
@rabidlassie which log is that and where would I find it
@wundrweapon there you go: https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-601503268
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?
@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%
so the current status is it works, but denuvo always trips?
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.
Also I had an update, Steam's Proton version got bumped up to 5.0-5. Still throws DRM error though :(
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?
can you post your log?
Yikes, over 500k lines o_O
A direct search for vulkan only results in some SOs successfully loading
nbd if you use a pastebin
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.
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?
consider throwing it in an archive.
Why didn't I think of that? Here's the archive
log.zip
Here's my log now with Proton 5.0.5. Much smaller than that of @wundrweapon
steam-782330.log
Oh, yes, I suppose I might as well throw up the log with Proton 5.0.5 for completion's sake.
steam-782330.log
@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.
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.
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.
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.
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.
@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.
@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
@Vladimir-A you have nofsync on, perhaps that is the issue?
@wundrweapon @ryester27 you both have stack overflow, not sure what causes this.
@rabidlassie I tried launch with fsync and without fsync, for example From Software games don't works with fsync. Same logs.
I don't understand how the Proton team didn't pre-test such a big title game?
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.
Here's to hoping they will drop Denuvo soon like with Rage 2. Especially since the game came cracked out of the box.
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
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.
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
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.
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.
Yeah, uh, we know
Arch received vulkan-icd-loader 1.2.135-1 officially last night. There's no more need to compile it :)
Is the DRM-free .exe still needed with Proton 5.0-5 and vulkan-icd-loader 1.2.135-1 on Arch?
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 notifications@github.com 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
.
Yes, it's needed :)
@Kron4ek
The Proton builld on your GitHub page is still 5.0-4. The game crashes with it.
@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.
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 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
@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
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?
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?
Am trying on Arch Linux, beta steam (tried both runtime and native), vulkan-icd-loader
1.2.135
and nvidia440.64
on a GTX 1080 Ti, trying proton5.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.
@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.
@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
@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.
I have same hashes also @C0rn3j
@wiltaylor Tried launching with just the EXE changed(kept the current launcher), no change, still crashes.
Tried a clean prefix for good measure(rm -rf ~/.local/share/Steam/steamapps/compatdata/782330/pfx
), didn't help.
+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 :)
@mozo78 no problem :)
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
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.
@999eagle and anyone else who managed to make it work: ProtonDB reports are very welcome: https://www.protondb.com/app/782330
@McMarius11 will do
@tuxayo yup, I'll add my report
@McMarius11 uploaded and edited my comment with the binary.
@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?
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
@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
@FTL-Space-Warp
~/.steam/root/compatibilitytools.d/
+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
Proton-tkg 5.4.r10.g7c7868f4
as the Proton version to use for DOOM EternalHopefully 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.
@999eagle Danke, küsse deine Augen!
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.
@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
@FTL-Space-Warp
- Download the Proton version I uploaded (https://ufile.io/x58gs3ia or https://uploadfiles.io/x58gs3ia), unpack to
~/.steam/root/compatibilitytools.d/
- Make sure you're opted in to the Steam client beta (Steam > Settings > Account > Beta participation)
- Restart Steam
- Add these launch options to DOOM Eternal in Steam:
+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
- Choose
Proton-tkg 5.4.r10.g7c7868f4
as the Proton version to use for DOOM Eternal- 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
@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.
@dylanmc1975 I'm using vulkan-icd-loader 1.2.135
, but the Steam beta should include that
@kdwinter I use ubuntu 19.04 with steamvr mesa drivers and an rx580 and so far the game works.
@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:
Libraries I installed (you might not need them, I put them here for completion, steam runtime should have some of them already)
@dylanmc1975 I'm using
vulkan-icd-loader 1.2.135
, but the Steam beta should include that
I hope, gentoo doesn't :)
@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 ?
@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%
@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.
@zaggynl @999eagle I have the same issue with the /home/sophie/
path.
The compatibilitytools folder is at ~/.steam/steam/compatibilitytools.d/
for me though.
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.
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?)
/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?
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.
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.
@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.
@999eagle 's proton version crashes for me on Pop_os the same as it always did.
steam-782330.log
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.
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 ?
My bad, turns out my globally set WINEDEBUG=-all envvar (for when I run other stuff with wine) prevents the logs from working.
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 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.
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.
@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.
@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.
@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.
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 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!
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)
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.
`
I followed 999eagle's instructions (I am on arch) and the steam version of the game works, but runs very poorly (15-25 fps).
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
@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/
seems like we shall have to wait for another stable release to enjoy this master piece.
@oscarcp Yeah I figured the patches do have an impact on performance. Good job so far everyone involved!
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 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.
@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
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.
@APoniatowski by 100% you mean that you have no performance issues?
gotta love when people use slow sites for downloads
@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.
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 ?
@999eagle Did you use the DRM-free version ?
https://drive.google.com/file/d/1pXLZLXaOTDwhP2T-8043De059yr7xxEc/view?usp=sharing protontkg arch install pkg
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.
@elovin No, I'm just using the default unmodified Steam version
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...
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.
4790k 1070 here custom pds kernel 5.6 newest and 100+ FPS maxes out 1080p
@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)?
gotta love when people use slow sites for downloads
4790k 1070 here custom pds kernel 5.6 newest and 100+ FPS maxes out 1080p
It's because of pds kernel may be?
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 notifications@github.com 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.
@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.
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
@gardotd426 thanks I'll check that out.
@MuchiMuchiPink make sure you direct the game to use that vulkan driver with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json
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.
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
@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.
@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.
@gardotd426 no, i don't play through the launcher. I just start the DOOMEternalx64vk.exe with a 64bit wineprefix, but thanks :)
@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).
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
@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.
Just for the record, @zaggynl 's mirror matches the original file of @999eagle
( https://zaggy.nl/nextcloud/s/W96Z7BBy6oirJpY )
md5sum: feec62ea77baa5b37bbe6f92946a42ea
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.
@VincentGuinaudeau I've put PROTON_LOG=1 %command%
on launch options, but I have no fatal errors in the steamlog
use PROTON_LOG=1 %command% +in_terminal 1
@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
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 :/
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.
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.
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!
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.
@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 ?
Anyone got it working on Ubuntu 18.04 yet?
Anyone got it working on Ubuntu 18.04 yet?
I did not ...
@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
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
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.
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.
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...
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
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.
1080Ti - 24 FPS on Low settings :D :D :D
@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.
@dylanmc1975 doom 2016 still has opengl apis, while Eternal is exlusively vulkan
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?
@999eagle
Are you able to share the patches for proton so we can compile ourselves?
@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.
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.
@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).
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.
@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.
@999eagle Thanks!
@999eagle For the record though it works with your patches on gentoo with GLIBC 2.30
:man_shrugging:
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.
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 :)
Hello @ashkitten, my understanding is that the state needs to reset on some Denuvo server.
can anyone confirm that proton 5.0-5 works?
@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
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.
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.
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.
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:
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?
@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
@999eagle You build works for me (kind off)
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!
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
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 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 insideDOOMEternal/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
@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.
Hello @Berinth, try using an absolute path (/home/username
) instead of ~
.
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.
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
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
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
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.
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
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.
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)
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
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.
In this tred a user complains with GTX970 too as I recall.
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
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
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.
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
@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)
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 :)
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
Some video or screenshots are welcome :)
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?
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
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...
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.
@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
Do we have any idea why nvidia users are getting lower performance? That's the idea I'm getting so far...
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?
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
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?
@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 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.
@boehmseb
Thanks for you efforts but this didn't help me too :(
@poke86 you're going to have the same problems as others using Ubuntu, so look through this thread for Ubuntu fixes
@999eagle
I am using ubuntu 19.10 , as far as I know everything is up to date
it dies after it prompts for winetricks
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)
vulkan is old, you need to update manually
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.
@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.
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 ...
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.
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
)
@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
I cannot get any reasonable performance from DOOM, tried 4 different wines, updated everything and disable nvapi...
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
@dylanmc1975 can you add your steam system info?
@dylanmc1975 +1, please add vulkan\os info
@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....
Any ubuntu ppa for vulkan 1.2 btw? Can't find any =(
Another reason why to go team red
@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?
@UVCRocketRunner
....wat? follow 999eagle's instructions, but make the directory yourself and extract the tar there. it works fine, aside from perf issues.
@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
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.
EDIT: Sorry for photo rotations :(
Using "Low" preset:
Using "Ultra-Nightmare" preset:
@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.
@brettalcox enable debug info in doom, settings, video
@MagicRB says it's using 1.1.119
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
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
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
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,
vulkaninfo says i've got 1.1.119, i'll double check my setup
wait, my api version is 1.1.119
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!
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
@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?
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:
@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
.
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
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
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",
@ReaperOfSouls1909 can you post your system info?
@gblanchard didn't work for me. Can you post your system info as well?
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 notifications@github.com 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.
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.
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.
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.
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.
@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?
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.
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2
go kill the thingies.
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?
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.
@tizzir I have compiled a custom kernel with PDS and still had the same results. My previous kernel was 5.4.24-1.
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
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.
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.
@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
@GloriousEggroll
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
Crashes shortly after the AMD no support HDR splash
RADV_PERFTEST=llvm PROTON_LOG=1 %command%
Using the new GE version from @GloriousEggroll
vulkan-icd-loader 1.2.135-1
mesa-aco-git 20.0.0.20200226.7a965bd4c38-7
Is it possible the Denuvo exe is causing this? The Steam version doesnt have the other version that Bethesda left in there.
mesa-git 1:20.1.0_devel.121420.500842399a3-1
vulkan-radeon-git 1:20.1.0_devel.121420.500842399a3-1
Tried the DRM free exe from Bethesda and got farther to a black screen but still crashes :/
@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.
@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.
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 ?
@jldez 442.74 is for Windows, its Linux counterpart is 440.66.03. You can get the driver here.
Steam runtime should already use any system libraries that are newer.
@MasterCATZ Why preload a 32bit lib for a 64bit game?
because the elf errors in the logs were driving me nuts
@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
I was using the idTechLauncher.exe that time it then launches that
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
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
Check to make sure you have the latest driver. Mesa 20.1 git. That seems to be a hard requirement.
vulkaninfo | grep -i 8bit
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
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
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
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))
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?
Is it your first attempt? You may have to just get it to crash/kill it, then just try again, like I did.
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
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
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.
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 :)
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
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
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".
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
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.
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.
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.
Controller input is messed up. Sticks behave randomly.
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/116394This 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.
Trying the custom Proton and removing the line "PROTON_NVAPI_DISABLE": "1",
the performance is not good :(
All AMD users have good performance
I'm pretty sure it's not launching for the majority of us.
Also for everyone that has gotten it to work, are you using the Denuvo exe or not?
Also for everyone that has gotten it to work, are you using the Denuvo exe or not?
Steam unmodified version.
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).
Random hangs with mesa radv git.
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.
@xDShot
Random hangs with mesa radv git.
Try closed source admgpu-pro vulkan driver - it didn't hang in several hours of gameplay.
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.logSteam Runtime
steam-782330.logSystem
system.txtSeems 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?
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.
@TimoFreiberg RX 480 and yes I am trying the 5.4 GE 2
@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.
That was just an attempt at anything working. Same result without it
I get the AMD HDR not supported and then nothing else. Crashes.
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?
@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).
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.
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.
@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
@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.
@TimoFreiberg I mean I wasn't going to worry about disabling the popup until I can figure out why it's crashing.
@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.
I assume try this version? https://github.com/Tk-Glitch/PKGBUILDS/releases/tag/5.4.r0.g676dd026
@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.
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.
We have life with the tkg build from above. Currently testing the Mesa git RADv and will see how that goes.
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.
Confirmed working on my end with the Steam / Denuvo version with following setup:
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2
Follow standard procedure to integrate with Steam runtime:
Purchase + Download the game if not done already
Select "Proton-5.4-GE-2" in the Steam per game settings for DoomEternal
⚠️⚠️⚠️ 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%
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. :
@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
@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.
@Bleuzen Need more confirmation but I think the DRM free exe no longer works with the current game update. Crashes for me aswell.
@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 insideDOOMEternal/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.
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?
@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
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.
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.
@tizzir I'll look into that, thanks.
Alright!
Game is running, been testing a bit now that my Denuvo 24 hour timeout is over. _Thanks Denuvo, I love you too._
Nvidia settings:
Doom Eternal tweaks
PROTON_NVAPI_DISABLE
1 or 0, no effect on fps+com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
(not needed)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.
@dpanter Any tips for not tripping Denuvo? Got in yesterday only to get instantly locked out again.
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.
The different Wine/Proton versions are triggering Denuvo. Keep it in mind.
I tried the custom Proton version from @999eagle and the launcher option and that works!
OS: Pop!_OS 19.10
GPU: AMD RX 580
Thought it was corrupted save file, but 2nd save also crashes every time Mission #2 starts loading
Anyone know if an official Proton beta update is coming from Valve some time soon? I'm not comfortable running binaries from unofficial sources.
Denuvo doesn't like Wine Staging, which proton-ge is based on, so if you want to avoid tripping Denuvo stick to normal Proton
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.
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?
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.
@jldez
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
There it's two commands to install it and then a reboot.
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...
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?
@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
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.
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.
@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
@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 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.
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.
alright, I'll try it. Last I heard version 2.31 was required though? that link is for 2.30
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.
Almost nothing I've tried on this board worked. Time to pirate Windows 10.
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?
@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.
@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!
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
rebootHowever, 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.
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.
I can confirm that on Ubuntu 20.04 will work.
Nvidia Driver: 440.66.03
VulkanInfo: Vulkan Instance Version: 1.2.131
~/.steam/root/compatibilitytools.d/
Steam>Setting>Account>Beta participation
Steam>Settings>Steam Play>Enable Steam Play/Run other titles with
Library>Doom>Settings(Gear Icon)>Properties>Set Launch Options
+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
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
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?
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!!
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
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?
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
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
@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.
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).
Tried Proton GE (doesn't launch), tried compiling TKG build, tried disabling fps counter and overlay too. No change in fps at all.
I tested some more, here is the state of things:
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)
@d3rhans So basically, Team Red have better luck in this case than Team Green? Just feeling around for things to note.
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...
@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.
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:
All unconfirmed but I was able to avoid getting sent to Denuvo hell for a third time.
FYI, seems to be working well for me using only @999eagle's instructions.
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.
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.
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.
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
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
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.
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?
@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.
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 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...
FYI, fixed my issue of mission always crashing by validating game files again. Steam found some issues and redownloaded them
no tkg proton doesnt work at all for me
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.
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.
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._
@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
@wundrweapon Thanks for confirming. I'll get rid of the newer/broken patch then.
@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?
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.)
@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.
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. :)
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%
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 :)
I just want to say, that this Linux community is awesome!
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 :)
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.
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
mean while that update got mine working
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.
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.
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.
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.
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
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 :(
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
@MacroHard-sys Use the tkg proton from 999 above. 5.4 GE 2 is crashing that exact same way for most of us here
@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
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?
@MacroHard-sys now you're at the same problem you tried to help me with earlier :/
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.
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.
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/
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
@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.
@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.
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.
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:
$ 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.
@Tk-Glitch do you also have the issue with vulkan-amdgpu-pro locking framerate to 60 with vsync enabled? is that only me?
@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.
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
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.
@grand248 That is expected and can be safely ignored.
@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?
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.
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
@Tk-Glitch
Did you reverted the borked patch already? Can we try Tkg again?
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 ;)
And nvapi setting is still there?
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
@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.
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?
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.
@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 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 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?
Considering I experience zero crackling and the game definitely loads FAudio libs here, I would assume so. Maybe you get some weird fallback.
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 ...
@Tk-Glitch
The latest build of yours run without problems, thank you :)
Unfortunately your NVAPI setting doesn't change low performance in any way :(
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.
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
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.
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 :(
It's only been a couple days. Give it a week or two.
It's nothing left to do but waiting :)
@Tk-Glitch I compiled your proton but my game still crashes.
Unhandled exception: divide by zero in 64-bit code (0x0000000141ec920c).
@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).
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 clientUbuntu 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 ?
@aleksbenmaza The last step that got it working was switching from Proton-5.0-5 to Proton-5.4-GE-2.
I'm running the unmodified Steam version of the game. It does give me the spurious warning message about out of date NVIDIA drivers on startup, but I just click past that and the in-game overlay shows the correct version.
I tried again with @999eagle's build, It worked! All I need now is a new GPU and some other tips to help iron out the other teething problems this game has running under Proton.
EDIT: Launched again, stuck in an infinite black screen. yay.
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 clientUbuntu 18.04
kernel 5.0.0-23-generic
nvidia driver 440.66.03
Proton-5.4-GE-2
Did you by any chance stay at the same begining of the level? There we all poor NVIDIA users are getting 60 FPS. Make some steps forward.
@aleksbenmaza The last step that got it working was switching from Proton-5.0-5 to Proton-5.4-GE-2.
I'm running the unmodified Steam version of the game. It does give me the spurious warning message about out of date NVIDIA drivers on startup, but I just click past that and the in-game overlay shows the correct version.
UH HUH. NOW. Tell me all the steps you took before please!!!!!
the error I run into with the steam version and GE-2 is
ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
(from the log)
how can that be fixed?
the error I run into with the steam version and GE-2 is
ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
(from the log)how can that be fixed?
You can just ignore that particular error message. You'll see that with virtually all Steam games if you're watching the console. It's an error about Steam's overlay, not the game. It's non-fatal.
the error I run into with the steam version and GE-2 is
ERROR: ld.so: object '/home/marvin/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
(from the log)
how can that be fixed?You can just ignore that particular error message. You'll see that with virtually all Steam games if you're watching the console. It's an error about Steam's overlay, not the game. It's non-fatal.
i disabled steam overlay for this test after i read it caused issues in some cases. could it be unrelated?
@mozo78 This was in an outdoor area shortly after completing level 1.
@MacroHard-sys Steps I took that definitely did not help were trying the non-Denuvo .exe, and attempting to launch proton from the command-line. Steps I took that may or may not have helped include switching to the beta Steam client, disabling the Steam overlay for the game, and upgrading from NVIDIA driver 440.64 to 440.66.03.
@mozo78 This was in an outdoor area shortly after completing level 1.
@MacroHard-sys Steps I took that definitely did not help were trying the non-Denuvo .exe, and attempting to launch proton from the command-line. Steps I took that may or may not have helped include switching to the beta Steam client, disabling the Steam overlay for the game, and upgrading from NVIDIA driver 440.64 to 440.66.03.
can't find that driver broy. link it up? Edit: Found it found it.
anybody have any idea why my doom eternal doesnt launch?
im using mesa-git
im using proton-ge-custom 5.4-ge-2
im using the steam client beta
ive disabled aco for this game
what did i miss here?
sysinfo and proton log:
https://gist.github.com/mathew2214/e927b5db0da74544134bf987ab28cf9d
this seems to be where it crashes
813.843:0038:0039: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:
Steam system info: https://gist.githubusercontent.com/zaggynl/19d6a81cd78c88066c7be8f132e63a3e/raw/51cf2ba54ad6cedea97c5648222216beb38ba0c2/gistfile1.txt
Proton log: https://gist.githubusercontent.com/zaggynl/028a7174d613123237b13a60794a728b/raw/bbae23a21f95d3d902d8c6c857d2721abeb8b3f0/gistfile1.txt
summary:
ubuntu 20.04
mesa-git via oibaf ppa
using proton 5.4 ge-2
steam beta
rx5700
launch options used:
RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager
Edit:
Official Proton 5.05 leaves a 50MB log, zipped:
steam-782330-zaggynl.log.zip
I think its something Navi related. There is a patch couple posts up but it did not seem to help me.
There is also some work going on in mesa upstream: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ac8bb33cd6025f805a390e7647506e932f4db0d
I was able to get the game working on Mesa and I have played about ~5 hours over the weekend without crashing. The performance is fantastic on an RX5700 XT. There are slight artifacts. It isn't enough to make the game unplayable, but amdvlk may provide a better experience.
I build a custom version of proton, by following the steps outlined here:
https://github.com/Tk-Glitch/PKGBUILDS/tree/master/proton-tkg
A community patch is needed to get everything working, so you need to add winevulkan_fshack_opts.mypatch
to PKGBUILDS/wine-tkg-git/customization.cfg
before building proton.
I cannot get Mesa 20 to work only 19:
lib32-llvm 9.0.1-1
lib32-llvm-libs 9.0.1-1
lib32-mesa 19.3.4-3
lib32-vulkan-icd-loader 1.2.135-1
lib32-vulkan-radeon 19.3.4-3
llvm 9.0.1-2
llvm-libs 9.0.1-2
mesa 19.3.4-2
mesa-demos 8.4.0-2
vulkan-icd-loader 1.2.135-1
vulkan-radeon 19.3.4-2
vulkan-tools 1.2.135-1
xf86-video-amdgpu 19.1.0-1
System:
Arch Linux x86_64 5.5.10-arch1-1
tried it with the mesa commit mentioned in https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-602687860
no change in game's behavior. still crashes with
Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x000000014093f5bd).
92.563:004f:0050:fixme:dbghelp:elf_search_auxv can't find symbol in module
As @bnpfeife commented, can confirm slight graphical glitches on textures (most notably the hud) with RX Vega 64/amdgpu-pro aswell.
Not horrible but worth noting:
@mathew2214 I experienced that exact issue with GE-2, TkG-r10 works fine though.
Where is everyone getting Proton 5.4? I have enabled Beta support on Steam and I'm not seeing that Proton version listed, only Proton 5.0 and below.
@thedopefish
@mozo78 This was in an outdoor area shortly after completing level 1.
@MacroHard-sys Steps I took that definitely did not help were trying the non-Denuvo .exe, and attempting to launch proton from the command-line. Steps I took that may or may not have helped include switching to the beta Steam client, disabling the Steam overlay for the game, and upgrading from NVIDIA driver 440.64 to 440.66.03.
I assume that your didn't install your drivers from PPA ?
@Voxed can you please upload the Proton archive file you had success with?
@thedopefish
@mozo78 This was in an outdoor area shortly after completing level 1.
@MacroHard-sys Steps I took that definitely did not help were trying the non-Denuvo .exe, and attempting to launch proton from the command-line. Steps I took that may or may not have helped include switching to the beta Steam client, disabling the Steam overlay for the game, and upgrading from NVIDIA driver 440.64 to 440.66.03.I assume that your didn't install your drivers from PPA ?
That's correct. I apt source
'd the 440.64 package from the PPA, then downloaded the 440.66.03 installer from nvidia's website and built a new set of packages.
I have not been able to get the game to run with the instructions above, on a 1080 ti Arch system, but have earned a 24 hour ban, meanwhile pirated versions of the game have been going around since day 1, while people that payed for the game get punished for just wanting to play.
Thanks Denuvo...
Any way around the 24 hour DRM ban?
I paid for this, it's not pirated, what is going on with this?
Any way around the 24 hour DRM ban?
I paid for this, it's not pirated, what is going on with this?
Sadly you can't do anything about it. Wait 24 hours or find someone who has the Bethesda.net version of the game and ask them for the .exe. I'm not sure if the updated version still has no Denuvo though
Any way around the 24 hour DRM ban?
I paid for this, it's not pirated, what is going on with this?Sadly you can't do anything about it. Wait 24 hours or find someone who has the Bethesda.net version of the game and ask them for the .exe. I'm not sure if the updated version still has no Denuvo though
i think they removed it pretty fast. you should still be able to find it online easily
Any way around the 24 hour DRM ban?
I paid for this, it's not pirated, what is going on with this?Sadly you can't do anything about it. Wait 24 hours or find someone who has the Bethesda.net version of the game and ask them for the .exe. I'm not sure if the updated version still has no Denuvo though
i think they removed it pretty fast. you should still be able to find it online easily
I have the 1.0 version without denuvo and it crashes if you try to launch the game with updated files
It works for me now with very good fps in the first few rooms.
I don't think I changed anything since yesterday :woman_shrugging:
Launch Options: RADV_PERFTEST=llvm %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
Arch Linux
Radeon RX 5700
mesa-aco-git 20.0 with ACO disabled (the RADV_PERFTEST=llvm
in launch options)
amdvlk 2020.Q1.3-1
self-compiled Proton-tkg 5.4.r10.g7c7868f4 (I'm sure I used this commit, although several doom eternal fixes came afterwards :thinking: )
~I do get the crackling audio, although I have faudio 20.03-1
on my system...~
edit: the next time i started doom, the crackling was gone.
It works completely fine now, I can even alt-tab!
The only issue right now is that the cursor in the menus is a tiny bit slow.
Just a quick note, like @Tk-Glitch pointed out, NVIDIA drivers have a problem specific to this game. Game uses system memory rather than VRAM.
@TimoFreiberg you aren't using amdvlk if those are your launch options, so AMDVLK means nothing to your system. If you have your system set to use mesa vulkan, then that's what it uses. You have to use VK_ICD_FILENAMES
to set a different vulkan driver.
Also, you might not be using mesa, you might be using AMDVLK, but in that case RADV_PERFTEST=llvm
is useless because llvm/aco are only RADV options, which is mesa. AMDVLK is separate. But the reason I say you might be using AMDVLK is because I discovered that Steam will default to AMDVLK on some games (at least some games, maybe all) if you have both AMDVLK and mesa installed on your system. With Resident Evil (both 2 and 7), for example, if you have both mesa and AMDVLK installed and don't specify VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json
then it uses AMDVLK.
Long story short, you're either using mesa or amdvlk, you can't use both, and if you're using amdvlk, RADV_PERFTEST
does nothing. You might be able to use mangohud to find out which one you're using, but otherwise you'll have to check the logs, it'll say RADV and NAVI 10 for the GPU, otherwise it'll say Unknown AMD GPU
or RX 5700
if you're using AMDVLK, I know the 5600 XT shows up with AMDVLK as "Unknown AMD GPU" but I'm not sure about the 5700 although I imagine it's the same. Either way if you're using Mesa it'll say RADV and just NAVI 10, otherwise you're using AMDVLK
@rabidlassie I don't think the game is intentionally using lots of system memory. On my Windows system the game uses a considerable amount of VRAM (~8 GiB at Ultra-Nightmare 1440p) and shows good performance. That it doesn't do that on Linux suggests that there is something that forces the game to reduce VRAM utilization. This explains poor performance (since much of the data has to hammer PCIe). I can't tell whether it is the driver or Wine/Proton, but I suspect it can be either of them. For example, maybe some Vulkan extension is not working correctly, which breaks texture/data streaming.
I paid for this
Yes, you get to enjoy the full 24 hours of it. Thank you for your purchase, dear customer.
Any way around the 24 hour DRM ban?
I paid for this, it's not pirated, what is going on with this?
@jonlee836 There is no workaround. Just wait and try again tomorrow. It sucks huge donkey cock I know, but it is what it is.
I'll say it again
Denuvo doesn't like Wine Staging, which proton-ge is based on, so if you want to avoid tripping Denuvo stick to normal Proton
and also avoid switching Wine versions too often, since it'll also trip Denuvo
@Voxed can you please upload the Proton archive file you had success with?
It's the build @999eagle uploaded. Use at your own risk of course.
https://uploadfiles.io/x58gs3ia
@mathew2214
https://github.com/Tk-Glitch/PKGBUILDS/commit/6353338e80f440148e7b31e9ecad8438265a2228
building from git might be the better way for more updated version
this is the build i did this morning
https://drive.google.com/file/d/1WRY8g8z1ulrfs1aYZqgO7KsdwmBT13Wk/view?usp=sharing
but considering now even Proton-5.4-GE-2 is working ,
I am unsure why everything is running without issues now even steams stock 5.0-5 is running
so I could have altered something else somewhere ... or last nights mesa update
at least now I am getting triple digits on an old R9 290
>
I'll say it again
Denuvo doesn't like Wine Staging, which proton-ge is based on, so if you
want to avoid tripping Denuvo stick to normal Protonand also avoid switching Wine versions too often, since it'll also trip
Denuvo
Does this apply to proton-tkg as well? This git issue is hard to keep track
of but I thought normal Proton doesn't work at all. I haven't been able to
get the game to run yet but I have no idea whether I've been banned or not
because I can't get past the HDP popup without a crash.
I think so. proton-tkg is usually built as staging
@blazini36 proton-tkg is built against staging by default. It can be built
against stable, but that has to be done manually and almost certainly isn't
on any of the builds floating around here. I personally thought vanilla
Proton was also built from wine staging but I guess not, although I could
have sworn it was. Either way, the staging builds have nothing to do with
it. Any new driver, wine/proton, or dxvk version you attempt to launch a
Denuvo game with gets registered as a specific machine. If you tweak little
things here and there, even if you use the same proton build, it counts as
a separate machine, and you only get like, 5 separate machine launches per
day with Denuvo. Even if you tried 5 non-staging builds, it would do the
same thing.
On Mon, Mar 23, 2020 at 6:15 PM jason0987 notifications@github.com wrote:
I think so. proton-tkg is usually built as staging
—
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-602885307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33YMR4WH53C474JNUPTRI7NQPANCNFSM4LP25FOQ
.
@gardotd426 Well I've encountered multiple times now, that if I use staging with any Denuvo game, I can't launch the game more than 5 times a day (activation limit) while this doesn't occur with normal wine. I've also seen another person describe the exact same issue with another game (NFS Heat)
As a follow up, I built mesa-git today and the artifacts are gone!
lib32-llvm 9.0.1-1
lib32-llvm-libs 9.0.1-1
lib32-mesa-git 20.1.0_devel.121503.41412cc4b74-1
lib32-vulkan-icd-loader 1.2.135-1
llvm 9.0.1-2
llvm-libs 9.0.1-2
mesa-demos 8.4.0-2
mesa-git 20.1.0_devel.121503.41412cc4b74-1
radeon-profile-git 20190903.r8.g306743e-1
vulkan-icd-loader 1.2.135-1
vulkan-tools 1.2.135-1
xf86-video-amdgpu 19.1.0-1
@jason0987 That sounds more like a prefix issue than wine-staging itself. Under certain conditions, a prefix can enter a state where any subsequent call to the Wine binary will trigger a prefix update, and result in a ticket generation from denuvo. Maybe there was a specific regression on staging at some point that triggered this, but nuking the prefix should fix that behavior on both mainline and staging.
Right now the only working setup I have is 999eagle's TkG build which has slightly crackly audio but more importantly it consistently crashes at a particular stage when hunting one of the Hell Priests. There a block you punch down with opens a big blue jump pad, and you use that to punch a crucified demon's green chestplate. I'll have to double-check where exactly that is. Regardless, the cutscene causes a complete machine crash a seconds or two in. Sound continues to play but graphics fail before turning into rainbows and no input functions, meaning I have to reset my mobo. Anyone else have this issue? How can I contribute to resolving it?
@wundrweapon try this
https://drive.google.com/file/d/1WRY8g8z1ulrfs1aYZqgO7KsdwmBT13Wk/view?usp=sharing
I am currently running this, unsure if its packed right or not , my file sizes always seem smaller than everyone elses releases
built on arch and running on my ubuntu 19.10 sound is fine for me now as well
steam overlay off and I am using
VK_ICD_FILENAMES=/pathto19.5files/amdvlkpro/amd_icd64.json STEAM_RUNTIME=1 steam
PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
@MasterCATZ I'm pretty sure that's the same build I have, TkG 5.4-r10-g7c7868f4. Plus I'm not using AMDGPU-PRO, I'm using the open-source amdgpu and amdvlk
@MasterCATZ with that proton version I'm getting this in the log:
3365.691:0015:0016:err:esync:esync_init Server is running with WINEESYNC but this process is not, please enable WINEESYNC or restart wineserver.
even a full restart didn't fix it, no idea where it's coming from. Any ideas on what could cause this?
@maarvw add PROTON_NO_ESYNC=1
to the launch options for the game.
@wundrweapon that's you're problem, the game doesn't work well with RADV (and doesn't work at all with ACO enabled on RADV). You need to use vulkan-amdgpu-pro
to get the best performance on AMD.
@gardotd426 i had that enabled from the start. used all the launch options suggested by @MasterCATZ infact.
Welp, guess I'll wait. I'm not gonna use proprietary drivers til I'm dead.
There's gotta be something, right? I can take bad performance, but there shouldn't be anything the proprietariat can render that the bourgeoifree is literally unable to. Even if I have to sit through a 1fps cutscene, surely there must be something to at least prevent a full-on system hang
@wundrweapon There's literally not. And I understand the whole wanting to use open source thing, but you're trying to play a proprietary game, and I guarantee you have numerous pieces of proprietary software on the same box you're saying you refuse to use proprietary GPU drivers on. It's always better to use Open Source when you can, but in this case unfortunately that's not an option. You don't have to replace Mesa, you can literally just use the proprietary vulkan driver JUST for this game and nothing else. It makes literally zero sense to arbitrarily draw your proprietary acceptance line at the point where it keeps you from playing a 60 dollar proprietary game you paid to play on a proprietary launcher, while also using other proprietary codecs, drivers, and other system components.
Mesa will probably improve in a month or two (or longer), but until then, just use the proprietary driver.
I would keep up responding, because the answer is "no", but that's off-topic. In the meantime I'll see if I can find why exactly amdgpu is crashing; with me luck
AMDVLK is a fine middle ground. It's the open source AMD driver and works with the game. It's not as good as AMDGPU-PRO but it's better than RADV at this time.
@gardotd426 While the game works better with amdgpu-pros vulkan driver RADV does not perform that bad on Vega cards, I tried both and yes its up to 50% Faster but if you use freesync you might want to stick with RADV (since amdgpu-pro does not support in on vulkan). For myself 60-70 fps (mesa) with freesync felt better than around 90-100 (amdgpu-pro) fps without freesync.
@Tbird761 I have amdvlk installed, and preformance metrics in-game show that that is the driver at play
@wundrweapon how ever my build was built this morning after navi patches were added
I am using
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-f02ae69 2020-03-22 eoan-oibaf-ppa)
with the amdpro files extracted from amdgpu-pro-19.50-967956-ubuntu-18.04
(vulkan-amdgpu-pro_19.50-967956_amd64.deb)
extract that file extract data.tar.xz and put those files somewhere edit amd_icd64.json to point to location of amdvlk64.so
the amd crap does not need to be installed :P
@MasterCATZ, I've already explained that, but you're still using a proprietary driver in that case, and apparently that's off the table for @wundrweapon. So they're stuck with what they've got until some more patches hit mesa-git.
@MasterCATZ I'm trying to do that but the game always crash. This is super weird because all other Vulkan applications are running with this ICD file.
Doing vulkaninfo
I obtain:
driverID = DRIVER_ID_AMD_PROPRIETARY
driverName = AMD proprietary driver
driverInfo =
Is there any comprehensive guide on how to integrate this? Because it's failing me hard...
Just switched from AMDVLK to RADV, and while the performance is noticably worse as mentioned, the cutscene played without a hitch. I'll keep going with this until we see another AMDVLK update and then redo that level
RE the Denuvo lockout:
I can confirm trying all the official Proton versions from steam, locked me out. Even from my dual boot Windows install.
I complained at Bethesda support.
Every1 here getting locked out, should do the same IMHO... :)
@wundrweapon just built AMDVLK runs fine
VK_ICD_FILENAMES=/home/aio/Programs/AMDVLK/bin/vulkandriver/drivers/xgl/builds/Release64/icd/amd_icd64.json STEAM_RUNTIME=1 steam
but I rather the 30% performance gain
VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlkpro/amd_icd64.json STEAM_RUNTIME=1 steam
@DistantThunder any chat system we could use lots of clutter going in here , downside to github , really needs a PM system
@999eagle 's list of steps isn't working for me :/ Attempts to load but quickly fails, steam button returns to just "play."
I've extracted the tkg into the .steam compatibility folder (tried in its root, as well as a dedicated folder for the tkg Proton build).
Below is my current launch options:
VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1 %command%
I have also tried strictly sticking to only the launch options in the original post.
Running KDE Neon 18.04 Plasma, AMD 5700XT w/ amdgpu.
@nessonic
Try starting steam with
VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json STEAM_RUNTIME=1 steam
also edit "amd_icd64.json" so that its path points to "amdvlk64.so"
default of amdgpu-pro would be be /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so
Proton files extracted in
~/.steam/compatibilitytools.d
root is just a symlink back to .steam
Did any1 try the https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-3 ?
I put it in the compatibility.d folder, but it does not show up in the proton version selection menu...
Hello @nessonic, %command%
allows you to put things in front of the command that gets run by steam. This allows us to set per-game environment variables that otherwise would be difficult to do. In your case, you were probably looking to have something like VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
.
for some reason mine does not load the drivers correctly if I put it in the game launcher so I start steam with it
FATAL ERROR: Please update your driver: VK_KHR_8bit_storage is required.
------ Command Line ------
Z:\ZFS3WAYSteamLibrarysteamapps\Manual\DOOM.EternalDOOMEternalx64vk.exe VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlkpro/amd_icd64.json PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
2020-03-24T12:15:28.292+10:00 LOG: Command Line: Z:\ZFS3WAYSteamLibrarysteamapps\Manual\DOOM.EternalDOOMEternalx64vk.exe VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlkpro/amd_icd64.json PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
VK_ICD_FILENAMES=/ZFS3WAY/SteamLibrary/amdvlkpro/amd_icd64.json STEAM_RUNTIME=1 steam
works for me how ever
I built vulkan-icd-loader and proton-tkg-r11 from tkglitch/pkgbuilds. When I go to edit /etc/vulkan/icd.d/amd_icd64.json it does not exist. The directory is there but it is empty. Is there a template for this file ?
{
"file_format_version" : "1.0.0",
"ICD" : {
"library_path" : "/opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so",
"api_version" : "1.1.129"
}
}
@blazini36 Even if the file was there, you have exactly zero reason to edit it. What made you think you should? If you have installed my amdgpu-pro package, you will find the json files in the /opt/amdgpu-pro/etc/vulkan/icd.d
dir. Launching the game with VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
as launch parameter will make use of amdgpu-pro instead of mesa.
@Tk-Glitch a couple of posts up mastercatz said to edit this file to point to the amdvlk driver. Thanks for clearing that up.
I set these launch options:
VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
Still crashes on me immediately, doesn't even ask about the HDR thing anymore, just get the winetricks popup then poof. Can't even tell if I'm banned.
@blazini36 can you start steam in the terminal so their is a console log
and I was referring to if someone downloaded and unpacked amdgpu-pro-19.50-1011208-ubuntu-18.04.tar.xz themselves without running someone elses harvesting script
nessonic had saved their file in /etc/vulkan/icd.d/ and that is who I was replying to
/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json is the default path
@Tk-Glitch actually, not sure if this was clear, I have installed amdgpu-pro......I do have the directory but it is empty, no json file in there.
/etc/vulkan/icd.d/amd_icd64.json
!= /opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json
@Tk-Glitch command does not run, maybe amdgpu-pro is not installed correctly. I just installe the package from pamac.
$ vulkaninfo | grep driver
ERROR: [Loader Message] Code 0 : /opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
driverVersion = 83886179 (0x5000063)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 20.1.0-devel (git-d9d549ff88) (LLVM 9.0.1)
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 20.1.0-devel (git-d9d549ff88) (LLVM 9.0.1)
VK_KHR_driver_properties : extension revision 1
driverVersion = 8388708 (0x800064)
driverID = DRIVER_ID_AMD_PROPRIETARY
driverName = AMD proprietary driver
driverInfo =
driverUUID = 414d442d-4c49-4e55-582d-445256000000
VK_KHR_driver_properties : extension revision 1
driverVersion = 8388742 (0x800086)
driverID = DRIVER_ID_AMD_OPEN_SOURCE
driverName = AMD open-source driver
driverInfo =
driverUUID = 414d442d-4c49-4e55-582d-445256000000
driverUUID = 414d442d-4c49-4e55-582d-445256000000
driverID = DRIVER_ID_AMD_OPEN_SOURCE
driverName = AMD open-source driver
driverInfo =
VK_KHR_driver_properties : extension revision 1
that is pretty normal
I have the amdpro-gpu drivers populating /opt/amdgpu-pro ...
vulkaninfo | grep driver
ERROR: [Loader Message] Code 0 : /opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so: wrong ELF class: ELFCLASS32
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.
driverVersion = 83886179 (0x5000063)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 20.1.0-devel (git-f02ae69 2020-03-22 eoan-oibaf-ppa) (LLVM 9.0.1)
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 20.1.0-devel (git-f02ae69 2020-03-22 eoan-oibaf-ppa) (LLVM 9.0.1)
VK_KHR_driver_properties : extension revision 1
driverVersion = 8388730 (0x80007a)
driverID = DRIVER_ID_AMD_PROPRIETARY
driverName = AMD proprietary driver
driverInfo =
driverUUID = 414d442d-4c49-4e55-582d-445256000000
VK_KHR_driver_properties : extension revision 1
driverVersion = 8388730 (0x80007a)
driverID = DRIVER_ID_AMD_PROPRIETARY
driverName = AMD proprietary driver
driverInfo =
driverUUID = 414d442d-4c49-4e55-582d-445256000000
VK_KHR_driver_properties : extension revision 1
@blazini36 Please provide a wine log.
To do so, open ~/.steam/root/compatibilitytools.d/proton_tkg_5.4.r11.g75c7644c/user_settings.py
and uncomment the WINEDEBUG
line. Then run the game until it crashes. You'll then find the log in your home dir steam-gameid.log
.
Well I don't have the default /opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json either, /opt/amdgpu-pro is as deep as it goes. so I suppose there is something wrong with my amdgpu-pro install? How are the Arch/Manjaro users installing this
Since you have built proton-tkg, you have my repo around. Go in the amdgpu-pro-vulkan-only
dir and run makepkg -si
. Follow the prompts. Done. However you seem to have messed quite a bit with your system so I'd get rid of whatever you have installed/added by hand/modified before doing so.
Actually, other than these proton builds, and the vulkan-headers and icd-loader from your repo I haven't really done anything out of the ordinary. Everything else was just through pamac and it's a fairly fresh manjaro install, ~ a month old. I'll try building the driver
wellp........
``:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [#############################################################################] 100%
(1/1) checking package integrity [#############################################################################] 100%
(1/1) loading package files [#############################################################################] 100%
(1/1) checking for file conflicts [#############################################################################] 100%
error: failed to commit transaction (conflicting files)
amdgpu-pro-vulkan-only: /opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so exists in filesystem (owned by lib32-vulkan-amdgpu-pro)
amdgpu-pro-vulkan-only: /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.so exists in filesystem (owned by vulkan-amdgpu-pro)
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).
err:vulkan:wine_vkCreateInstance Failed to create instance, res=-3
warn:debugstr:OutputDebugStringA "Unspecified Vulkan error: Error( VK_ERROR_INITIALIZATION_FAILED )"
Yup, something is frogged with your vk driver/libs.
Edit: You'll want to uninstall the vulkan-amdgpu-pro
and lib32-vulkan-amdgpu-pro
packages before proceeding.
Edit2: But you said you didn't have those files? Permission issues?
I uninstalled them through the package manager, your install ran fine after. Those packages were installed, I said the .json files were missing, and the default directory stopped 2 levels short. I didn't specifically check for any driver files, but the package manager did report them as being installed.
Edit: yeah I dunno, drivers from the tkg repo now installed, restarted, still crashes immediately. I can still run doom 2016 in Vulkan so I'd say nothing is too borked
Does DOOM 2016 run with VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
as launch param? Just to make sure amdgpu-pro works.
Did somebody manage to launch doom eternal with default amdgpu driver (not amdgpu-pro) and with usual wine+dxvk (not proton)?
Did somebody manage to launch doom eternal with default amdgpu driver (not amdgpu-pro) and with usual wine+dxvk (not proton)?
DOOM Eternal is Vulkan native game. DXVK is not involved.
@Tk-Glitch , Yes, it runs with that launch option @4k and 60fps locked
Does DOOM 2016 run with
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
as launch param? Just to make sure amdgpu-pro works.
Works great over here.
@ClockGen What igo95862 said. Regarding RADV, it requires mesa-git currently if you have a Navi GPU (some early 19.x should also work). Polaris/Vega should be able to run it OOTB with mesa 19/20. It doesn't currently work with ACO. And of course you need the winevulkan patch for wine else the game will crash on launch.
@blazini36 How did you make your proton build then? Did you run proton-tkg.sh, or did you use the PKGBUILD?
ran ./proton-tkg.sh from within the proton-tkg directory.
Regarding what you just sid to the other poster so I don't get confused here....are you saying Doom eternal requires mesa-git with a Navi GPU? I hope not cuz I'm running a 5700xt lol...........
EIther was I was running Mesa git and couldn't run the game, possibly for other reasons.
That's exactly what I said. I have made a hack for it yesterday (since I'm also using a 5700XT), but using AMDGPU-PRO is a functional alternative. The patch allowing RADV to run the game on Navi was only merged today in mesa-git, so unless you tried specifically today, and not too long ago, it was expected not to work.
Regarding the build process, it might be worth a shot running makepkg -s
to trigger dependencies resolution, then cancel it when it starts actually building wine, then re-run ./proton-tkg.sh
to make sure you build against a complete set of dependencies.
Well it's working...but it's slow and audio is crackling. Sometimes FPS dips to 28fps
CPU: Intel i7 8700K @ stock
GPU: nVidia GeForce RTX 2070 @ stock
Dist. Ubuntu-Budgie 19.10
Vulkan ver: 1.2.131
nVidia Driver ver: 440.66.03
Steam: Beta release
Proton: Proton-tgk 5.4.r10.g7c7868f4
Also, for the newbies fresh to Linux (like me). I wasn't able to run this from my NTFS volume until I followed these instructions below. It would crash on load.
https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
Guys, I'm at a complete loss here. I've tried everything I can and I can't get this game to work.
System specs:
Running the game with:
PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
So among the thing's I've seen here:
Stock 5.0-5 just crashes silently. The Proton logs are a staggering 54MB. I uploaded a compressed file: https://drive.google.com/open?id=1LQ5Xa6HbF3MadzNtefRaze1XdJyg4_4m
Here's a short extract of the end:
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3cf: DW_CFA_advance_loc 2
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d1: DW_CFA_restore %r14
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d1: DW_CFA_advance_loc 2
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d3: DW_CFA_restore %r15
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d3: DW_CFA_advance_loc 1
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d4: DW_CFA_restore %rbp
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d4: DW_CFA_def_cfa %rsp, 8
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d4: DW_CFA_advance_loc 1
84.223:003a:003b:trace:seh:execute_cfa_instructions 7f8bae60f3d5: DW_CFA_restore_state
84.223:003a:003b:err:seh:setup_exception stack overflow 1632 bytes in thread 003b eip 00007f8bb0c6a118 esp 0000000000130fb0 stack 0x130000-0x131000-0x230000
85.238:001e:0022:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\WineUsd.sys" : builtin
85.239:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winehid.sys" : builtin
85.239:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\hidclass.sys" : builtin
85.240:0016:001a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\drivers\\winebus.sys" : builtin
pid 3974 != 3973, skipping destruction (fork without exec?)
When I use 5.4-GE-2, I can reach the GPU driver version pop-up. I press play, and the game crashes shortly after. Here's a gist with the logs for it: https://gist.github.com/thebozzcl/80197c6c98652a70e801950ba677311e
The section that caught my eye was:
1494.038:0049:004a:fixme:dbghelp:elf_search_auxv can't find symbol in module
1494.048:0049:004a:fixme:dbghelp:elf_search_auxv can't find symbol in module
1494.058:0049:004a:fixme:dbghelp:elf_search_auxv can't find symbol in module
1494.059:0035:0036:trace:seh:call_teb_handler handler at 0x7b4749f0 returned 1
1494.059: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).
1494.069:0049:004a:fixme:dbghelp:elf_search_auxv can't find symbol in module
I think I saw somebody else who had a similar problem. I will have to dredge through the pile of comments again... but in the meantime, if anybody has any clue what the hell is causing this please let me know.
I'm completely at a loss here. I've compiled the latest wine-tkg-git and mesa-git. But the game keeps crashing at launch with this error
FATAL ERROR: Please update your driver: VK_KHR_get_surface_capabilities2 is required.
although this extension is in the latest radv, amdgpu-pro and winevulkan.
@Progman-DT I remember that error
Ubuntu 19.10 DRM 3.36.0, 5.5.11-050511-generic, LLVM 9.0.1 Mesa 20.1.0-devel
(git-f02ae69 2020-03-22 eoan-oibaf-ppa)
, can not remember what I did to solve it anymore,
it was either me patching the exe file
( instructions somewhere in first 300 comments but I think proton had a patch added since )
or it was the pre loading of the drivers when steam started
for me adding
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
never worked but something like this did
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.jsonn STEAM_RUNTIME=1 steam
then launching game with
PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
how ever not knowing who is Nvidia / AMD ... makes it hard knowing what drivers people are using
also you need Vulkan Instance Version: 1.2.135
@Progman-DT that error is because you don't either don't have the patched Proton (you didn't say which Proton version you're using) or you didn't upgrade your vulkan instance. mesa-git
isn't enough, that only provides vulkan-radeon
, which has nothing to do with the icd loader or headers. Nor does wine-tkg-git have anything to do with running the game. You need a patched PROTON-tkg, not wine-tkg-git, with the winevulkan patch. Or Proton-5.4-GE.
If you're on an Arch-based distro, you need to update (or install if you don't already have them) vulkan-icd-loader lib32-vulkan-icd-loader vulkan-tools vulkan-headers
(only vulkan-icd-loader
and vulkan-headers
will be required immediately for Doom Eternal, but you'll need the others anyway for other games. Either install them, or upgrade them.
Then you need either proton-tkg with the winevulkan patch, or Proton-5.4-GE-3 or whatever the latest GE build is.
So - after some further testing between the Steam version, and the 'DRM-free' version. Proton-5.4-GE-2 actually works. The problem is when users get the mysterious "no launch" crash where they hit the play button and the id logo shows in the system tray, then just exits - that's denuvo.
Chances are you're hitting denuvo and likely will have to wait it out. It's just crashing instead of giving the warning.
I managed to get the denuvo error earlier today with a new test build, then I made another build, and was hitting the "no launch" crash. I then tried with my 5.4-GE-2 release, and got the same "no-launch" crash. I then tried the "DRM-FREE" version with both 5.4-GE-2 and my test build - and both launched fine.
In fact, the standard Proton-5.0.5 also works with the 'DRM-FREE' version also.
For now I'm going to wait 24 hours and see if it allows to run afterwards.
For clarification, this is what the error log looks like with the "no launch" crash:
147104.271:0034:0035:trace:seh:call_teb_handler handler at 0x7b4749f0 returned 1
147104.271:0034:0035: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).
147104.279:005a:005b:fixme:dbghelp:elf_search_auxv can't find symbol in module
Register dump:
rip:000000014093f5bd rsp:0000000000924290 rbp:00000000009243c0 eflags:00010202 ( R- -- I - - - )
rax:00000001433551f8 rbx:0000000145ff3d80 rcx:0000000000000000 rdx:000000013b4442e8
rsi:000000000092cd90 rdi:0000000000000000 r8:0000000000000000 r9:0000000000000202 r10:0000000000000001
r11:0000000000000202 r12:0000000000000000 r13:000000014604e840 r14:000000000092ee50 r15:0000000000000000
Stack dump:
0x0000000000924290: 000000014263a8e8 000000007ca199e2
0x00000000009242a0: 0000000000000000 0000000000923da8
0x00000000009242b0: 000000000092cd90 000000014096ce89
0x00000000009242c0: 0000000000924d90 0000000000924cc0
0x00000000009242d0: 0000000000000000 0000000000000000
0x00000000009242e0: 000a7325202c6425 0000003000000020
0x00000000009242f0: 0000000000924dc0 0000000000924cf0
0x0000000000924300: 0000000000000000 0000003000000020
0x0000000000924310: 0000000000924de0 0000003000000020
0x0000000000924320: 0000000000924df0 0000000000924d20
0x0000000000924330: 0000000000924e00 0000000000924d30
0x0000000000924340: 000a7325202c6425 2c70252000000009
Backtrace:
=>0 0x000000014093f5bd EntryPoint+0xe2c4a59d() in doometernalx64vk (0x00000000009243c0)
1 0x000000014096ce89 EntryPoint+0xe2c77e68() in doometernalx64vk (0x00000000009243c0)
2 0x0000000140aebda5 EntryPoint+0xe2df6d84() in doometernalx64vk (0x0000000000000000)
3 0x0000000140318ce1 EntryPoint+0xe2623cc0() in doometernalx64vk (0x0000000000000000)
4 0x00000001403192a2 EntryPoint+0xe2624281() in doometernalx64vk (0x000000000092ffd0)
5 0x00000001423d06f7 EntryPoint+0xe46db6d6() in doometernalx64vk (0x000000000092ffd0)
6 0x000000007b455131 __wine_start_process+0x160() in kernel32 (0x000000000092ffd0)
0x000000014093f5bd EntryPoint+0xe2c4a59d in doometernalx64vk: movq (%rcx),%rax
Modules:
Module Address Debug info Name (136 modules)
PE 930000- a2c000 Deferred oo2core_8_win64
PE a30000- a43000 Deferred aclui
PE a50000- b96000 Deferred comctl32
PE 62600000- 6263c000 Deferred usp10
PE 637c0000- 6387a000 Deferred winmm
PE 64340000- 64380000 Deferred winhttp
PE 64940000- 64959000 Deferred shcore
PE 64c80000- 64c8d000 Deferred steamclient64
PE 64d40000- 64d4f000 Deferred vulkan-1
PE 65000000- 65143000 Deferred ole32
PE 65600000- 6561e000 Deferred xinput1_3
PE 65780000- 6578e000 Deferred version
PE 68a40000- 68a96000 Deferred shlwapi
PE 6a100000- 6a231000 Deferred oleaut32
PE 6a700000- 6a77e000 Deferred setupapi
PE 6afc0000- 6afcb000 Deferred msimg32
PE 6b2c0000- 6b340000 Deferred wininet
PE 6b880000- 6b887000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bed9000 Deferred imm32
PE 6c0c0000- 6c0d1000 Deferred wsock32
PE 6d9c0000- 6d9df000 Deferred mpr
PE 6e340000- 6e348000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6e6c8000 Deferred api-ms-win-core-localization-l1-2-1
PE 6e780000- 6e7da000 Deferred oleacc
PE 6f480000- 6f504000 Deferred gdiplus
PE 6fbc0000- 6fc44000 Deferred rpcrt4
PE 71240000- 71260000 Deferred jsproxy
PE 7b000000- 7b0bc000 Deferred kernelbase
ELF 7b400000- 7b67b000 Export kernel32<elf>
\-PE 7b410000- 7b67b000 \ kernel32
ELF 7bc00000- 7bdaf000 Deferred ntdll<elf>
\-PE 7bc20000- 7bdaf000 \ ntdll
ELF 7c000000- 7c004000 Deferred <wine-loader>
PE 13b400000- 13b44b000 Deferred steam_api64
PE 140000000- 15e3b2000 Export doometernalx64vk
PE 180000000- 18007b000 Deferred bink2w64
ELF 7f544ae80000- 7f544cbd4000 Deferred steamclient.so
ELF 7f544cbd5000- 7f544cf54000 Deferred lsteamclient<elf>
\-PE 7f544ccf0000- 7f544cf54000 \ lsteamclient
ELF 7f544cf56000- 7f544d074000 Deferred libgcrypt.so.20
ELF 7f544d074000- 7f544d095000 Deferred liblz4.so.1
ELF 7f544d095000- 7f544d0be000 Deferred liblzma.so.5
ELF 7f544d0be000- 7f544d150000 Deferred libpcre2-8.so.0
ELF 7f544d150000- 7f544d203000 Deferred libsystemd.so.0
ELF 7f544d203000- 7f544d230000 Deferred libselinux.so.1
ELF 7f544d230000- 7f544d286000 Deferred libdbus-1.so.3
ELF 7f544d286000- 7f544d28d000 Deferred libkeyutils.so.1
ELF 7f544d28d000- 7f544d56d000 Deferred libcrypto.so.1.1
ELF 7f544d56d000- 7f544d57f000 Deferred libkrb5support.so.0
ELF 7f544d57f000- 7f544d586000 Deferred libcom_err.so.2
ELF 7f544d586000- 7f544d59f000 Deferred libk5crypto.so.3
ELF 7f544d59f000- 7f544d690000 Deferred libkrb5.so.3
ELF 7f544d690000- 7f544d6a5000 Deferred libavahi-client.so.3
ELF 7f544d6a5000- 7f544d6b3000 Deferred libavahi-common.so.3
ELF 7f544d6b3000- 7f544d705000 Deferred libgssapi_krb5.so.2
ELF 7f544d705000- 7f544d7a1000 Deferred libcups.so.2
ELF 7f544d7a1000- 7f544d7fa000 Deferred libvulkan.so.1
ELF 7f544d7fc000- 7f544d805000 Deferred libxfixes.so.3
ELF 7f544d805000- 7f544d812000 Deferred libxcursor.so.1
ELF 7f544d8e8000- 7f544d916000 Deferred libexpat.so.1
ELF 7f544d916000- 7f544d95e000 Deferred libfontconfig.so.1
ELF 7f544d95e000- 7f544d978000 Deferred libz.so.1
ELF 7f544d978000- 7f544d9ae000 Deferred libpng16.so.16
ELF 7f544d9ae000- 7f544d9c2000 Deferred libbz2.so.1
ELF 7f544d9c2000- 7f544da83000 Deferred libfreetype.so.6
ELF 7f544da83000- 7f544da95000 Deferred libxi.so.6
ELF 7f544da95000- 7f544da9a000 Deferred libxcomposite.so.1
ELF 7f544da9a000- 7f544daa7000 Deferred libxrandr.so.2
ELF 7f544daa7000- 7f544dab4000 Deferred libxrender.so.1
ELF 7f544dab4000- 7f544dabb000 Deferred libxxf86vm.so.1
ELF 7f544dabb000- 7f544dac0000 Deferred libxinerama.so.1
ELF 7f544dac0000- 7f544db8b000 Deferred winex11<elf>
\-PE 7f544dad0000- 7f544db8b000 \ winex11
ELF 7f544db8c000- 7f544dbaf000 Deferred libgpg-error.so.0
ELF 7f544dbaf000- 7f544de2e000 Deferred libgcrypt.so.11
ELF 7f544de2e000- 7f544de39000 Deferred libffi.so.6
ELF 7f544de39000- 7f544deb6000 Deferred libgmp.so.10
ELF 7f544deb6000- 7f544dee8000 Deferred libhogweed.so.5
ELF 7f544dee8000- 7f544df25000 Deferred libnettle.so.7
ELF 7f544df25000- 7f544df3b000 Deferred libtasn1.so.6
ELF 7f544df3b000- 7f544e0bf000 Deferred libunistring.so.2
ELF 7f544e0bf000- 7f544e0e1000 Deferred libidn2.so.0
ELF 7f544e0e1000- 7f544e20d000 Deferred libp11-kit.so.0
ELF 7f544e20d000- 7f544e3e3000 Deferred libgnutls.so.30
ELF 7f544e3e3000- 7f544e3fc000 Deferred libnss_myhostname.so.2
ELF 7f544e3fc000- 7f544e405000 Deferred libnss_dns.so.2
ELF 7f544e405000- 7f544e41e000 Deferred libresolv.so.2
ELF 7f544e41e000- 7f544e424000 Deferred libnss_mdns4_minimal.so.2
ELF 7f544e424000- 7f544e438000 Deferred libnss_files.so.2
ELF 7f544e438000- 7f544e496000 Deferred winspool<elf>
\-PE 7f544e440000- 7f544e496000 \ winspool
ELF 7f544e496000- 7f544e4d8000 Deferred ws2_32<elf>
\-PE 7f544e4a0000- 7f544e4d8000 \ ws2_32
ELF 7f544e4d8000- 7f544e531000 Deferred winevulkan<elf>
\-PE 7f544e4f0000- 7f544e531000 \ winevulkan
ELF 7f544e531000- 7f544e575000 Deferred uxtheme<elf>
\-PE 7f544e540000- 7f544e575000 \ uxtheme
ELF 7f544e575000- 7f544efe6000 Deferred shell32<elf>
\-PE 7f544e590000- 7f544efe6000 \ shell32
ELF 7f544efe6000- 7f544f0d0000 Deferred msvcrt<elf>
\-PE 7f544f000000- 7f544f0d0000 \ msvcrt
ELF 7f544f0d0000- 7f544f104000 Deferred iphlpapi<elf>
\-PE 7f544f0e0000- 7f544f104000 \ iphlpapi
ELF 7f544f104000- 7f544f182000 Deferred dbghelp<elf>
\-PE 7f544f110000- 7f544f182000 \ dbghelp
ELF 7f544f182000- 7f544f331000 Deferred gdi32<elf>
\-PE 7f544f1a0000- 7f544f331000 \ gdi32
ELF 7f544f331000- 7f544f46c000 Deferred ucrtbase<elf>
\-PE 7f544f360000- 7f544f46c000 \ ucrtbase
ELF 7f544f46c000- 7f544f6fa000 Deferred user32<elf>
\-PE 7f544f490000- 7f544f6fa000 \ user32
ELF 7f544f6fa000- 7f544f723000 Deferred bcrypt<elf>
\-PE 7f544f700000- 7f544f723000 \ bcrypt
ELF 7f544f723000- 7f544f766000 Deferred sechost<elf>
\-PE 7f544f730000- 7f544f766000 \ sechost
ELF 7f544f766000- 7f544f7df000 Deferred advapi32<elf>
\-PE 7f544f770000- 7f544f7df000 \ advapi32
ELF 7f544f9f0000- 7f544fa04000 Deferred wow64cpu<elf>
\-PE 7f544fa00000- 7f544fa04000 \ wow64cpu
ELF 7f545d1ee000- 7f545d1fa000 Deferred libnss_sss.so.2
ELF 7f545e8d8000- 7f545e8de000 Deferred libxau.so.6
ELF 7f545e8e0000- 7f545e90b000 Deferred libxcb.so.1
ELF 7f545e90b000- 7f545e925000 Deferred libgcc_s.so.1
ELF 7f545e925000- 7f545e9e4000 Deferred libgldispatch.so.0
ELF 7f545e9e4000- 7f545e9f9000 Deferred libxext.so.6
ELF 7f545e9f9000- 7f545eb3f000 Deferred libx11.so.6
ELF 7f545eb3f000- 7f545eb73000 Deferred libglx.so.0
ELF 7f545eb75000- 7f545ecbb000 Deferred libm.so.6
ELF 7f545eeb5000- 7f545eebc000 Deferred libdl.so.2
ELF 7f545eebc000- 7f545eec7000 Deferred librt.so.1
ELF 7f545eec7000- 7f545ef5c000 Deferred libgl.so.1
ELF 7f545ef5c000- 7f545f125000 Deferred libc.so.6
ELF 7f545f127000- 7f545f149000 Deferred libpthread.so.0
ELF 7f545f149000- 7f545f4da000 Export libwine.so.1
ELF 7f545f4da000- 7f545f717000 Deferred gameoverlayrenderer.so
ELF 7f545f719000- 7f545f747000 Deferred ld-linux-x86-64.so.2
Threads:
process tid prio (all id:s are in hex)
00000008 steam.exe
["C:\windows\system32\steam.exe" /mnt/Games/Steam/steamapps/common/DOOMEternal/idTechLauncher.exe]
00000030 0
00000009 0
0000000c services.exe
[C:\windows\system32\services.exe]
00000027 0
00000018 0
00000011 0
0000000e 0
0000000d 0
0000000f plugplay.exe
[C:\windows\system32\plugplay.exe]
00000015 0
00000014 0
00000010 0
00000016 winedevice.exe
[C:\windows\system32\winedevice.exe]
0000001e 0
0000001d 0
0000001c 0
0000001b 0
0000001a 0
00000019 0
00000017 0
00000025 winedevice.exe
[C:\windows\system32\winedevice.exe]
0000002a 0
00000029 0
00000028 0
00000026 0
0000002b explorer.exe
[C:\windows\system32\explorer.exe /desktop]
0000002f 0
0000002e 0
0000002d 0
0000002c 0
00000031 idTechLauncher.exe
["Z:\mnt\Games\Steam\steamapps\common\DOOMEternal\idTechLauncher.exe"]
00000033 -2
00000032 0
00000034 (D) Z:\mnt\Games\Steam\steamapps\common\DOOMEternal\DOOMEternalx64vk.exe
[DOOMEternalx64vk.exe +com_enableCrashHandler 0 ]
00000059 0
00000058 0
00000057 0
00000056 0
00000055 0
00000054 0
00000053 0
00000052 0
00000051 0
00000050 0
0000004f 0
0000004e 0
0000004d 0
0000004c 0
0000004b 0
0000004a 0
00000049 0
00000048 0
00000047 0
00000046 0
00000045 0
00000044 0
00000043 0
00000042 0
00000041 0
00000040 0
0000003f 0
0000003e 0
0000003d 0
0000003c 0
0000003b 0
0000003a 0
00000039 0
00000038 -1
00000035 2 <==
System information:
Wine build: wine-5.4-205-g3ddf3a7 (Staging)
Platform: x86_64
Version: Windows 8
Host system: Linux
Host version: 5.5.8-fsync.300.fc31.x86_64
147104.485:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-appmodel-runtime-l1-1-2.dll" at 0x6c100000: PE builtin
147104.485:0031:0032:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000092FA80
pid 160393 != 160392, skipping destruction (fork without exec?)
@GloriousEggroll does the 'no-launch' also crash with division by zero?
@Progman-DT If you really want to use it with wine-tkg, you'll need to enable the _protonify
option in the .cfg to get the required winevulkan patch. Proton-tkg comes with it already enabled.
@gardotd426 @Tk-Glitch Thank you, I was able to launch the game. But now the "drm-free" version cannot connect to Bethesda servers and doesn't let me in:)
Not sure if this is of any help but I had the game running day-one on a clean ArchLinux install and can confirm the following, in the case of an AMD setup.
Mesa:
Mesa shader compilers:
Vulkan drivers:
Wine:
git clone https://github.com/ValveSoftware/wine.git
cd wine
./configure --enable-win64
make -j16
X11 config:
ALSA:
On my setup the game runs at a constant 100 FPS at 1080p with every setting on ultra nightmare (using a Sapphire RX5700 Pulse and Ryzen 2700).
@Tk-Glitch
Thanks for your efforts, the game runs now!
However, I'm getting the following message.
"Updated drivers are required. Installed: 337.88. Required: 442.74 or newer."
I have nvidia 440.64 installed so I'm not sure why this message is popping up.
Is this a problem with doom eternal not detecting the correct driver or proton/steam-wine?
@jonlee836 You can skip the driver check as noted here https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-2
@cylgom Thanks for this!
I've never run a custom built proton and/or Wine version in steam. Any tutorials for this you can recommend?
Also, what about Denuvo? Won't it be tripped by the custom built Wine / Proton version?
It does not trip Denuvo, no. I've been playing with the 999eagle build (tkg) and everything has been fine.
Well there are different experiences.
I tried two different versions yesterday 5.4-GE-2 and 5.4-GE-3.
Only trying to start each one time. Now I'm in DRM hell again. Can't even play it on my windows install.
Guess how mad I am!
Gonna wait for an officially supported version.
Meanwhile only my ElAmigos can help me out :)
Finally, I launched game with nvidia drivers and valve's wine, but I'm getting message "Unable to contact game services..." What to do? I'm using DRM-Free version.
Buy the game
On Tue, Mar 24, 2020 at 10:51 AM Eldar notifications@github.com wrote:
Finally, I launched game, but I'm getting message with Unable to contact
Bethesda services. What to do? I'm using DRM-Free version.—
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-603284603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y336GFYEVXJVUUHEAXFTRJDCIJANCNFSM4LP25FOQ
.
If this game is Vulkan native, Why it doesn't work on PROTON out of the box and with a good performance?
@CSahajdacny The same reason Red Dead Redemption 2 doesn't work out of the
box (at all, let alone with any good performance) - because it's not simply
a matter of "if a game has vulkan, it works." What makes you think that?
On Tue, Mar 24, 2020 at 11:29 AM CSahajdacny notifications@github.com
wrote:
If this game is Vulkan native, Why it doesn't work on PROTON out of the
box and with a good performance?—
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-603306849,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y336AIBX6UM4G7HEFPQDRJDGVDANCNFSM4LP25FOQ
.
@EldarAgalarov The DRM free EXE is for two versions behind where Steam is. You just have to use the Denuvo that comes with Steam.
My 24 hour ban is up. The game only runs sometimes for me with proton_tkg_5.4.r10.g7c7868f4, most of the time I get a black screen and have to force quit.
With Proton GE, nothing happens after I hit play after the driver detection problem.
The game is stuck at 40fps on low or high settings, GPU usage always 100% and sounnd is very gltchy.
@cylgom Once you built your own wine, how did you get Steam to launch Doom Eternal with it? I need some help with that part.
I've reinstalled my system with a newer version of GNOME and the game no longer hangs when alt-tabbing, however it captures input even when not focused on the window
While all the progress is good, this entire thread feels like a good use case for why windows gpu passthrough is a good idea.
While all the progress is good, this entire thread feels like a good use case for why windows gpu passthrough is a good idea.
It's boring to do things the easy way.
"While all the progress is good, this entire thread feels like a good use
case for why windows gpu passthrough is a good idea."
That's exactly why it's important to do this. These wizards will get this
game running perfect and headache free. Even if its through wine it's
important to get these games running easily through linux so the adoption
picks up and these games start getting offered natively.
5 years ago I didn't bother with linux gaming, I ran consoles because I
cant stand windows. Now it's so good that 90% of the windows games just run
by the time I buy them. This is a minor hiccup that does not bother me at
all.
On Tue, Mar 24, 2020, 1:39 PM PraetorianSC4 notifications@github.com
wrote:
While all the progress is good, this entire thread feels like a good use
case for why windows gpu passthrough is a good idea.—
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-603397535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJZQMOR3LVMYFHEVTL57YQLRJDV33ANCNFSM4LP25FOQ
.
While all the progress is good, this entire thread feels like a good use case for why windows gpu passthrough is a good idea.
It's boring to do things the easy way.
Let's not paint in broad strokes here. GPU passthrough for windows in linux is still quite complicated. I'm also not dismissing the immensely positive amount of outcomes achieved thus far, just making an observation.
@kelvinhbo What tool are you using in your second screenshot where you have GPU utilization and temps?
@dv1 @Tbird761 While I bought and downloaded the game from Steam I am currently launching it stand-alone, using the DRM-free executable a friend gave me and my own wine build. Shell script below to give you an idea.
#!/bin/sh
rm /home/cylgom/games/doom_eternal/log
/home/cylgom/games/doom_eternal/wine/wine64 \
/home/cylgom/games/pc/doom_eternal/DOOMEternalx64vk_nodrm.exe \
+in_terminal 1 \
+com_skipIntroVideo 1 \
+com_skipKeyPressOnLoadScreens 1 \
&> /home/cylgom/games/doom_eternal/log
I don't think people who bought the game should annoyed by DRM, so here's the md5 for just the main executable : 82a3ffa77c438979b863f27beab2f119
@MasterCATZ
I'm on Discord and on multiple Linux-related Discord channels.
For the record, I achieve this:
VK_ICD_FILENAMES=/opt/amdgpu-pro-19.50_967956-1/vulkan/icd.d/amd_pro_icd64.json vulkaninfo | grep Inst
WARNING: [Loader Message] Code 0 : Didn't find required layer object disable_environment in manifest JSON file, skipping this layer
Vulkan Instance Version: 1.2.135
Instance Extensions: count = 17
maxMultiviewInstanceIndex = 4294967295
drawIndirectFirstInstance = true
vertexAttributeInstanceRateDivisor = true
vertexAttributeInstanceRateZeroDivisor = true
@kelvinhbo What tool are you using in your second screenshot where you have GPU utilization and temps?
I used nvtop for that
@kelvinhbo
The game is stuck at 40fps on low or high settings, GPU usage always 100% and sounnd is very gltchy.
In case you missed it, I shared my experience with the same resolution, same GPU, weaker CPU. I decided it was not playable in 3440x1440 even on lowest possible settings.
By the way, that first room with the 3 zombies is not representative of the general game performance. You need to get to the first major combat scene at least. Also notice the fps getting annihilated on the bridge with the giant demon walking next to it... oofalicious.
Also many systems that are perfectly capable of running the game don't have VT-d/IOMMU support. GPU passthrough isn't an end all be all.
Plus anything that allows be to never touch Windows again is A+ in my book.
@nessonic
Try starting steam with
VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json STEAM_RUNTIME=1 steam
also edit "amd_icd64.json" so that its path points to "amdvlk64.so"
default of amdgpu-pro would be be /opt/amdgpu-pro/lib/x86_64-linux-gnu/amdvlk64.soProton files extracted in
~/.steam/compatibilitytools.droot is just a symlink back to .steam
So amd_icd64.json already pointed back to amdvlk64.so, I verified that file exists - so no change made there
I did move my compatibilitytools.d folder to .steam...and now after a Steam restart it's no longer finding the tkg version of Proton. I did try your launch options prior to making this change, same issue where it won't load at all.
I am not using amdgpu-pro FYI - unsure if that was required. I broke my system trying to install that the other week so I'll hold off on that driver if possible
Got this running under Ubuntu 19.10 with nvidia 1080: (DRM free version)
nvidia 440.64 via ubuntu graphics ppa
compiled vulkan loader from source
performance is in fact horrible - audio crackles, very laggy input, sub 30fps in 1080p. But it does run...
@nessonic
You do not need to install AMDGPU-PRO. You can grab Vulkan only with a few simple steps. Reposting instructions from earlier, just cleaned it up a little.
Download 19.50 - Ubuntu version if you want to copy/paste the commands below.
tar xf amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz
cd amdgpu-pro-19.50-967956-ubuntu-18.04
ar x vulkan-amdgpu-pro_19.50-967956_amd64.deb
tar xf data.tar.xz
cd opt
sudo cp -r amdgpu-pro/ /opt/
Steam launch option:
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
@nessonic, what distribution are you on? Because depending on which distro you're using, you seem to probably have been given bad information. Most distros I know, ~/.steam/root/compatibilitytools.d
is NOT a symlink back to ~/.steam
(which of course it's not, that wouldn't make any sense. In reality, ~/.steam/root
is the symlink, and it's NOT to ~/.steam
, it's to ~/.local/share/Steam
. So like this:
~/.steam/root/
------> ~/.local/share/Steam
. So it would be ~/.local/share/Steam/compatibilitytools.d
.
One easy way to check is to just run file ~/.steam/root
, and it'll tell you whether it's a symbolic link or not.
But the fact that your proton builds are not longer being detective shows that you were given bad information, just put them back where they were. It wouldn't make any sense to move them anyway, idk why that was suggested but it's impossible to find the earlier comments in this mess.
@gardotd426 I'm on KDE Neon 18.04. My /root is indeed a symlink over to .local/Steam. I'll put the compatibilitytools.d back
@nessonic that's why you shouldn't just randomly follow people sending you on wild goose chases, they often don't know what they're talking about. Also, if you move a folder from a symlink into the actual folder, it literally wouldn't do anything, because they're the same thing. So idk why they gave you that suggestion in the first place. Either way, just put compatibilitytools.d/
back in ~/.steam/root/
.
What proton version are you trying to use?
Got this running under Ubuntu 19.10 with nvidia 1080: (DRM free version)
nvidia 440.64 via ubuntu graphics ppa
compiled vulkan loader from sourceperformance is in fact horrible - audio crackles, very laggy input, sub 30fps in 1080p. But it does run...
Please, confirm the bad performance here:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394
@gardotd426 Lol I was confident I could move a folder back where it was, no worries there.
I've lately been trying with the tkg 5.4 r10 version that was compiled & posted here. I've also tried GloriousEggroll's latest (5.4 GE 2) to no avail. And of course tried 5.0-5 via the steam client.
stills crashes on
33594.400:000c:000d:fixme:dbghelp:elf_search_auxv can't find symbol in module
for me, on any proton version. Has anyone else had this issue or know how it could be fixed?
Is there some means to get a more organized conversation with statistics than this git issue? It's great that theres this many replies......shows there are quite a few people that want to get this working right. I still haven't gotten the game to start and Trying to wade through what works and what does not is like nearly impossible at this point while I assume the answer is probably already here
Talk to Liam at GamingOnLinux and see about getting a wiki going. We had to
do that for the crash issues with Navi, here's that wiki
https://www.gamingonlinux.com/wiki/AMD_Navi_GPU_troubleshooting
you think that format would help?
On Tue, Mar 24, 2020 at 7:15 PM blazini36 notifications@github.com wrote:
Is there some means to get a more organized conversation with statistics
than this git issue? It's great that theres this many replies......shows
there are quite a few people that want to get this working right. I still
haven't gotten the game to start and Trying to wade through what works and
what does not is like nearly impossible at this point while I assume the
answer is probably already here—
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-603552826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333IWZYCATKW25F72ITRJE5HPANCNFSM4LP25FOQ
.
@nessonic what's your setup?
On Tue, Mar 24, 2020 at 6:38 PM nessonic notifications@github.com wrote:
@gardotd426 https://github.com/gardotd426 Lol I was confident I could
move a folder back where it was, no worries there.I've lately been trying with the tkg 5.4 r10 version that was compiled &
posted here. I've also tried GloriousEggroll's latest (5.4 GE 2) to no
avail. And of course tried 5.0-5 via the steam client.—
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-603541020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33Y3RHA7CQPFCNWMK73RJEY7JANCNFSM4LP25FOQ
.
OS: Manjaro Linux 19.0.2 KDE
Kernel: 5.4.27-1-MANJARO
CPU: Intel i5-6600K (4) @ 4.4GHz (OC from 3.5GHz)
Memory: 32GB
GPU: NVIDIA GeForce GTX 1080
Driver: 440.64
proton_tkg_5.4.r10.g7c7868f4 with "+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1" (like @999eagle suggested).
Default setting from the box - high on all video options with dynamic scaling (1440p) @ 50% - Gave me 30-50 fps with some slight sounds problems (some kind of ticking now and then).
Lowering settings didn't seem to affect fps. Apart from changing scaling to 100% which affected the fps by 10. Changing to 1080p didn't affect anything performance wise.
I was monitoring these testings with GreenWithEnvy on other monitor and found out strange behavior. While I was playing the game, GPU% was at 100% all the time and Mem ctrl% was at about 10%... The card itself was cold... 50c cold... this card usually gets to 70c while I play other "less demanding" stuff. And while i'm in the game menu Mem ctrl% raises to 30% and the voltage aswell. Things get hotter from there. Didn't encounter anything like that before.
The game is playable tho.
Hope this info helped.
Also, would love to get suggestions on how to improve performance from here.
Thanks.
Hey guys, the game seems to run pretty well on my machine (ryzen 1500x 16gb ram gtx 1660ti) at medium settings with the resolution scalar set to 50. however, whenever I get an achievement in the game it immediately crashes and I cannot continue playing. I have a picture attached here.
Notice the black rectangle in the corner where the achievement used to be. Let me know if any of you have experienced this before.
@gardotd426 I briefly tried to get ahold of him on the IRC then realized I don't know what I'm doing on IRC. Do you mind getting ahold of him since you seem to know your way around? The format is fine I'm sure with listings of hardware, driver versions, launch options etc.. I'm sure TKG or someone can specify exacty what would be necessary better than me.....I can't get the game to run after all lol
Hello everyone! Just decided to remove the dust on my old github account to participate in this most relevant conversation, the most important of the last century in my opinion.
I was able to make Doom Eternal run with @999eagle 's Proton-tkg 5.4.r10.g7c7868f4
I used all these parameters, I don't know which ones are superfluous yet:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% +in_terminal 1 +com_skipKeyPressOnLoadScreens 1
Steam Beta
Lenovo Legion Y720
Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8
GPU: NVIDIA GeForce GTX 1060
RAM: 15.6 GB
The distro is Void Linux
Kernel Linux 5.5.11_1 x86_64
i3wm 4.18
NVIDIA driver 440.66.03
My linux was like a little mess, the vulkan-loader 1.2.135 drivers, vkd3d, libOSmesa, glu, etc, installed along with the NVIDIA downloaded from https://developer.nvidia.com/vulkan-driver
I uninstalled as much as I could of all that, reinstalled the NVIDIA driver (just in case) and it worked with tkg. Didn't work with GE-2 nor proton 5.05.
DOOM 2016 wasn't starting with Vulkan either before I did that. It started working too after that.
mesa 20.0.2_1 package is installed but I don't know if it does anything.
Performance is poor by kinda playable. Between 20 and 50 FPS, even in low video settings, depending on what is happening in the game. Moving very slow when fighting many demons.
DRM makes me wait 24hs after playing 5 times.
I get a black screen when switching to another workspace.
Played in Hell on Earth, almost finished it. Stopped to do other things and then DRM kicked in.
I hope the solution for the low FPS can be found soon...
@danielgul It seems to be using RAM as VRAM instead of the GPU's VRAM, for nvidia GPUs at least.
@gardotd426
well mine links back to the home folders steam
Another updated build:
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-3
Seems to work when not being blocked by Denuvo. Denuvo seems to actually give the expected notification when it blocks. Works with radv on mesa-git using llvm (not aco). Also works with amdgpu-pro. Did not test nvidia. Tested on at least two systems. Denuvo blocked my laptop.
@MasterCATZ That's not entirely common, I've had Steam on 6+ distributions
and it's always ~/.steam/root/ ---> ~/.local/share/Steam. Either way, what
was even the point in telling them to move their proton builds? If you move
them to the symlinked directory you're literally not doing anything at all.
On Tue, Mar 24, 2020 at 9:40 PM Thomas Crider notifications@github.com
wrote:
Another updated build:
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-3
Seems to work when not being blocked by Denuvo. Denuvo seems to actually
give the expected notification when it blocks. Works with mesa-git. Tested
on at least two systems. Denuvo blocked my laptop.—
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-603592529,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y335Q4T32YY3HDZR2C53RJFOI5ANCNFSM4LP25FOQ
.
@GloriousEggroll I tried GE-3 and I still get a crash immediately after hitting play, but that's been the case since I installed AMDGPU-pro. I can however play Doom 2016 or anything else at any time fine so I know my drivers are not completely borked.
Can you suggest launch options or anything to get this working with a 5700xt? I'm not sure why I'm failing so hard on this, at this point I'd be happy to see a Denuvo ban message
@blazini36 what are the errors you're getting? How did you install
vulkan-amdgpu-pro?
On Tue, Mar 24, 2020 at 10:02 PM blazini36 notifications@github.com wrote:
@GloriousEggroll https://github.com/GloriousEggroll I tried GE-3 and I
still get a crash immediately after hitting play, but that's been the case
since I installed AMDGPU-pro. I can however play Doom 2016 or anything else
at any time fine so I know my drivers are not completely borked.Can you suggest launch options or anything to get this working with a
5700xt? I'm not sure why I'm failing so hard on this, at this point I'd be
happy to see a Denuvo ban message—
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-603598132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337DTMSNOVMKACCE6CDRJFQ3RANCNFSM4LP25FOQ
.
@gardotd426 I have no Idea what the errors are, launching steam in terminal doesn't really say much and the log file is massive so who knows. I installed vulkan-amdgpu-pro from TKG's pkgbuilds, along with vulcan headers and icd-loader...135. I've tried every tkg/GE proton build that's come up and I still have no idea whats going on.
On Manjaro-KDE by the way, R5 3600/5700xt
SOrry for some ridiculous reason github keeps switching my sign in accounts, ShadeTechnik is me
check your amd_icd64.json and make sure it links to the right location,
they're all different. Some packages have
/usr/share/vulkan/icd.d/amd_icd64.json link to /usr/lib/amdvlk64.so or
/opt/amdgpu-pro/lib/amdvlk64.so, some of them are
/usr/share/vulkan/icd.d/amd_pro_icd64.json which links to /usr/lib/amd64.so
or /opt/amdgpu-pro/lib/amdvlk64.so, so on and so forth. I'm replying
through email right now so I can't do code tags, but you should be able to
confirm that the .json is the correct one by running:
yay -Qo /usr/share/vulkan/icd.d/amd_icd64.json
which should say that the file is owned by the tkg vulkan-amdgpu-pro
package you installed. At that point just cat it:
cat /usr/share/vulkan/icd.d/amd_icd64.json
It'll tell you where it looks for the amdvlk64.so file, at which point just
make sure you actually have that file there.
It's probably there, and everything probably works, but it always helps to
make sure it's not something stupid like that.
On Tue, Mar 24, 2020 at 10:31 PM blazini36 notifications@github.com wrote:
SOrry for some ridiculous reason github keeps switching my sign in
accounts, ShadeTechnik is me—
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-603605363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337XA6I2VWDLXJDTDMTRJFUHPANCNFSM4LP25FOQ
.
I'm hereby reporting that I have since managed to get the copy-protected Steam version to run without issue. Great performance on "Ultra Nightmare", no alt-tab crashes, etc.
* Based on Ubuntu 18.04.3 LTS.
Proton-5.4-GE-3.tar.gz
from here (thanks @GloriousEggroll):/home/<username>/.steam/root/compatibilitytools.d
.%command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
Good luck; I hope this helps some of you!
@gardotd426 I had to install yay since it's not an included Manjaro package but maybe this is my problem?
yay -Qo /usr/share/vulkan/icd.d/amd_icd64.json
/usr/share/vulkan/icd.d/amd_icd64.json is owned by amdvlk 2020.Q1.3-1
$ cat /usr/share/vulkan/icd.d/amd_icd64.json
{
"file_format_version": "1.0.0",
"ICD": {
"library_path": "/usr/lib/amdvlk64.so",
"api_version": "1.2.133"
}
}
I was back and forth with TKG about the amdgpu-pro thing but I thought it was sorted, doesn't really look like its using the AMDGPU-pro
@3c8e1f54a4b6 Why is +com_skipSignInManager 1
necessary? I can't find info on what exactly is missing in the campaign progress (so, if for example XP points are missing, weapon points are not tracked etc.) if I am not logged into a Bethesda account.
@3c8e1f54a4b6 I have nVidia card and so when it launches, it comes up with a dialog box saying the graphics driver version is old(337) and needs to be 442 or newer. On Linux latest is 440 and I have that version.
@gardotd426 I was not telling them to move it , they were saying they put it in /.steam/root/ as well
I was just telling them that was the same as /.steam
@3c8e1f54a4b6 Why is
+com_skipSignInManager 1
necessary?
I am happy to say it's not. Nothing changed when I removed it from my list of launch options. Also, adding it did not disable any Bethesda.net
-related features (as far as I can tell). The same goes for +com_skipIntroVideo 1
; removing it doesn't cause crashes, and the videos display just fine.
@3c8e1f54a4b6 I have nVidia card and so when it launches, it comes up with a dialog box [...].
Not sure, sorry! I have an AMD GPU, so I'm unable to reproduce any NVIDIA-related issues.
@blazini36 You're not looking at the right place for amdgpu-pro (at least with my packages). The readme gives the correct path for them: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/amdgpu-pro-vulkan-only
@blazini36 see that's exactly why I said to check, that's your problem
right there. You need to have
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json
In your launch options
On Wed, Mar 25, 2020, 1:03 AM Etienne Juvigny notifications@github.com
wrote:
@blazini36 https://github.com/blazini36 You're not looking at the right
place for amdgpu-pro (at least with my packages). The readme gives the
correct path for them:
https://github.com/Tk-Glitch/PKGBUILDS/tree/master/amdgpu-pro-vulkan-only—
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-603642128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337UXPWXFU2GYCIKFE3RJGGCFANCNFSM4LP25FOQ
.
@3c8e1f54a4b6 Fantastic, thanks! The only remaining issue is light crackling in the audio. Graphics seem OK (I couldn't actually play yet, have to take care of something else first, so I could only launch the main menu). Anybody knows anything about that?
EDIT: Crackling only seems to appear in the main menu, not in the game. Also, I set VSync to "Adaptive" to help performance.
@GloriousEggroll
The post of @3c8e1f54a4b6 above gave me hope again, so I tried your 5.4-GE-3 release.
Game starts, but after driver warning (I know I can disable that), there's just a black screen.
Maybe you can use that info about a nvidia setup.
Or maybe some1 else has any ideas.
Or the very silent proton developers can take a look.
System info:
Linux Mint 19.3 (Ubuntu 18.04 based)
custom kernel 5.5.11
latest mesa git
latest nvidia beta driver
Nvidia RTX 20180 Ti
steam beta client
steam command line output:
------ Command Line ------
DOOMEternalx64vk.exe +com_enableCrashHandler 0 +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
2020-03-25T09:47:59.396+01:00 LOG: Command Line: DOOMEternalx64vk.exe +com_enableCrashHandler 0 +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
------ OS Information ------
Microsoft Windows 7 Build 7601
------ CPU Information ------
AMD Ryzen Threadripper 3960X 24-Core Processor
1 CPU package, 24 physical cores, 48 logical cores
3.5 GHz AMD CPU with MMX & SSE & SSE2 & SSE3 & SSSE3 & SSE41 & SSE42 & AVX & HTT
32768 kB 1st level cache, 524288 kB 2nd level cache, 16777216 kB 3rd level cache
79.73 GB System Memory
idLib::SetProduction( PROD_PRODUCTION )
------- Initializing renderSystem --------
PreliminaryRenderSetup
...registered window class
-------------------------
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
-------------------------
Vulkan Device Info:
-------------------------
Vendor : NVIDIA
GPU : GeForce RTX 2080 Ti
VRAM : 11510 MiB
Driver : 440.66.04 (6e108100)
VK API : 1.2.135
Fossilize INFO: Overriding serialization path: "/Games/SteamLibrary/steamapps/shadercache/782330/fozpipelinesv4/steamapprun_pipeline_cache".
-------------------------
Device Extensions
-------------------------
+ VK_KHR_swapchain
+ VK_KHR_dedicated_allocation
+ VK_NV_dedicated_allocation_image_aliasing
+ VK_KHR_8bit_storage
+ VK_KHR_16bit_storage
+ VK_KHR_shader_float16_int8
+ VK_EXT_descriptor_indexing
+ VK_EXT_full_screen_exclusive
+ VK_KHR_driver_properties
Initializing Vulkan subsystem
ShowGameWindow: (0, 0) 1920 x 1080, full screen
RENDER THREAD STACK SIZE: 4194304
Initialized stack tracer
WARNING: idBroadcastManager::ReleaseBroadcastEvent called with out of range system ID [65535]
Fossilize ERROR: Error: pNext in VkSamplerCreateInfo not supported. (pNext->sType chain: [1000130001])
Fossilize ERROR: Failed to record sampler.
Fossilize ERROR: Error: pNext in VkSamplerCreateInfo not supported. (pNext->sType chain: [1000130001])
Fossilize ERROR: Failed to record sampler.
Fossilize ERROR: Error: pNext in VkSamplerCreateInfo not supported. (pNext->sType chain: [1000130001])
Fossilize ERROR: Failed to record sampler.
Fossilize ERROR: Error: pNext in VkSamplerCreateInfo not supported. (pNext->sType chain: [1000130001])
Fossilize ERROR: Failed to record sampler.
proton log:
steam-782330.log
Thanks
5.4-GE-3 works whereas 5.4-GE-2 didn't, performance appears to be a few fps better than tkg-5.4 in calm areas but i still get 20fps in fights on low settings.
In-game diagnostics still showing vulkan 1.1.119 which may be the cause (i'm opted into steam beta and running steam-runtime)
5.4-GE-3 Works for me! With
%command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
You don't need any launch options at all, the game runs without them.
Also no need for %command% at the start of the launch options.
The syntax goes:
1: environment variables
2: %command%
3: command line arguments for the specific game executable
Example:
PROTON_LOG=1 %command% +com_skipIntroVideo 1
Hello! I can't get it to work...
My setup:
elementary OS 5.1.2 Hera based on Ubuntu 18.04.3 LTS
Linux 5.3.0-42-generic
GTX1060 6GB with 440.64 drivers
I have steam beta
I ran with the newest 5.4-GE-3 and launch options: PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
I found two error messages in the log, repeated multiple times:
FATAL ERROR: Please update your driver: VK_EXT_full_screen_exclusive is required.
ERROR: ld.so: object '/home/luka/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Any ideas how to fix this? Thanks!
Edit: Uploaded entire log
steam-782330.log
@gardotd426 that did it now it launches. When I first checked that path I didn't have AMDGPU-PRO installed correctly, then the next day when I did I must have not realized I was using the wrong path.
Surprised I didn't have a ban but I was able to launch it with GE3 and TKG-r12. On the 5700xt@1440p I'm getting ~60FPS that dips to ~30 in fights on the first stage. A bit of crackly audio in the menu but it seems to stop in game.
GE3 might run slightly smoother than TKG-r12. I'll have to wade through the thread and see if there is any improvements to be had when I get off work but for now its definitely playable. I haven't messed with it much and my only launch option is:
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json %command%
Thanks guys
@johnygum you need to install the latest beta driver from nvidia, it comes with vulkan 1.2.135, which has that VK_EXT_full_screen_exclusive feature.
https://developer.nvidia.com/vulkan-driver
You can safely ignore the ld.so preload error.
@blazini36
Your 5700XT performance is weird. What settings are you playing at? What does it display as a Vulkan Driver in the in-game perf overlay?
On Vega @1440p on High, I'm more around 90-120 fps.
Finally working for me now thanks to GE3!
AMD Radeon 5700XT
Kubuntu 19.10
Latest Oibaf PPA (mesa-git)
LunarG Vulkan Package: https://packages.lunarg.com
5.4-GE-3
Steam Beta Client
Runs perfectly, FPS crazy smooth, performance on par with my windows partition, only tested a little bit so far but no graphical glitches, can alt-tab out fine if the game is set to windowed/borderless.
Official Denuvo stuffed exe.
@DistantThunder I left everything set the way it was default for 1080p and just changed the resolution to 1440p so it is high/ultra. Like I said I didn't take any time to play with it much, I was just happy to see it launch....I'll mess with it later today
Really annoying that git keeps randomly switching my accounts based on the device I'm using. The above was my comment.
@AllKind I have updated my graphics drivers to 440.66.04, but the error seems to be the same...
steam-782330.log
Thanks @GloriousEggroll , with Proton-5.4-GE3 it works for me!
Debian 10.3 (4.19.98-1)
i5 7600k, 32 RAM, RTX2070
Steam Beta client
Vulkan 1.2.131.2
NVIDIA driver 440.66.04
Game is running out-of-box from Steam client without any launch options or DRM-Free binary.
On 4k and "Ultra Nightmare" I'm getting 20-25 FPS.
On 2k and "Ultra Nightmare" I'm getting 40-60 FPS.
Sound is almost clean, at least it's not annoying me.
Great job!
@johnygum it could be your are hitting the Denuvo block (DRM protection).
Somebody described the exact error in some posts above (sorry I don't take the time now to do all the scrolling). Find that post and compare it (maybe without PROTON_LOG=1, just starting steam in a terminal). If they are the same, you got to wait 24 hours... and yeah welcome to Denuvo hell.
@AllKind Oh, yeah that might be the case, I was starting Doom a bunch of times lately when I was trying different configurations.... Thanks
with @GloriousEggroll's new GE-3 proton, it finally works for me.
Linux Mint 19.3
Nvidia GTX 1070
using the unmodified steam .exe
did not use any of the launch options to skip things.
still getting the "outdated driver" error but i just click past that
performance is still pretty bad, getting 40-60 fps on lowest settings with really bad dips in quality during some cutscenes and tense encounters. but it works
Kubuntu 18.04
Nvidia GTX 1070
Nvidia driver 440.64
Vulkan 1.1.126
Proton 5.4-GE-3
(standard exe started from steam)
I have hot the outdated driver message. The game crashed at the first two tries in the loading screen. But after that I was able to start my campaign and play the game. The performance was quite bad i have got 10-20 fps at the lowest settings with a resolution of 1080p. The crackling sound issue does also occur.
Please, confirm the bad performance here:
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394
Hello @mozo78, you've self-promoted your forum link 4 times now. Consider this a warning that any further self-promotion will be considered spam.
People with 5700xt here, do you have a problem when the game freeze the whole system 5 minutes into the game? I'm using Proton 5.4-GE-3 and amdgpu-pro.
@Progman-DT I have also experienced freezes on my 5700 either at random and in certain areas of the map. The display driver always crashes during the Cultist Base level when you drop in to the pit (Where those exploding deamons are introduced) for example. Sometimes the display driver managed to recover and GNOME-shell will crash, sometimes the entire system just reboots, sometimes I manage to switch to another TTY before the display driver tries to recover which lets me reboot the system like normal via the TTY, switching from a TTY back go GNOME-shell will still either lock the system or crash GNOME-shell.
These issues I experienced with AMDVLK-pro 19.50 + Linux 5.6rc4 + This custom Proton build
I am unable to confirm if these issues exist on the latest stable kernel and Proton 5.5 and/or GE (in combination with RADV if possible) because Denuvo keeps giving me 24 hour bans whenever I launch the game..
@dennis1248 AMDVLK is known to have such an issue with the game. RADV doesn't have the issue but lower performance (and you need either early mesa 19 or mesa-git for Navi or the game will crash on launch). The proprietary amdgpu-pro driver also works stabler than AMDVLK and with high performance. Not sure if it's as stable as RADV though.
Nope, just compiled the latest mesa-git, and the game still freezes the whole system with RADV even faster than with amdgpu-pro.
Then you likely have another issue. I have finished the game with my own proton builds and RADV+5700XT without a single crash or hang. That being said I have played the first hour or so on AMDGPU-PRO with no crash or hang either.
This guy noticed the issue with nvidia: https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394/6
Apparently the game barely uses any VRAM, and I checked it too for myself. You can too if you got two screens: htop and watch nvidia-smi on one screen and the game on the other. Check it out yourself too if you're curious
I literally have almost the same framerate running on both low and ultra, and with all up to ultra settings, the game only uses ~850 MB of VRAM, and the process used ~9GB of RAM; It would drop to ~550MB for the game and ~5-6GB with setting on low/medium.
Is there any explanation for this?
Hello @mozo78, you've self-promoted your forum link 4 times now. Consider this a warning that any further self-promotion will be considered spam.
Hello @kisak-valve,
This isn't my forum, it's the NVIDIA forum.
Proton-5.4-GE-3 works, no extra parameters needed. Steam Beta. Updated to NVIDIA 440.66.04
It even plays the sound in the intro bethesda video, which the tkg didn't.
Can't switch to any other window/workspace or the DOOM screen/window goes all black.
Usage of laptop RAM: 60% of 15.6GB
Usage of graphic memory: 23% of 6GB
Proton-5.4-GE-3 works, no extra parameters needed. Steam Beta. Updated to NVIDIA 440.66.04
It even plays the sound in the intro bethesda video, which the tkg didn't.Can't switch to any other window/workspace or the DOOM screen/window goes all black.
Usage of laptop RAM: 60% of 15.6GB
Usage of graphic memory: 23% of 6GB
Settings matter a lot, can you specify what quality settings you put on? (texture matters most for this)
I got it working with @GloriousEggroll's Proton-5.4-GE-3. Although, there are some graphical artifacts and stuttering. Take a look:
https://www.youtube.com/watch?v=NhK5NRv7Xhw
I have all the settings in the lowest as possible, and turned off everything that can be turned off.
It's still running below 60FPS, got 17 FPS minimum during non gameplay scenes.
I think the VRAM is not being used either as it should.
In the last run the Nvidia-Settings is telling me the dedicated memory reached 1863 MB (31%), but the base when it is not running is 21%.
People with 5700xt here, do you have a problem when the game freeze the whole system 5 minutes into the game? I'm using Proton 5.4-GE-3 and amdgpu-pro.
Yes, it felt like always when i was fighting Hell knights, no idea if this is related. But after switching to amdgpu-pro compiled with Tkglitch's PKGBUILDS (Its version 19.50, aur has 19.30 right now) everything works fine :) But im using the proton version posted by 999eagle, with GE 3 the game crashes after starting
I got it working with @GloriousEggroll's Proton-5.4-GE-3. Although, there are some graphical artifacts and stuttering. Take a look:
https://www.youtube.com/watch?v=NhK5NRv7Xhw
I had the same problems. I bet you are using an amd gpu with vulkan-radeon? Try switching to amdvlk or vulkan-amdgpu-pro. They worked for me without those artifacts :)
I got it working with @GloriousEggroll's Proton-5.4-GE-3. Although, there are some graphical artifacts and stuttering. Take a look:
https://www.youtube.com/watch?v=NhK5NRv7XhwI had the same problems. I bet you are using an amd gpu with vulkan-radeon? Try switching to amdvlk or vulkan-amdgpu-pro. They worked for me without those artifacts :)
Thanks! That fixed the artifacts, but the stuttering is still there.
Edit: Another weird thing, the tab button doesn't seem to be working.
Thanks! That fixed the artifacts, but the stuttering is still there.
Edit: Another weird thing, the tab button doesn't seem to be working.
Did you try turning Steam overlay and steam fps counter off in the games properties on steam?
Finally working!
Specs:
How:
cd Vulkan-Loader
mkdir build
cd build
cmake ..
make
sudo make install
sudo ldconfig
vulkan-tools
from apt and run vulkaninfo | less
. That will show you your Vulkan version. Should be updated after running ldconfig
.+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
Audio is crackling, (EDIT) performance is awful... but it runs! I'll get to testing and fixing audio in a bit, and will update my post if I get it to work.
EDIT: I managed to fix the audio by changing the screen resolution. It was not set at my laptop's native resolution, for some reason. Performance is still god-awful, though, and videos do in fact seize up.
My specs:
Ubuntu 18.04
kernel 5.3.0-42-generic (hwe)
GeForce drivers 440.64 (I uninstalled all of the ubuntu nvidia packages, and ran the nvidia one by hand after systemctl isolate multi-user.target
)
GeForce GTX 970 card
Proton-GE-5.4-3 (even though I hit this bug, it seems to be using the right one for Doom Eternal)
I also added +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
to launch parameters.
I get a "GPU Driver Error"
Hitting Yes exits immediately.
Hitting Play churns my CPU for a bit, and then exits.
What am I missing?
Has anyone else encountered a crash while playing the game and earning an achievement/seeing a friend come online? This keeps happening to me and it is starting to get really frustrating.
@DrSlowpokePhd Doom currently will crash if the window loses focus for any reason. Any steam popup or even changing volume will cause it to freeze.
@DrSlowpokePhd playing with Borderless Windowed mode seems to fix it for me, although I would also recommend disabling Steam Overlay.
My specs:
Ubuntu 18.04
kernel 5.3.0-42-generic (hwe)
GeForce drivers 440.64 (I uninstalled all of the ubuntu nvidia packages, and ran the nvidia one by hand aftersystemctl isolate multi-user.target
)
GeForce GTX 970 card
Proton-GE-5.4-3 (even though I hit this bug, it seems to be using the right one for Doom Eternal)
I also added+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1
to launch parameters.I get a "GPU Driver Error"
Hitting Yes exits immediately.
Hitting Play churns my CPU for a bit, and then exits.What am I missing?
Kai4785, I believe that behavior is what happens when the DRM kicks in after trying to run it more than 5 times.
My game runs all right with GE-3 (except for the low FPS cause of the game not working well with NVIDIA), but after playing 5 times it starts to do as you describe. I am waiting 24hs now until being able to play again.
@KaeKun DRM should only trigger if you use 5 different wines or something similar.
@KaeKun DRM should only trigger if you use 5 different wines or something similar.
For me it does every 5 times I run it with the same Proton. Unless something else is happening.
Finally working!
Specs:
* Ubuntu 19.10, kernel 5.3 * GeForce drivers 440.44
How:
1. Use [Proton-GE-5.4-3](https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.4-GE-3) 2. (Maybe optional? Not sure) Build and install [Vulkan-Loader 1.2.135](https://github.com/KhronosGroup/Vulkan-Loader). Clone the repo and run:
cd Vulkan-Loader mkdir build cd build cmake .. make sudo make install sudo ldconfig
1. Install `vulkan-tools` from apt and run `vulkaninfo | less`. That will show you your Vulkan version. Should be updated after running `ldconfig`. 2. Run the game with the following launch config: `+in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1`
Audio is crackling, (EDIT) performance is awful... but it runs! I'll get to testing and fixing audio in a bit, and will update my post if I get it to work.
EDIT: I managed to fix the audio by changing the screen resolution. It was not set at my laptop's native resolution, for some reason. Performance is still god-awful, though, and videos do in fact seize up.
Got it working as well.
Specs:
Fedora 31 with all updates
GPU: nvidia GTX 1070, driver 440.64
Used the proton build mentioned above
Worked with whatever Vulkan loader version Fedora 31 currently has.
Notes on performance: It's generally bad. Things can be improved by switching to Bordeless Window and turning off V-Sync. What this gets is good FPS and render quality on a mix of High and Ultra settings in the menu, and 30+ fps in the Gore Nest mission (but with crap quality since the game will scale everything down to try and hit 60fps). I presume that setting 30fps as scaling target will improve visuals.
Sound crackles.
I'm having deja-vu from 2016 when Doom was in a similar state for a while on Linux.
What am I missing?
@kai4785 You can edit a config file to remove the driver warning.
Copypasta from Proton-5.4-GE-2 release notes:
To get rid of pre-launch GPU notices such as (HDR not supported), open DOOMEternal/launcherData/launcher.cfg and change all of these to 0:
rgl_showAMDStartupWarning 0 rgl_showIntelStartupWarning 0 rgl_showNvidiaStartupWarning 0
@zachzilla04 it doesn't have to be 5 different wines. It can be one wine
run 5 different times if you tweak or change things like DXVK version,
vulkan icd loader version, vulkan driver (amdvlk, radv, amdgpu-pro, etc),
anything like that can trip Denuvo into thinking you're on a different
machine. It happened to me multiple times with Resident Evil 2 before they
removed Denuvo.
On Thu, Mar 26, 2020 at 9:24 AM dpanter notifications@github.com wrote:
What am I missing?
@kai4785 https://github.com/kai4785 You can edit a config file to
remove the driver warning.
Copypasta from Proton-5.4-GE-2 release notes:To get rid of pre-launch GPU notices such as (HDR not supported), open
DOOMEternal/launcherData/launcher.cfg and change all of these to 0:rgl_showAMDStartupWarning 0
rgl_showIntelStartupWarning 0
rgl_showNvidiaStartupWarning 0—
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-604428925,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333OE3B32WLMXDVAHYDRJNJRZANCNFSM4LP25FOQ
.
Thanks for the help.
In my config, rgl_showNvidiaStartupWarning 0
was already 0, and the warning still displays.
But setting rgl_minNvidiaDriverVersion 0
to 0 does work! : )
This morning, behavior is different, presumably because of "Denuvo" reasons. Now I get
Clicking "Retry" here just pops back up, clicking "OK" exits.
@kai4785 You triggered the DRM somehow and now you have to wait 24 hours.
So the community has done a lot of work:
So it would be great to hear from the Valve people here. The proton developers.
Thanks,
AllKind
Thanks! That fixed the artifacts, but the stuttering is still there.
Edit: Another weird thing, the tab button doesn't seem to be working.Did you try turning Steam overlay and steam fps counter off in the games properties on steam?
Good call. Disabling the Steam overlay makes the tab button work.
On another note. Installing amdvlk
fixes the artifacts in Doom Eternal, but introduces them in other games, such as 7 Days to Die.
On another note. Installing
amdvlk
fixes the artifacts in Doom Eternal, but introduces them in other games, such as 7 Days to Die.
As a reminder for others in the same boat, you can specify which Vulkan ICD you want to use with the VK_ICD_FILENAMES environment variable instead of trying to juggle which one is installed or default. If you have multiple ICDs on your system, just specify the path to the json file that defines the one you want to use with a particular game.
@PopeRigby just don't use AMDVLK for those games. AMDVLK is used by setting
an envvar, although Steam will often use it by default if it's installed.
But for your other games, just put:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command%
in the launch options. Sorry I can't use code tags, I'm replying via email
and so they don't work.
On Thu, Mar 26, 2020 at 2:10 PM PopeRigby notifications@github.com wrote:
On another note. Installing amdvlk fixes the artifacts in Doom Eternal,
but introduces them in other games, such as 7 Days to Die.—
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-604590491,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y332D4MDNHUXXG4EEVO3RJOLC3ANCNFSM4LP25FOQ
.
So will I have to specify RADV for every game expect for Doom Eternal?
Every steam game, yep. For some reason Steam automatically uses AMDVLK when
it's installed, even though nothing else (like Lutris/Wine) does that.
Trust me, it drove me insane before I found that out, because Navi cards
with AMDVLK cause menu text to not render in Resident Evil 7 or Resident
Evil 2 Remake, and I was flipping out before I realized what had happened.
The alternative would be to install amdvlk and it's associated json files
somewhere else, but that's not really possible (well it is, but not
advisable) with the official Arch/Manjaro package. So just add that for the
games you don't want to use amdvlk for in Steam. If they don't have
rendering issues I would just keep amdvlk though, because performance is
mostly the same.
On Thu, Mar 26, 2020 at 2:16 PM PopeRigby notifications@github.com wrote:
So will I have to specify RADV for every game expect for Doom Eternal?
—
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-604593560,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y335NH2KCQEAYZEZZCT3RJOLYTANCNFSM4LP25FOQ
.
It's likely a matter of defaults. Launch Steam itself with that environment variable set to whichever ICD you want to use by default and just change the ones you want to be different.
There is hope for us with NVIDIA!
https://forums.developer.nvidia.com/t/low-performance-in-doom-eternal/116394/16
Since this issue is already used like a forum thread:
for me with amdgpu-pro vulkan everything just works, even steam overlay and the steam controller (though annoyingly in the menu the right trigger becomes mouse click, but this can be worked around via mapping 'a' and 'd' to the grip buttons).
To resolve the remaining minor problems:
default-sample-rate = 48000
in /etc/pulse/daemon.conf (file location depends on the distro) and restart pulseaudioFor a potentially easier solution, this instruction video by Chris Titus Tech might be worth looking into:
https://www.youtube.com/watch?v=g3UPxd8iUsU&feature=emb_logo
I just found a solution to my Nvidia performance issue, bought a RX5700 second hand and sold my RTX2060 for the same price ;)
For a potentially easier solution, this instruction video by Chris Titus Tech might be worth looking into:
That video is a horrible train wreck of confusing, flawed, and out-right incorrect information. Holy heck man, it actually hurts to watch.
For a potentially easier solution, this instruction video by Chris Titus Tech might be worth looking into:
That video is a horrible train wreck of confusing, flawed, and out-right incorrect information. Holy heck man, it actually hurts to watch.
The video is 11 minutes long when it takes < 2 minutes to explain and get things working. The website is a better tutorial than the video. _Install the latest modified Proton with these commands_ and then _copy + paste these launch options_ and then run. Then the video just stretches everything out to 11 minutes with rambling.
Just to summarize the issue (for anybody coming along looking for resourceful information):
DOOM Eternal is using Vulkan headers that are not (or were not) available on Proton and most Linux distros.
To fix this and get the game to launch without crashing, you must use a modified Proton and install Vulkan loader and headers version 1.2. Most people are relying specifically on Proton 5.4-GE-3.
You place Proton in ~/.steam/root/compatibilitytools.d
and then go to DOOM Eternal properties and force Steam to use the custom Proton.
There are also some issues with the default boot of the game, so adding certain launch options is also necessary. RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
These seem to work fine.
AMD GPU users seem to have great performance beyond this point, but NVIDIA GPU users like myself are having performance issues - something that NVIDIA seems to be looking into, not something Valve or Proton can necessarily fix.
Tinkering too much with Proton versions or game files can trigger a DRM lock which will prevent you from launching the game at all for at least 24 hours, but it will notify you of this through a message box when you try to start the game.
Edit: That brings us here. There is unofficial support for the game. Performance degredations for NVIDIA users. Depending on the system, there might be crackling in the sound. JcKlomp claims you can fix this, though, by changing the default sample rate to 48 kHz.
I got DOOM to boot, and no performance issues here, but it crashes every time a steam popup happens. Is there a known fix yet? Alternately a way to disable steam achievements from showing would help.
@75AngryDucks , I think it was mentioned that using borderless window in the in game video settings and disabling steam overlay in the steam game properties may help to prevent that.
@KaeKun I have it set to borderless, and that fixed it until the next time I loaded the game. Steam overlay is also disabled but it still shows achievements. I have it set to windowed now, and will test to see if it crashes. Oddly enough it's still fullscreen even with bordered window mode.
@SalmonSeasoning , the game may or may not tell you about you being blocked by the DRM, it may just crash after the first second of the introvideo freezing the bethesda block logo falling animation, or may just go black screen and then crash, or it may go black screen and hang there until you kill the process. I got all those different behaviors.
I even got a new behavior! I just now let the game crashed there and this window suddenly popped up. It is the first time this happened to me. This happened during DRM lock.
Also, using proton seems to be enough to the DRM lock it, at least that's my experience. Is anybody else being able to start the game a lot of times during the day?
@KaeKun I would't suspect DRM to prevent allocation of video memory. That's more of a system failure. Have you tried updating your NVIDIA/AMD drivers? What distro are you using etc? I'm not a Linux pro, but I'd say you should definitely double check all your drivers and and stuff are up to date. Try verifying your game files. I've been DRM locked multiple times already just from changing Proton versions and I've only gotten the 24 hour message. Might be best to also try to kill all instances of the game using kill -9 <PID>
(I haven't seen anything WINE related respond to anything other than -9 when it's stuck). You can do ps ax | grep "steam"
to find processes related to Steam. Edit: Also I've got wine-staging installed compared to normal wine. You could try that?
Steam for Linux, Beta
Lenovo Legion Y720
Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8
GPU: NVIDIA GeForce GTX 1060
RAM: 15.6 GB
The distro is Void Linux
Kernel Linux 5.5.11_1 x86_64
i3wm 4.18
NVIDIA driver 440.66.04
Using Proton-5.4-GE-3
Everything is up to date. I never compiled wine nor wine-staging 64bit on my Void. Void Linux only comes with wine-32bit so I depend on the Lutris (I am not using Lutris for Doom Eternal yet) and the proton builds to run wine in 64bit.
Has anyone noticed it hitting the CPU more than games generally do? Doom
doesn't have benchmarks but looking at the in game statistics my CPU maxes
out about the same as my 5700xt does. The gaming system is a R5 3600 with a
light overclock and 16gb 3600mhz ram. Most games run GPU bound on this
setup at ~120FPS @ 1440p. I played doom eternal on 1440p high for a bit
last night and it's running from 120fps to 40fps in game. Totally playable,
it's not bad at all but I'm sure it could be better. Just wondering if the
CPU hit is a proton thing or what, @ 1440p I should be bottlenecked by the
GPU.
On Thu, Mar 26, 2020 at 5:04 PM Ty Qualters notifications@github.com
wrote:
@KaeKun https://github.com/KaeKun I would't suspect DRM to prevent
allocation of video memory. That's more of a system failure. Have you tried
updating your NVIDIA/AMD drivers? What distro are you using etc? I'm not a
Linux pro, but I'd say you should definitely double check all your drivers
and and stuff are up to date. Try verifying your game files. I've been DRM
locked multiple times already just from changing Proton versions and I've
only gotten the 24 hour message. Might be best to also try to kill all
instances of the game using kill -9(I haven't seen anything WINE
related respond to anything other than -9 when it's stuck). You can do ps
ax | grep "steam" to find processes related to Steam.—
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-604685078,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJZQMORZ42ET3EHOGY5AXWTRJO7O5ANCNFSM4LP25FOQ
.
@KaeKun Might be an issue since it's in a laptop and it's a 10-series card. Most people here probably running an RTX 20 series or an AMD card. Looking up the specs of the laptop, it says 6 GB of VRAM and the game allocates ~3GB so that shouldn't be the issue. Could very easily be just another issue with NVIDIA drivers. Considering your'e running Void Linux out of everything, I'm going to assume you don't have a lot of bloat in the background.
I have no issues with the game besides stuttering, so I'm not really sure what's causing that.
For a potentially easier solution, this instruction video by Chris Titus Tech might be worth looking into:
That video is a horrible train wreck of confusing, flawed, and out-right incorrect information. Holy heck man, it actually hurts to watch.
The video is 11 minutes long when it takes < 2 minutes to explain and get things working. The website is a better tutorial than the video. _Install the latest modified Proton with these commands_ and then _copy + paste these launch options_ and then run. Then the video just stretches everything out to 11 minutes with rambling.
I fail to see the relevance of your rambling about his rambling. Running a script and setting some launch options is easier than some of the solutions proposed here and elsewhere, so it might be useful for many.
Proton-5.4-GE-3 runs for me and runs well!
75-100FPS depending on what's going on vs 120FPS on Windows, should be more when I remove the PROTON_LOG=1 launch command, log file is 300+MB!
Have not had any odd graphics/stuttering.
Steam system info: https://gist.githubusercontent.com/zaggynl/62963c4962309f9bbc4bc1d091cdf419/raw/f0bbe2b783e63d62d3b3aea9b378362b08fdafea/gistfile1.txt
Proton log file: steam-782330-zaggynl.log.zip
Launch command: RADV_PERFTEST=llvm PROTON_LOG=1 %command%
Edit: added full Steam info, it didn't complete loading before.
@KaeKun Might be an issue since it's in a laptop and it's a 10-series card. Most people here probably running an RTX 20 series or an AMD card. Looking up the specs of the laptop, it says 6 GB of VRAM and the game allocates ~3GB so that shouldn't be the issue. Could very easily be just another issue with NVIDIA drivers. Considering your'e running Void Linux out of everything, I'm going to assume you don't have a lot of bloat in the background.
I have the exact same laptop(the 1060 has 6GB VRAM), but with arch instead. I can run the DRM-free version(both proton 5.0.4 and GE-3 build), albeit with the RAM issue I mention higher up in this thread.
@zaggynl Does it ever drop below 75fps? I've got a system with a 3900x and 5700xt as well but I moved the 5700xt to my Mediacenter PC which is a 3600 cuz remote play just wasn't cutting it.
So as I posted above I'm seeing ~40-120fps @ 1440p. The drop in frames might be a CPU hit when normally a 3600 and 3900x wouldn't be very far off in a game like doom at 1440p
Short update after further testing:
In case you've just started testing and have an NVIDIA card, in my case the performance in the first few rooms of the first level was horrible (20-25FPS) but improves after the first outside area.
I guess from here I just have to wait for a new NVIDIA driver.
After beating the campaign in Windows, I've had a chance to test again. In Windows, I was getting anywhere from 80 FPS to 140+ FPS.
Hardware:
Software:
Right before the game, I get a warning about my drivers being out of date, but the game launches without issue. Videos seem to play okay. Sign in works okay. In the Battlemode tutorials where there are very few objects, I get 140+ FPS at 1080p. In the Fortress of Doom, I get like 30 FPS average at 1080p. My graphics settings are at Ultra Nightmare with a FOV of 110. Some of the models (like the Slayer standing on the podium in the main menu) almost look blurry to me.
Either way, the progress is impressive from just a week ago.
After beating the campaign in Windows, I've had a chance to test again. In Windows, I was getting anywhere from 80 FPS to 140+ FPS.
Hardware:
- i7-4770
- GTX 1080 ti
- 32GB RAM
Software:
- Fedora 30
- RPMFusion NVIDIA Drivers: 440.64
- Steam Beta Client
- Proton-5.4-GE-3
- Doom Eternal Retail (DRM version)
Right before the game, I get a warning about my drivers being out of date, but the game launches without issue. Videos seem to play okay. Sign in works okay. In the Battlemode tutorials where there are very few objects, I get 140+ FPS at 1080p. In the Fortress of Doom, I get like 30 FPS average at 1080p. My graphics settings are at Ultra Nightmare with a FOV of 110. Some of the models (like the Slayer standing on the podium in the main menu) almost look blurry to me.
Either way, the progress is impressive from just a week ago.
Yeah, I'm seeing really poor performance myself. Game finally runs, but on a 3800X and a 1080Ti, I'm averaging 17-30fps at 1080p universally at 440.64-2 drivers.
Manjaro 5.4.x with Proton-5.4.-GE-3. Seems like Manjaro needs 440.66.0 to improve that performance. Also hopefully Nvidia can look into the driver issue. Performance appears to be crazy bad Nvidia side.
Good news everybody!
Ubuntu 18.04
GeForce GTX 970 (driver 440.64)
i5-4670
16GiB Memory
Proton-5.4-GE-3 (Force the use of a specific Steam Play compatibility tool in Properties)
Doom Eternal via Steam
Launch Options: RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
steamapps/common/DOOMEternal/launcherData/launcher.cfg
setting rgl_minNvidiaDriverVersion 0
disabled the graphics card warning.
/etc/pulse/daemon.conf
setting default-sample-rate = 48000
fixed my crackling sound
And I played an hour with no crashes.
I had to turn graphics down, performance wasn't great, and matches what others have talked about in terms of performance compared to Windows. I always expect a little off the top, but more like 4-5%, not 20-50% difference in frame rates.
I also noticed that when frame rates dropped, so did the gameplay speed, and cinematic scenes. When people were talking to Doomguy, they would often start at the right time, but they spoke faster than the characters were being rendered, so their lips were out of sync.
I also couldn't alt+tab out of the game with out causing the game to get stuck at a black screen, and had to be killed off by process ID (steam couldn't stop the game).
@zaggynl Does it ever drop below 75fps? I've got a system with a 3900x and 5700xt as well but I moved the 5700xt to my Mediacenter PC which is a 3600 cuz remote play just wasn't cutting it.
So as I posted above I'm seeing ~40-120fps @ 1440p. The drop in frames might be a CPU hit when normally a 3600 and 3900x wouldn't be very far off in a game like doom at 1440p
I've only played one map, didn't appear to go below 60FPS, I'll look into better logging.
In addition this was posted on Reddit: https://flightlessmango.com/benchmarks/PqwIAd6zmyc via https://old.reddit.com/r/linux_gaming/comments/fphldf/doom_eternal_benchmark_linux_vs_windows/.
Good news everybody!
Ubuntu 18.04
GeForce GTX 970 (driver 440.64)
i5-4670
16GiB Memory
Proton-5.4-GE-3 (Force the use of a specific Steam Play compatibility tool in Properties)
Doom Eternal via Steam
Launch Options:RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
steamapps/common/DOOMEternal/launcherData/launcher.cfg
settingrgl_minNvidiaDriverVersion 0
disabled the graphics card warning.
/etc/pulse/daemon.conf
settingdefault-sample-rate = 48000
fixed my crackling soundAnd I played an hour with no crashes.
I had to turn graphics down, performance wasn't great, and matches what others have talked about in terms of performance compared to Windows. I always expect a little off the top, but more like 4-5%, not 20-50% difference in frame rates.
I also noticed that when frame rates dropped, so did the gameplay speed, and cinematic scenes. When people were talking to Doomguy, they would often start at the right time, but they spoke faster than the characters were being rendered, so their lips were out of sync.
I also couldn't alt+tab out of the game with out causing the game to get stuck at a black screen, and had to be killed off by process ID (steam couldn't stop the game).
You are with NVIDIA, why RADV_PERFTEST=llvm?
Good news everybody! Ubuntu 18.04 GeForce GTX 970 (driver 440.64) i5-4670 16GiB Memory Proton-5.4-GE-3 (Force the use of a specific Steam Play compatibility tool in Properties) Doom Eternal via Steam Launch Options:
RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
steamapps/common/DOOMEternal/launcherData/launcher.cfg
settingrgl_minNvidiaDriverVersion 0
disabled the graphics card warning./etc/pulse/daemon.conf
settingdefault-sample-rate = 48000
fixed my crackling sound And I played an hour with no crashes. I had to turn graphics down, performance wasn't great, and matches what others have talked about in terms of performance compared to Windows. I always expect a little off the top, but more like 4-5%, not 20-50% difference in frame rates. I also noticed that when frame rates dropped, so did the gameplay speed, and cinematic scenes. When people were talking to Doomguy, they would often start at the right time, but they spoke faster than the characters were being rendered, so their lips were out of sync. I also couldn't alt+tab out of the game with out causing the game to get stuck at a black screen, and had to be killed off by process ID (steam couldn't stop the game).
You are with NVIDIA, why RADV_PERFTEST=llvm?
This issue thread is so dense I imagine it would be easy to get confused.
I have used the launch options from @mozo78 and the performance was still bad when the steam fps counter was enabled. But the game is nicely playable when disabling the steam fps counter.
Btw, some good news, it got a little easier now to run this game:
There was a Steam client update yesterday on its stable channel, so we don't have to use the Steam Beta anymore, only custom Proton :)
One step less. Nice.
You are with NVIDIA, why RADV_PERFTEST=llvm?
I always facepalm when someone suggests Mesa fixes for Nvidia proprietary.
In short Nvidia performance won't improve until there's either there's driver fixes or maybe wine vulkan gets improved to handle whatever vulkan extensions the game devs are using for memory management.
No Man's Sky had the same memory management issue in Proton until Hello Games fixed it, a temp solution was to spoof as AMD with a vulkan layer but that apparently doesn't work in this case.
Anyone got this running using Flathub's flatpak version of steam?
I can select the custom Proton version when placing it in ~/.var/app/com.valvesoftware.Steam/.local/share/Steam/compatibilitytools.d/Proton-5.4-GE-3 but the game will hang on start up (no crash either). I get the warning popup about the missing AMD HDR support and see the "id" logo in systray (and keep seeing it there), but the game does not start nor crash. Cannot end the process through Steam client either.
Using Gentoo Linux, AMD Ryzen 3700X, Radeon 5700XT
@nuku97 I have the same problem and suspect it's due to an outdated vulkan-loader version. Upstream issue reported as https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/989
Edit: It's not quite the same problem as I'm running nVidia but the error message I'm getting in the logs points in that direction, but the SDK should also be the place to look at in your case, as well.
OS: Fedora 32
KERNEL: 5.6.0-0.rc7.git0.2.fc32.x86_64
CPU: AMD Ryzen 7 3700X
GPU: Radeon RX Vega 64
GPU DRIVER: 4.6 Mesa 20.0.2
RAM: 16 GB
Proton 5.4-GE-3
The game won't launch for me either. It shows the HDR warning, I press the 'PLAY' button, then launcher simply crashes. Don't know what else to do.
@simeonoff
On Arch/Manjaro this will work, might not work with Fedora, don't know what the package manager is but if you build these packages however else, it should work I'd assume:
go here:
https://github.com/Tk-Glitch/PKGBUILDS
Build and install "vulkan-headers-git", "vulkan-icd-loader-git", and "amdgpu-pro-vulkan-only"
Then set launch option:
VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json
That is the only option you need. If it doesn't work doublecheck that amd_icd64.json is in that location.
It will work with proton 5.4-GE3 or tkg-5,4-r12, GE3 seems better ATM
OS: Arch, AMD 5600 XT.
The game works fine, but I'm getting strange graphical glitches in mesa and amdgpu-pro. amdvlk doesn't have any glitches, but it hardlocks after a time, and I actually have to reboot my system to bring it back up.
Glitch examples below:
I was getting similar glitches with the exact same setup
@blazini36 Thanks, I prefer to keep my distro clean for stability as it's my work station. Those patches won't work on Fedora as it uses the DNF package manager. But what you're saying is I need the latest vulkan headers, loader, and drivers to get the thing working?
@simeonoff I manage both mesa-git+various patches + updated vulkan + kernel with fsync for fedora on copr as well as vkd3d (for dx12):
https://copr.fedorainfracloud.org/coprs/gloriouseggroll/mesa-aco/
https://copr.fedorainfracloud.org/coprs/gloriouseggroll/kernel/
https://copr.fedorainfracloud.org/coprs/gloriouseggroll/vkd3d/
However they are currently for Fedora 31. I'll see about getting some Fedora 32 builds going.
Edit:
xxmitsu also has some mesa and kernel builds, although his are more vanilla without extra patches if that's what you're looking for. He also seems to have f32 builds up:
https://copr.fedorainfracloud.org/coprs/xxmitsu/kernel-fedora-fsync/
https://copr.fedorainfracloud.org/coprs/xxmitsu/mesa-git/
Afaik you should just need the updated packages from his mesa-git repo, and set RADV_PERFTEST=llvm %command% in the game launch options on steam.
@simeonoff It was pointed out to me that the vulkan packages were updated in the Arch repos. Build dates say the 21st but I dunno, I constantly updated and wasn't seeing above ...132 until 2 days ago, either way they're there now, in Arch at least.
I can't say exactly what you need, I can say I have similar hardware, a 3600/5700xt and a 3900x/5700xt. I pulled my hair out with the same issue as you, I wasn't able to catch definitive ino on it because of the way this thread moves.
Soon as I did what I told you it ran right away, no DRM issues, no long list of launch options (just the one). I suggest you just save the headache and get ahold of Vulkan-icd-loader 1.2.135 and the header for it. then grab the vulkan driver from AMDGPU-pro, you don't need the whole driver. Where you get them is upto you
@GloriousEggroll, thanks, I will try the mesa updates from xxmitsu. The funny thing is I was on Fedora 31 using your mesa-aco but it didn't work with it either. That's why I upgraded to the Beta release, hoping it would solve the issue. Are you guys planning to update the kernel in 32 with the proposed fsync patches?
@blazini36 Thanks, will resort to your suggestion if the updated mesa drivers don't work.
@GloriousEggroll, thanks, I will try the mesa updates from xxmitsu. The funny thing is I was on Fedora 31 using your mesa-aco but it didn't work with it either. That's why I upgraded to the Beta release, hoping it would solve the issue. Are you guys planning to update the kernel in 32 with the proposed fsync patches?
@blazini36 Thanks, will resort to your suggestion if the updated mesa drivers don't work.
@simeonoff yeah my aco repo was configured to use daniel's aco repo directly instead of mesa-git, which is missing some patches required to get doom eternal running. I've actually been in the middle of converting it to use mesa-git with aco auto-enabled as well as some other patches. the kernel i provide is patched with the latest fsync patches that i was informed of from kisak directly, so they should be the latest available
@GloriousEggroll Thanks. After switching to the suggested mesa-git, it now launches. I can confirm with this mesa, the vulkan drivers and launcher update to:
mesa-vulkan-drivers-20.1.0-0.3.20200327.15.07885cb.fc32.i686
mesa-vulkan-drivers-20.1.0-0.3.20200327.15.07885cb.fc32.x86_64
vulkan-loader-1.2.135-20200325.fc32.i686
vulkan-loader-1.2.135-20200325.fc32.x86_64
The sound crackles with your Proton 5.4-GE-3 release. Everything else seems to be working just fine. Thanks for pointing me in the right direction and for all of your work!
Edit:
Lol, got banned for 24 hours by Denuvo for switching from Proton 5.4-GE-3
to Proton-tkg 5.4.r10.g7c7868f4
. Note to self: Don't switch the Steam Play compatibility tool if you don't want to get banned.
You only have 5 tickets per day, and a number of things can consume a ticket such as switching wine/proton builds, windows version reported, kernel, GPU (so indirectly, graphics drivers) etc. It's extremely easy to get locked out.
I think at least for Doom, switching GPUs isn't an issue, thank god.
So just for reference, NVIDIA users are basically locked out pretty much unless NVIDIA updates their drivers or something?
Pretty much.
Well that sucks.
That's what happens with proprietary drivers, when something like this
happens, there's no recourse but to wait.
On Sat, Mar 28, 2020 at 7:05 AM Marisa Kirisame notifications@github.com
wrote:
Well that sucks.
—
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-605431697,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333L7FFUMYFQ5FTSDG3RJXKWBANCNFSM4LP25FOQ
.
So just for reference, NVIDIA users are basically locked out pretty much unless NVIDIA updates their drivers or something?
Yes, we are DOOMED.
So just for reference, NVIDIA users are basically locked out pretty much unless NVIDIA updates their drivers or something?
@FirstZero Well, no.
As I stated in my post about performance on a 1080ti, it does work and is playable... not exactly a stellar experience, but definitely playable. I don't blame you for not seeing the post, this thread has exploded.
Now the fact that a RX460 kicks the 1080ti's ass without breaking a sweat does not detract from the fact that we (well, at least I can) can play Doom Eternal with a Nvidia GPU.
TLDR:
Radeon VII: 3440x1440 everything max, RS off, 100 ish fps
1080ti: 2560x1080, medium, RS off, 40 ish sad fps
Using RADV, here's graphic glitches. They're similar to the amdgpu_pro ones, but different.
It seems like there's an issue with Navi 10 support. The amdgpu_pro setup in the AUR is outdated, so maybe that's the issue there, but I'm running the latest stable mesa, and AFAIK Navi 10 is supported so I dunno what the deal is.
Using RADV, here's graphic glitches. They're similar to the amdgpu_pro ones, but different.
It seems like there's an issue with Navi 10 support. The amdgpu_pro setup in the AUR is outdated, so maybe that's the issue there, but I'm running the latest stable mesa, and AFAIK Navi 10 is supported so I dunno what the deal is.
Try mesa-git, I'm using oibaf ppa on ubuntu, have not run into glitches yet, apart from briefly during resizing.
I moved over to mesa-git. It's running like a dream now
So just for reference, NVIDIA users are basically locked out pretty much unless NVIDIA updates their drivers or something?
@FirstZero Well, no.
As I stated in my post about performance on a 1080ti, it does work and is playable... not exactly a stellar experience, but definitely playable. I don't blame you for not seeing the post, this thread has exploded.
Now the fact that a RX460 kicks the 1080ti's ass without breaking a sweat does not detract from the fact that we _(well, at least I can)_ can play Doom Eternal with a Nvidia GPU.TLDR:
Radeon VII: 3440x1440 everything max, RS off, 100 ish fps
1080ti: 2560x1080, medium, RS off, 40 ish sad fps
<30fps on a 3800X + 1080Ti @ 1080p is not playable at all at any graphics settings.
Since yesterday the game fails to connect to Bethesda.net most of the time.
Sometimes, with some luck, it works.
But most of the time it doesn't.
This is really sad because I get much longer loading screens (because game tries to connect to servers there but I have to wait until it timeouts) and the warning messages because of this interrupt gameplay.
I'm currently using Proton-5.4-GE-3.
Tried everything I could think of. Have re-created the wine-prefix, tried another Proton version (my own tkg build), disabled my hud, removed the start parameters...
I'm out of ideas.
Am I the only one with this problem?
As I said, this started to appear since yesterday. It worked the days before, I played some story with my proton-tkg build without this problem.
So just for reference, NVIDIA users are basically locked out pretty much unless NVIDIA updates their drivers or something?
@FirstZero Well, no.
As I stated in my post about performance on a 1080ti, it does work and is playable... not exactly a stellar experience, but definitely playable. I don't blame you for not seeing the post, this thread has exploded.
Now the fact that a RX460 kicks the 1080ti's ass without breaking a sweat does not detract from the fact that we _(well, at least I can)_ can play Doom Eternal with a Nvidia GPU.
TLDR:
Radeon VII: 3440x1440 everything max, RS off, 100 ish fps
1080ti: 2560x1080, medium, RS off, 40 ish sad fps<30fps on a 3800X + 1080Ti @ 1080p is not playable at all at any graphics settings.
Yes, I'm with 9900K an 1080Ti and I barely can touch 29 FPS. It's definitely not playable.
Long story short, the Nvidia Linux driver (up to 440.64-7) has major issues with Doom Eternal. I'm seeing 40% utilization across all my 16 threads, 100% utilization of my 1080Ti, an 12GB RAM utilization but only 3GB VRAM utilization.
As such, I'm seeing over 300fps in the menus, ~45-50fps at the main menu, and then <20fps in actual gameplay at 1440p Ultra Nightmare, and this does not change whether it's Low or Ultra Nightmare. Based on above, I think what's happening is that instead of dumping all the visual data into VRAM, it's dumping massive amounts of it into standard RAM, and the GPU has to run through the CPU to access that data. There's a whole lot of backforth swapping likely happening, which is cratering the framerate.
Without Doom Eternal running, I average 1-2% CPU, 5-10% GPU, and 2.5GB of RAM. With Doom Eternal, it's 40% @ 16 threads, 100% GPU, 3GB VRAM, and 13.8GB system RAM. It's an Nvidia issue and until they address it, we're basically stuck with an unplayable game. That said, cheers to the Radeon family, glad you guys can rip and tear until it is done.
I had no trouble playing the whole thing from start to end despite constant FPS drops, which at some points caused the game to run at slow motion. I wouldn't really call it unplayable despite all that, but I DEFINITELY would prefer a smoother experience if it can be fixed.
Ok... This is dedicated to my Nvidia brothers and sisters that are struggling right now.
So after about a week of tweaking stuff and trying desperately to squeeze as much performance out of my GTX 1080 as possible on Doom Eternal, while reading and researching everything related to Linux Nvidia setup under the sun, I've managed to get a satisfactory result (and to learn many things along the way).
Lets start by saying that I've been using Linux Mint as my daily driver for the past 18ish months and the quest to get Doom Eternal to run as I want it took me to Manjaro. The sole reason is that its extremely easy to build and install latest version of programs and utilities.
I've started with KDE, but then changed DE to Cinnamon (because im a noob). DEs are playing some role in the process so bare with me.
My system specs right now are:
OS: Manjaro Linux 19.0.2 (KDE >> Cinnamon)
Kernel: 5.5.13-1-MANJARO
CPU: Intel i5-6600K (4) @ 4.400GHz (OC from 3.5GHz)
Memory: 32GB @ 2400MHz
GPU: NVIDIA GeForce GTX 1080 (Driver v440.66.04)
Resolution: 1920x1080@60, 2560x1440@144, 1920x1080@60 (yes, this did made some things a bit tricky)
I will go with the process I've made from the most obvious to the small tweaks.
Needless to say that you should always use the beta version of Steam for Linux gaming.
As of right now, Proton-5.4-GE-3
is the best option for Doom Eternal. Not great, not terrible. I'm keeping an eye for new releases to test.
Initial test runs were under v440.64 Nvidia driver. Later I found out about the Vulkan 1.2 Developer Beta Driver - Driver v440.66.04 from - https://developer.nvidia.com/vulkan-driver
Then it was time to start messing around with the xorg config.
I had some prior knowledge (bad experience) from trying setup a 3 monitor layout using nvidia-settings
on Cinnamon Mint so no problem... this didn't really go as intended.
Then I discovered a treasure trove of knowledge:
https://wiki.manjaro.org/index.php/Configure_Graphics_Cards
https://wiki.archlinux.org/index.php?title=NVIDIA/Tips_and_tricks
First I properly learned how to use nvidia-settings
and how to point it to the proper config file I've made for it using:
sudo mhwd-gpu --setmod nvidia --setxorg /etc/X11/mhwd.d/nvidia.conf
(If you dont have mhwd-gpu
on your distro, I believe nvidia-xconfig
with the default path/file being /etc/X11/xorg.conf
, does the same.)
Then came the good part - the config itself.
I'll spare you the finer things and stick to the important stuff that are located in the Section "Device"
part of the config, which is what you need to focus on and add some lines to:
Option "Coolbits" "31"
- Unlocks all the power, performance and overclocking Nvidia features.
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
- Forces the "Powermizer" to use max performance mode and forces the clocks to operate @ 100% value. (Don't worry, it does not mean that your GPU will be utilized 100% at all times.)
It should look something like this:
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 1080"
Option "Coolbits" "31"
Option "RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
EndSection
Also, add a Module
section with the following modules like this:
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Now go to to nvidia-settings
-> "OpenGL Settings" and set "Image Settings" to "High Performance". (you can enable API indicators if you REALLY want to.)
Then go to the most bottom item "nvidia-settings Configuration" and click on "Save Current Configuration" button. that will create .nvidia-settings-rc
file. Its important to save it on the default location that is at the $HOME
directory.
To make these settings persistent after login, add the line nvidia-settings --load-config-only
to your ~/.xinitrc
file. (if for some reason you don't have that file in your home directory, check man nvidia-settings
for alternative methods.)
Sudo save -> restart for xorg.conf changes to take effect.
I suggest installing GreenWithEnvy
. This is a good tool to set a good and aggressive fan curve for your card and even overclocking and TDP changes.
Also it provides very useful info.
https://gitlab.com/leinardi/gwe
https://aur.archlinux.org/packages/gwe
GWE relies on the "Coolbits" "31"
option mentioned above and will not function w/o it.
Notice that "GPU%" and "Mem ctrl%" are showing 0% while the Current clocks are at their 100% range. This is a sensor bug that caused by us forcing the clocks to operate at 100% with "RegistryDwords"
option. This has nothing to do with GWE, you will see other sensor programs reporting 0%. You may consider that as 100%.
I strongly suggest setting up a fan curve here.
Here is also where you may do some overclocking. I'm using some stable values that I found over the years messing around with my card and this setting works for me w/o issue.
Next, we go to the kernel.
Sudo create /etc/modprobe.d/nvidia.conf
(if you don't already got it) and add options nvidia NVreg_UsePageAttributeTable=1
to it.
You may read about Page Attribute Table (PAT) here:
https://wiki.gentoo.org/wiki/NVIDIA/nvidia-drivers#Kernel_module_parameters
https://wiki.archlinux.org/index.php/NVIDIA/Tips_and_tricks#Kernel_module_parameters
Important to note that you should enable this option only if your CPU supports PAT. To check if it supports it, type cat /proc/cpuinfo | grep pat
Sudo save and restart for the kernel modules to load with the option.
Now lets talk about the sound issue and my speculation why I don't experience it.
I'm using a program called PulseEffects and I route all my sound through it. Nothing special with the config really... just enabled some filters. Everything out of the box. I speculate that it may be the reason why the sound works great on Doom Eternal for me.
https://github.com/wwmm/pulseeffects
This is a really powerful toy.
Steam launch options:
MANGOHUD=1 RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
Taken from https://www.christitus.com/doom-eternal-linux
To disable "Install driver" warning at game startup, go to:
.steam/steam/steamapps/common/DOOMEternal/launcherData/launcher.cfg
and change rgl_minNvidiaDriverVersion
to 0.
A good performance overlay I use - MangoHud:
https://github.com/flightlessmango/MangoHud
Looks great and ain't covering game hud like the game's performance metric.
Find a way to disable your DE's compositor. In Cinnamon there is an option to disable compositor for full screen programs in "System settings" -> "General". A compositor can really tank performance.
And... that's it. I hope that I didn't forgot anything.
Right from the get go I noticed a huge decrease in CPU and noticed my VRAM utilizes a lot more then before. Still not perfect mind you, but A LOT better.
Right now I'm @ 60FPS solid on high settings @ 1080p.
I would like to thank manjaro-chroot
and timeshift
for being my closest friends during this process :D
I wrote this post primarily to show all your 2080ti owners that you can do better and to save you a lot of time figuring this out.
Hope I helped.
Reap and tear, until it is done!
WWG1WGA,
Daniel
Thank you for your efforts but it doesn't help at all :(
@danielgul
man xorg.conf:
The “extmod”, “dbe”, “dri”, “dri2”, “glx”, and “record” extension modules are loaded automatically, if they are present, unless disabled with "Disable" entries.
To see what extension modules are available, check the extensions subdirectory under:
/usr/lib/xorg/modules
So why put freetype, type1 in there? Some might not have it.
Can't you set PowerMizer in nvidia-settings?
like with cmdline: nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1
(to set to performance)
No need to set it globally, just when you need it.
Why advise everyone to use tripple buffering? Might not what ppl want.
"RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
Option "EXAPixmaps" "off"
Couldn't find any reference to these in the nvidia driver README. Where did you get that from?
You might just be lucky regarding sound. In the commits of Proton-GE after v.3, libfaudio was reverted to stable, as of some users had problems. It might help, as others mentioned, to just increase the default sample-rate in pulseaudio.
@everyone
I didn't find a way to view the current nvidia module parameters, anyone knows?
Regarding Flathub's flatpak version of Steam vs. Gentoo's steam-overlay:
@e-user I think the issue you linked might not be the (only) problem for flatpak"s version and was meanwhile fixed, as stated in the comment by @valentindavid . At least for me, vulkan based games such as Doom (2016) work again. Still, Doom Eternal does not work for me in Flatpak-Steam, even when using the Proton from @GloriousEggroll .
However, meanwhile, I got Doom Eternal working with a non-flatpak Steam installation. For me, it started working after installing the latest Mesa from git. (Other packages I have installed: llvm-10.0.0 and llvm-9.0.1, vulkan-headers-1.2.135 , media-libs/vulkan-loader-1.2.135, Proton-5.4-GE-3, and Steam from Gentoo's steam-overlay with disabled USE flag "-steamruntime". According to Doom Eternal's performance data overlay, the game is using radv, llvm 9.0.1 and mesa 20.1.0-devel, vulkan 1.2.128). I get about 60-70 fps on my Ryzen 3700X and Radeon 5700XT in 2560×1440 (WQHD) resolution with everything set to Ultra Nightmare details. I also tried amdvlk driver as alternative to Mesa"s vulkan drivers, but with that driver the game crashes on startup for me. Ss, this is sill less than half of the fps I get under my dual boot windows, but still I am surprised it is already running this good at this point of time. I wonder if there is an easy way to install mesa-git on flatpak - maybe @valentindavid has a clue for me (tried _flatpak install org.freedesktop.Platform.GL.mesa-git_ after seeing this package name somewhere, but it doesn't find a package to install), that might help to get the gaming running in flathub's steam package?
@nuku97 I have the same problem and suspect it's due to an outdated vulkan-loader version. Upstream issue reported as https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/989
Edit: It's not _quite_ the same problem as I'm running nVidia but the error message I'm getting in the logs points in that direction, but the SDK should also be the place to look at in your case, as well.
Game launches and works with Proton 5.4 GE-3, Vulkan Loader 1.2.135 and Nvidia drivers 440.66.04 Beta. But FPS is low, 25-50 fps on low graphics settings. How to increase it? Anyone Nvidia holders have the same issue?
@EldarAgalarov if you read the thread, nVidia drivers seem to have a problem where those cards are using system RAM instead of the onboard GPU memory. This is probably something only nVidia can fix, since their drivers are closed-source and proprietary.
@danielgul
man xorg.conf:The “extmod”, “dbe”, “dri”, “dri2”, “glx”, and “record” extension modules are loaded automatically, if they are present, unless disabled with "Disable" entries.
To see what extension modules are available, check the extensions subdirectory under:
/usr/lib/xorg/modulesSo why put freetype, type1 in there? Some might not have it.
@AllKind this section was generated after I installed the beta 440.66.04 driver.
I believe that this is needed to be explicitly included considering that this is a beta driver.
Can't you set PowerMizer in nvidia-settings?
like with cmdline:nvidia-settings -a [gpu:0]/GPUPowerMizerMode=1
(to set to performance)
No need to set it globally, just when you need it.
@AllKind nvidia-settings powermizer options work like crap. cli doesn't seem to take any effects on the clocks and if you did manage to make it work, its not persistent after boot.
Including "RegistryDwords" to your xorg.conf makes sure it does what is needed and don't decide to save power when you need it most.
Why advise everyone to use tripple buffering? Might not what ppl want.
@AllKind You are right. I included an example from my config to show how people may include the options into the device section. I removed the extra stuff so people wont get confused.
Triplebuffer and EXAPixmaps are there to help me eliminate screen tearing and artifacts in the compositor and have nothing to do with the topic.
"RegistryDwords" "PowerMizerEnable=0x1; PerfLevelSrc=0x2222; PowerMizerDefault=0x1; PowerMizerDefaultAC=0x1"
Option "EXAPixmaps" "off"
Couldn't find any reference to these in the nvidia driver README. Where did you get that from?
You might just be lucky regarding sound. In the commits of Proton-GE after v.3, libfaudio was reverted to stable, as of some users had problems. It might help, as others mentioned, to just increase the default sample-rate in pulseaudio.
@AllKind The readme and man pages for nvidia-setttings, nvidia-xconfig, xorg-conf, etc are lacking a lot of the information and options that are available to say the least...
You may read on the topic here:
https://askubuntu.com/questions/379483/nvidia-x-server-settings-lost-on-every-reboot
https://forums.opensuse.org/showthread.php/410089-nvidia-powermizer-how-tweak
And also refer to the many links I provided on my post above for more info.
You also probably right regarding the sound issue that I was lucky. As I said before, I didn't do anything special or intentional to make the sound work great, I'm just using PulseEffects.
@everyone
I didn't find a way to view the current nvidia module parameters, anyone knows?
@AllKind You may check for available module params for nvidia with sudo modinfo -p nvidia
.
To check nvidia module configuration use sudo modprobe -c | grep nvidia
.
More info here: https://wiki.archlinux.org/index.php/Kernel_module
I would be interested to know which of the modules loaded to the kernal actually have "glx" "dbe" etc loaded to them. All I can see is "nvidia", "nvidia_drm" and "nvidia_modeset".
I am seeing the "NVreg_UsePageAttributeTable=1" option added to the module configuration though.
If anyone can clarify, It would be appreciated.
@mozo78
Yes, I'm with 9900K an 1080Ti and I barely can touch 29 FPS. It's definitely not playable.
Thank you for your efforts but it doesn't help at all :(
That's upsetting and I'm sorry to hear that...
If you can clarify what you are doing and which distro you are running, maybe I can help.
WWG1WGA,
Daniel
P.s It would be great if more people could report if they tried anything I talked about and how it went.
And if you also in the quest to max performance for Doom Eternal with nvidia card and found out something interesting that could be done. Thanks.
Don't worry mate, I'll wait NVIDIA to fix things :)
Hey all,
I just wanted to see if anyone else has experienced crashes when viewing the Rune menu, and intermittent crashes on loading screens? The game otherwise runs perfectly. Trying to gauge if this issue is just a me problem.
https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-605543105
If nothing else, I'll use some of the tools you've highlighted. Those seem like massive QoL benefits, can't say no to that.
Has anyone tried this with an AMD card using RADV? I'm running Arch with Mesa 20.0.2. I see that I'll have to use LLVM instead of ACO, but some more info on the current state with Proton-GE and Mesa would be much appreciated. I'm not too keen on moving away from Mesa anytime soon.
@sonic2kk I used it for a bit. The performance sucks but I found it generally more stable
People with audio / sound crackling issues, this fixed it for me:
Configure /etc/pulse/daemon.conf to have the following settings:
default-sample-format = s32le
default-sample-rate = 48000
alternate-sample-rate = 44100
I also installed re-installed faudio via protontricks but that did not fix it. Mentioning it in case it's the combination that does it.
Not sure it was posted before, but nVidia reacted to the low performance report in their forums, stating they would look into it. Let's hope the number of active Linux users is significant enough for them to make it a business decision to support this.
Has anyone tried this with an AMD card using RADV? I'm running Arch with Mesa 20.0.2. I see that I'll have to use LLVM instead of ACO, but some more info on the current state with Proton-GE and Mesa would be much appreciated. I'm not too keen on moving away from Mesa anytime soon.
There are multiple post about how to use RADV with LLVM me included.
I still use proton-tkg with the patch from @999eagle or you can just use the build she uploaded, for more information see this post.
There are also multiple post about how to use amdgpu-pros vulkan driver without installing it system wide (you can literally just add a environment variable to steams launch options and load the driver only for doom eternal)
If you use an older AMD gpu ( GCN 1.0/1.1) you will need to use mesa-git.
@sonic2kk Both ACO and LLVM ARE RADV. RADV is mesa's vulkan-radeon
driver, which can be run with either LLVM, or ACO, using RADV_PERFTEST=llvm
or RADV_PERFTEST=aco
. But BOTH of those are in fact RADV. So I'm not sure what you're even asking/wondering. As @elovin said, you can use vulkan-amdgpu-pro
and not "leave mesa behind," because they can live together on your system quite easily, unlike radeonsi and amdgpu-pro-libgl
. You don't have to install it system-wide at all if you don't want, but installing it system-wide doesn't mean leaving mesa behind either.
Hey all,
I just wanted to see if anyone else has experienced crashes when viewing the Rune menu, and intermittent crashes on loading screens? The game otherwise runs perfectly. Trying to gauge if this issue is just a me problem.
Following up on my above post: if anyone were to have these errors, you can correct them by clearing out the files in DOOMEternal/base/video/runes and DOOMEternal/base/video/tutorials. Game runs flawlessly now and no longer crashes. Seems as though something in one or two of those bk2 files did not agree with my system.
It does not appear to be an issue with proton, so I wanted to clear the air.
@EldarAgalarov if you read the thread, nVidia drivers seem to have a problem where those cards are using system RAM instead of the onboard GPU memory. This is probably something only nVidia can fix, since their drivers are closed-source and proprietary.
This statement is totally true, I was able to confirm it while playing by having htop open and nvidia-smi watched. The nvidia driver is not properly allocating vram to the game and is using a portion of my ram as a buffer of some kind. Here is a screenshot of the game running, I couldn't get an in game screenshot as the game paused when I tried to run a command in my WM.
My cpu utilization is basically non existent and the nvidia driver is only allocating 760 Megs... I have the game set to ultra as well to test it. It looks like the steam overlay is using more ram than the game... So yeah, nvidia has to fix this problem.
System Stats:
So, is anything being done about making ACO compiler work or improving performance with RADV?
So, is anything being done about making ACO compiler work or improving performance with RADV?
I really wonder if this would dramatically improve performance or if the bottleneck is somewhere else. E.g. in my radv setup with radeon 5700xt I get about 70 fps, no matter if the quality is set to ultra nightmare or low. In windows I get about 140 fps.
@nuku97 And you get basically ~140fps with amdgpu-pro on linux.
@Progman-DT Yes it's being worked on. The missing features for ACO are still WIP. There are two MRs that when combined can give up to 30% perf gains with RADV/LLVM already.
Nvidia has just released a driver update to address the issue:
https://developer.nvidia.com/vulkan-driver
April 1st, 2020 - Windows 442.86, Linux 440.66.07
New:
Multi thread-capable deferred ray tracing pipeline creation
Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces [Linux]
Fixes:
Added a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory [Linux]
Correctly cap the drawCount for vkCmdDrawIndirectCount and vkCmdDrawIndexedIndirectCount on Turing GPUs
Fixed descriptor indexing with large arrays and large blocks
Pacman distro users can grab it from here: https://github.com/Frogging-Family/nvidia-all
Finally!!!
It's fixed:
Huzzah :D
Can confirm with the 440.66.07 driver I am now getting 144 fps locked pretty much
system Arch Linux
CPU AMD RYZEN 2700x
GPU NVIDIA RTX 2070
48GB DDR 4 3200
driver version 440.66.07
Sick! Now we're just waiting for Valve to release the proton patch directly from Steam, right?
Yep, 144+FPS @ 1440p Ultra Nightmare with the 440.66.07 driver
Ryzen 3700x, RTX 2080, xubuntu 19.10, Proton-5.4-GE-3
Alt-tab in fullscreen still breaks the game but in borderless window it works. Steam overlay still has a big impact on performance (down to 80-100 FPS)
Sick! Now we're just waiting for Valve to release the proton patch directly from Steam, right?
Yes, and I would expect it any day now. Time between proton releases is typically 10-14 days.
Is anyone else still getting stuttering on AMD cards?
@jalabb Popups (volume, achievements, etc) still break the game for me even though the game is set to borderless. Is there another fix I can try?
Updated Nvidia drivers to 440.66.07 beta. And now game works great with stable 60 FPS on nightmare graphics settings on GTX 1060 6GB.
Nvidia has just released a driver update to address the issue:
https://developer.nvidia.com/vulkan-driverApril 1st, 2020 - Windows 442.86, Linux 440.66.07 New: Multi thread-capable deferred ray tracing pipeline creation Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces [Linux] Fixes: Added a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory [Linux] Correctly cap the drawCount for vkCmdDrawIndirectCount and vkCmdDrawIndexedIndirectCount on Turing GPUs Fixed descriptor indexing with large arrays and large blocks
Pacman distro users can grab it from here: https://github.com/Frogging-Family/nvidia-all
Just tried installing it _manually_ from the distro. This was a massive mistake. Anyone who considers going down that path for Manjaro, don't do this; it borks everything. Spent the last 45 minutes praying that I didn't have to reinstall Manjaro. Looks like I didn't. If you ain't super tech savvy and terminal savvy, I guess wait until 440.66.07 comes down through the package manager.
That said, @Tk-Glitch: thanks for the update!
@PraetorianSC4 What do you mean you tried installing it manually "from the
distro"? Where did you get it, and what did you do?
On Wed, Apr 1, 2020 at 7:34 PM PraetorianSC4 notifications@github.com
wrote:
Nvidia has just released a driver update to address the issue:
https://developer.nvidia.com/vulkan-driverApril 1st, 2020 - Windows 442.86, Linux 440.66.07
New: Multi thread-capable deferred ray tracing pipeline creation Allow presenting from queue families which only expose VK_QUEUE_COMPUTE_BIT when using XCB in addition to Xlib surfaces [Linux] Fixes: Added a workaround for Linux Steam Play title DOOM Eternal, which overrides application requested memory locations, to ensure performance-critical resources be placed in video memory [Linux] Correctly cap the drawCount for vkCmdDrawIndirectCount and vkCmdDrawIndexedIndirectCount on Turing GPUs Fixed descriptor indexing with large arrays and large blocks
Pacman distro users can grab it from here:
https://github.com/Frogging-Family/nvidia-allJust tried installing it manually from the distro. This was a massive
mistake. Anyone who considers going down that path for Manjaro, don't do
this; it borks everything. Spent the last 45 minutes praying that I didn't
have to reinstall Manjaro. Looks like I didn't. If you ain't super tech
savvy and terminal savvy, I guess wait until 440.66.07 comes down through
the package manager.That said, @Tk-Glitch https://github.com/Tk-Glitch: thanks for the
update!—
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-607540558,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33ZARWY56YNKOTGYTXDRKPFQLANCNFSM4LP25FOQ
.
@sonic2kk Both ACO and LLVM _ARE_ RADV. RADV is mesa's
vulkan-radeon
driver, which can be run with either LLVM, or ACO, usingRADV_PERFTEST=llvm
orRADV_PERFTEST=aco
. But BOTH of those are in fact RADV. So I'm not sure what you're even asking/wondering. As @elovin said, you can usevulkan-amdgpu-pro
and not "leave mesa behind," because they can live together on your system quite easily, unlike radeonsi andamdgpu-pro-libgl
. You don't have to install it system-wide at all if you don't want, but installing it system-wide doesn't mean leaving mesa behind either.
I was being specific, I am aware that they are RADV. What I meant by not leaving Mesa behind is that I'd rather not use a proprietary driver of any kind. Shame to hear Mesa doesn't perform quite as well, here's hoping those patches for ACO that were mentioned make a difference!
I downloaded and installed the NVIDIA driver from https://developer.nvidia.com/vulkan-beta-4406607-linux
Void Linux.
installed with sudo sh NVIDIA-Linux-x86_64-440.66.07.run
First try: lxdm would not start. (keeps trying and failing)
So I removed /etc/X11/xorg.conf, an uninstalled
sudo sh NVIDIA-Linux-x86_64-440.66.07.run --uninstall
I installed it again, and this time it allowed it to create its own xorg.conf
Then modified it with the info from lspci | grep VGA following the instructions from https://wiki.voidlinux.org/Proprietary_Video_Drivers
And it worked :)
"Working" on my computer means that lxdm login screen is a black screen, but I can still enter my user and password pressing the right keys. Because of authorization reasons my x cannot show anything until my user is logged in. I just didn't see the need to fix that :p
Doom is working well now, around 100 FPS.
I also can confirm that the NVIDIA-Linux-x86_64-440.66.07.run has resolved the performance issues, it's not an April fools.
I had issues installing, using the UI software tool uninstalled the current Nividia drivers, upon reboot I had no UI.
I tried installing the new driver but got the error "The kernel header file ..... does not exists".
To solve this after a reboot, ctrl,alt,F6 to login via CLI. Then ran pacman -S linux-headers and selected linux-55 for my kernel version (uname -r).
This is for Manjaro.
I could then install the new Nivida drivers.
sudo sh NVIDIA-Linux-x86_64-440.66.07.run
Cheers
I get the driver out of date window and then the game crashes with a new Ubuntu and Steam install, using Proton-5.4-GE-3. Everything works fine on my other PC.
Distro: Ubuntu 18.04
Kernel: 5.3.0-45
GPU: RTX 2080 SUPER
Driver: 440.64
CPU: Ryzen 9 3900X
RAM: DDR4 3200MHz 64GB
Log snippet
3778.856:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\MSIMG32.dll" at 0x6afc0000: PE builtin
3778.856:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\OLEACC.dll" at 0x950000: PE builtin
3778.857:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\gdiplus.dll" at 0x6f480000: PE builtin
3778.871:0030:0031:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7fd7ff890000: builtin
3779.003:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-synch-l1-2-0.dll" at 0x6e340000: PE builtin
3779.003:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-fibers-l1-1-1.dll" at 0x6b880000: PE builtin
3779.006:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-localization-l1-2-1.dll" at 0xf20000: PE builtin
3779.010:0030:0031:fixme:font:get_outline_text_metrics failed to read full_nameW for font L"Ani"!
3779.025:0030:0031:fixme:heap:RtlSetHeapInformation 0x10000 0 0x92d480 4 stub
3779.048:0030:0031:warn:debugstr:OutputDebugStringA "Winsock Initialized\n"
3779.048:0030:0031:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b00fdce ip=7b00fdce tid=0031
3779.048:0030:0031:trace:seh:raise_exception info[0]=0000000000000015
3779.048:0030:0031:trace:seh:raise_exception info[1]=0000000000925390
3779.048:0030:0031:trace:seh:raise_exception rax=0000000000924db0 rbx=00007fffffea8000 rcx=0000000000924d90 rdx=0000000000000000
3779.048:0030:0031:trace:seh:raise_exception rsi=0000000000924e90 rdi=0000000000924dc0 rbp=00000000009251d0 rsp=0000000000924d70
3779.048:0030:0031:trace:seh:raise_exception r8=0000000000000002 r9=0000000000924e80 r10=6b636f736e695722 r11=0000000000000000
3779.048:0030:0031:trace:seh:raise_exception r12=0000000000000001 r13=0000000000000001 r14=00000001409939e8 r15=000000000092d428
3779.048:0030:0031:trace:seh:RtlVirtualUnwind type 1 rip 7b00fdce rsp 924d70
3779.048:0030:0031:trace:seh:dump_unwind_info **** func fd80-fe07
3779.048:0030:0031:trace:seh:dump_unwind_info unwind info at 0x7b08e344 flags 0 prolog 0x11 bytes function 0x7b00fd80-0x7b00fe07
3779.048:0030:0031:trace:seh:dump_unwind_info 0x11: subq $0xc8,%rsp
3779.048:0030:0031:trace:seh:dump_unwind_info 0xa: pushq %rsi
3779.048:0030:0031:trace:seh:dump_unwind_info 0x9: pushq %rdi
3779.048:0030:0031:trace:seh:dwarf_virtual_unwind function 7b439c71 base 0x7b439a28 cie 0x7b490710 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
People with audio / sound crackling issues, this fixed it for me:
Configure /etc/pulse/daemon.conf to have the following settings:
default-sample-format = s32le default-sample-rate = 48000 alternate-sample-rate = 44100
I also installed re-installed faudio via protontricks but that did not fix it. Mentioning it in case it's the combination that does it.
@mixedCase Can you please explain how you re-installed faudio via protontricks? Thank you
I downloaded and installed the NVIDIA driver from https://developer.nvidia.com/vulkan-beta-4406607-linux
Void Linux.
installed withsudo sh NVIDIA-Linux-x86_64-440.66.07.run
First try: lxdm would not start. (keeps trying and failing)
So I removed /etc/X11/xorg.conf, an uninstalled
sudo sh NVIDIA-Linux-x86_64-440.66.07.run --uninstall
I installed it again, and this time it allowed it to create its own xorg.conf
Then modified it with the info from lspci | grep VGA following the instructions from https://wiki.voidlinux.org/Proprietary_Video_DriversAnd it worked :)
"Working" on my computer means that lxdm login screen is a black screen, but I can still enter my user and password pressing the right keys. Because of authorization reasons my x cannot show anything until my user is logged in. I just didn't see the need to fix that :pDoom is working well now, around 100 FPS.
@gardotd426 see above is what I did. Except I rolled back to 440.64 stable, while our champ here pushed forward and got it working.
One final point, you'll need linux##-headers (## being your kernel version: 4.9 = 49, 5.4 = 54, and so on) to install the latest drivers. If you don't want to tinker and deal with your ssdm or lxdm with xorg crashing after driver reboot, wait for stable release of the drivers after community testing and all that. Else, above is the path to success.
Confirmed! 100-150 fps @ 1440p on Ultra Nightmare settings with GTX 1080 with the new 440.66.07 driver!
This game is actually fun now :D
RIP AND TEAR!!!
Anybody else is getting a crash after picking up the second shotgun upgrade? Then tutorial pops up and the game freezes. At least the drivers fixed the fps.
@PraetorianSC4 It's pretty simple, really. From my readme:
git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
Then follow the prompts and replace existing packages by the new ones when asked. That's basically all there is to it.
If you want to go back to your distro-provided packages, just install them through mhwd, pacman, or any pacman GUI frontend of your choice, and replace the -tkg packages when prompted. Simple.
If anyone needs Fedora RPMs for the working beta drivers, please ping me and I'll try to publish them to COPR.
@e-user that would be awesome!
Turns out nVidia drivers are on the list of forbidden items for COPR.
Long story short, you can grab the Fedora nVidia RPMs from my Google Drive, instead.
@jalabb Popups (volume, achievements, etc) still break the game for me even though the game is set to borderless. Is there another fix I can try?
@75AngryDucks It's not really a solution, but I'd just deactivate any popup until the issue is resolved. For the achievement popups, deactivating the steam overlay should stop them from apprearing [EDIT : it doesn't]. Volume on the other hand, I don't know, that's specific to your desktop I guess. Maybe try another Proton version to see if it helps (vanilla 5.0-5 vs 5.3-GE-3 for example)
[EDIT] I'm using XFCE4 (Xubuntu) and achievement/volume popups don't crash the game.
Turns out nVidia drivers are on the list of forbidden items for COPR.
Long story short, you can grab the Fedora nVidia RPMs from my Google Drive, instead.
That's unfortunate, but thanks for sharing the files.
I just had a perfect run, one hour of 60FPS (triple-buffered vsync) on nightmare graphics settings, crackling sound gone after patching up pulse.conf - however I couldn't start the game anymore after that, so I'm suspecting I've triggered Denuvo's five strike per 24h ban.
Dear Valve team, if you're reading this, could you please help us get the Denuvo situation fixed?
@jalabb for me disabling the steam overlay doesn't disable achievements popups
also alt-tabbing doesn't work unless I use a lower resolution so that the window doens't fill up the entire screen(in borderless)
Managed to get a fair bit of info on how this game's doing so far. Great job so far with getting this working!
Distribution: Arch Linux
GPU: nVidia GTX 1660 Super
Driver/LLVM version: nvidia 440.66.07
Kernel version: 5.5.13-zen2-1-zen
Proton version: 5.4-GE-3
Desktop Environment: KDE 5.18.4.1
Running default exe with denuovo.
First up, audio:
People with audio / sound crackling issues, this fixed it for me:
Configure /etc/pulse/daemon.conf to have the following settings:
default-sample-format = s32le default-sample-rate = 48000 alternate-sample-rate = 44100
s32le wasn't necessary, setting the sample rate to 48khz is the important part. Unfortunately I use the external soundcard/amp Soundblaster E1 which can only run at 44.1khz. I was still able to workaround this however...
Regarding stability: The game will need to be in window mode if I want to be able to alt tab without the game locking up. Something seems off about the whole window implementation in general: When I set the game to window mode 1280x720 it still presented the window as covering most of the 2560x1440 screen with a border at the top. When I set the resolution lower, the game froze.
Edit: Game also froze when right clicking border and setting to fullscreen that way. Game also freezes when any other dialog overlays on fullscreen as other users have experienced.
Regarding performance: feels identical to windows now, perfect! Disabling the steam overlay improves the performance as well (same as in Windows 10), would highly recommend trying it.
I just had a perfect run, one hour of 60FPS (triple-buffered vsync) on nightmare graphics settings, crackling sound gone after patching up pulse.conf - however I couldn't start the game anymore after that, so I'm suspecting I've triggered Denuvo's five strike per 24h ban.
I had this issue with GE proton with a different game, starting it up too many times using it would require me to wait 24 hrs. But I haven't had this problem on GE with Doom Eternal despite restarting it many times (albeit after the game froze). I'm not entirely sure why....
@jalabb The volume popup is specific to my DE, but I can get around that by setting volume ingame. Disabling the steam overlay doesn't stop achievement popups, so currently my game crashes every time I get an achievement.
@PraetorianSC4 It's pretty simple, really. From my readme:
git clone https://github.com/Frogging-Family/nvidia-all.git cd nvidia-all makepkg -si
Then follow the prompts and replace existing packages by the new ones when asked. That's basically all there is to it.
If you want to go back to your distro-provided packages, just install them through mhwd, pacman, or any pacman GUI frontend of your choice, and replace the -tkg packages when prompted. Simple.
@Tk-Glitch
I actually did just that. In my case, it led to a gpu blackscreen after reboot. The driver process recommends running mkinitcpio -p after the install is done. This in turn also leads to xorg breaking. I wasn't aware that xorg would break after a driver update as @KaeKun and @grand248 pointed out. As such, to return to a stable state, I rolled back. I'm on Manjaro 5.4 unlike @grand248 who is on 5.5. I don't think the kernel version matters as long as the headers are correct.
I'll give it another shot later today and follow up.
@Waistless: seems like the Vulkan fullscreen extension is conflicting with the linux and windows DE compositors in some way?
@FTL-Space-Warp @75AngryDucks Yes I got an achievement and it did pop up even with the overlay off, but it did not crash the game. I edited my original comment. It could be a problem specific to your DE, people earlier in the thread reported issues with Gnome but XFCE4 works fine for me.
I'm not an expert in any way shape or form, but it could be compositing, XFCE has much lighter compositing than GNOME, if any at all.
EDIT: compositing should be turned off automatically though, maybe it gets switched on for a moment or something weird like that
@jalabb I'm using Manjaro KDE Plasma, and mine crashes.
@MagicRB Is there a way to force compositing off during gameplay? I can give that a try and report back.
@75AngryDucks as I said if you're using steam and/or proton-ge it should be off already and I have no idea how it works on GNOME, I've never used GNOME. But you seem to be running KDE, on KDE the shortcut is Alt+Shift+F12 to toggle compositing.
@PraetorianSC4 5.4? The probable issue here is that 5.4 was built with an earlier version of GCC than what you currently have system-wide, so your modules don't get built due to GCC mismatch. mkinitcpio -P
has exactly zero reason to break Xorg directly as it's completely unrelated and also being run each time you install a kernel update, and here again, the likely issue is the one above. Multiple Manjaro users running 5.5/5.6 have had no issue, which helps that assumption.
Edit: A log of the issue would certainly help figuring it out.
I managed to launch the game using Steam Beta and Proton-5.4-GE-3, however I see all kinds of graphical glitches on almost all surfaces. Does anyone know how to fix these? I have a RX 580. According to mesa-overlay I get a steady 60-80FPS on all Ultra settings, so the game is definitely playable, but I was wondering if that is already the maximum?
@MagicRB Toggling compositing immediately breaks the game. I also tested using window rules to force compositing off, but it still crashed the next time I got an achievement. I could try changing DEs, but I saw that it could cause conflicts. If there's a way to cleanly switch them I could give xfce4 a try.
Not really, maybe if you managed to install a really minimal instance of XFCE but I don't recommend it, leave it to someone else.
I found a temporary hack to disable steam notifications
Within $HOME/.local/share/Steam/resource/styles/steam.styles
Change Notifications.Stacksize "3" to "0". Then restart steam.
Fast tested by turning on steam input for all controllers, then plugging in my xbox one controller. With this hack it no longer popups a controller profile loaded notification on the bottom right.
Hope that helps you guys rip & tear until this gets fixed :)
@Tk-Glitch You were right, amdgpu-pro is significantly faster than radv. Unfortunatly it took a while to figure out How to install amdgpu-pro on Gentoo for use with Doom Eternal so here is a short guide for everyone else:
Download amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz from https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt
Unpack: tar xvfJ amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz
Unpack the Vulkan drivers deb file for 64bit: ar x vulkan-amdgpu-pro_19.50-967956_amd64.deb
Unpack the data.tar.xz file which was inside the deb file: tar xvfJ data.tar.xz
Move the extracted folder opt/amdgpu-pro from the archive to /opt/amdgpu-pro
Start steam with the following command: VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json /usr/bin/steam (alternativly you can probably add the environment variable to Doom Eternal launch options inside steam) in order to use the amdgpu-pro vulkan driver instead of the default mesa radv driver. Through the performance overlay of Doom Eternal you can confirm it is using the correct driver (will say amd driver instead of mesa).
Note: I use 64bit Gentoo, with mostly stable packages except mesa -9999 (git), steam from steam-overlay with disabled USE "-steamruntime" and beta client updates, Proton-5.4-GE-3. Hardware Ryzen 3700X with Radeon 5700XT
@nuku97 And you get basically ~140fps with amdgpu-pro on linux.
@Progman-DT Yes it's being worked on. The missing features for ACO are still WIP. There are two MRs that when combined can give up to 30% perf gains with RADV/LLVM already.
Finally:
resample-method = speex-float-5
default-sample-format = s24le
default-sample-rate = 48000
alternate-sample-rate = 44100
default-fragments = 2
default-fragment-size-msec = 125
Game runs perfect, no graphic glitches, no crackling sound, 180-250 FPS on Full-HD and Graphic settings to high. (RTX2060, Ryzen 1700, 16GB RAM, Fedora 31)
When can we expect 440.66 version to be pushed to the stable release?
Probably never. 445 series is more likely to be the first stable release to contain the fix.
Any idea if this is a question of weeks or months?
I tried to install it manually, but it broke my system and had to revert. I'm just wondering if it is worth trying again.
OS: Manjaro Linux x86_64
Kernel: 5.6.0-rc1-1-tkg-pds
WM : i3 (no compositor)
CPU: AMD Ryzen 5 2600 (12) @ 3.400GHz
GPU: AMD ATI Radeon RX590
Mesa-git 20.1.0_devel.121255.b93a1952258-1
I've got like 20 fps, can't really tell because MANGOHUD doesn't work. I also tried amdgpu-pro, I've followed @nuku97 instructions but it doesn't seem to make any difference. I tried Proton-5.4-GE-3 and Proton-tkg-5.5. Any ideas why ? It seems like people on rx580 or rx590 get very good performance. I'm also on a rather small resolution, 1200x900 (CRT monitor), though I tried 1080p and there's no difference.
My launch options are:
MANGOHUD=1 STEAM_RUNTIME=1 RADV_PERFTEST=llvm VK_ICD_FILENAMES=/opt/amdgpu-pro/etc/vulkan/icd.d/amd_icd64.json PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
@Tk-Glitch The vulkan beta driver fails to install through dkms on latest linux 5.6.2-5-tkg I built. 440.64 seems to install fine however.
5.5.14 with 440.66.07 works fine though.
@AllKind @Tk-Glitch Driver confirmed working on 5.6.xx with the recently pushed commit to nvidia-all
@Waistless This worked for me. It didn't actually fix the problem, but it let me go through and get the rest of the singleplayer achievements, so now I can replay it with no issues.
@nuku97 Thanks for chipping in :) That definitely helped me extract the most out of my GPU with this game. Those instructions worked well for Fedora 32. All I need to figure out now is how to enable FreeSync.
As far as I understand there's no way to get FreeSync working with the mesa drivers. I have to use proprietary drivers.
@d3rhans
* Pulseaudio settings changed to:
resample-method = speex-float-5
default-sample-format = s24le
default-sample-rate = 48000
alternate-sample-rate = 44100
default-fragments = 2
default-fragment-size-msec = 125
I'm still getting crackling sound on Fedora 31, independent of my Pulseaudio settings, but only every other boot of the game or so. Do you get consistent good results with these settings every time you boot up the game?
And why should the resample method matter, did you get those settings from somewhere else?
Question:
+com_skipSignInManager 1
option but what does it do? from the naming i would assume it skips the bethesda login, but it does not for me - i always have to wait for the client to connect to somethingmy first launch had no audio issues but now every other launch is full of crackling sounds which makes it unplayable, any idea how to dig deeper into this sound issue?
ive tried both pulseaudio configurations without good results
@e-user @evilch3n When you run pacmd list-sinks
does "sample spec" for your default audio device (that DE uses at launch) show the sample rate as 44100hz or 48000hz?
From my experience, when I launch the game with the default device set to 44100hz, it always crackles even when I change default device.
When I launch the game on a 48000hz device it doesn't crackle and I can then change the default sound device and it will remain uncrackled. Some sound cards such as my external Soundblaster E1 can't run at 48000hz so I have to use that workaround.
I didn't change the default sample format or any other settings. Only the default sample rate to 48000hz and alt sample to 44100 (so it does 48k when possible).
Perhaps there's an easier way such as forcing Doom Eternal to run at 48000hz, or is this issue to do with pulseaudio resampling?
This will give very different results depending on hardware. There's no be all end all setting for Pulseaudio. If you're one of the unlucky to experience Pulseaudio-induced crackling issues, you'll have to find settings that work for your specific hardware. Copy/pasting settings that work on different hardware blindly will not necessarily help at all, and could eventually make things much worse.
A wrong default-fragment-size-msec
value, notably, can make crackling unbearable.
So remember to make backups before playing with PA 🐸
I noticed my built in audio had more sample rate options in Win 10, so I tried them out here by forcing them through pulse daemon conf.
Using ONLY: (substituting relevant values)
default-sample-rate = 48000
alternate-sample-rate = 48000
Tested by restarting pulseaudio service and socket, verifying changes were accepted using
pacmd list-sinks
44100: Crackle
48000: Fine
96000: Crackle
192000: Crackle
avoid-resampling = true
with all other options default (44.1khz, 48khz alternative) still had cracklingI'm not sure there's any more definitive way to prove Doom Eternal under Wine/Proton doesn't like any audio sample rate other than 48Khz. Tweaking any other pulseaudio options shouldn't be needed.
To confirm the right settings have applied:
pacmd list-sinks
Your default audio should read:
sample spec: s16le 2ch 48000Hz
@Waistless
pacmd list-sinks | grep "ample"
sample spec: s24le 2ch 44100Hz
sample spec: s16le 2ch 48000Hz
sample spec: s32le 2ch 48000Hz
:man_shrugging:
@evilch3n Grep alone doesn't show everything, there'll be multiple devices listed. From that listing it shows one of your audio devices can't run at 48Khz, assuming you've forced default-sample-rate = 48000
and alternate-sample-rate = 48000
(which you should attempt first to try and get all devices at 48k)
If that device happens to be the default that you are using, you'll need to use the work around of starting up Doom Eternal with a 48khz device set to default, then change default to the 44.1khz device.
This situation is why I suggested there should be a way to have Doom Eternal to be forced to startup at 48Khz and let Pulseaudio handle resampling, but I'm not sure such a command exists outside of hard coding proton/wine to handle it that way.
@Waistless thanks for the infos,
i can confirm no crackling with 48000 for everything
I had the game was working great yesterday with the new nvidia driver, but today it just crashes to desktop the moment i start it. I get a black screen for a second, then it closes. removing +com_skipIntroVideo 1 from the launch options replaces the black screen with the first second of the intro video, but it doesn't change anything else. Adding PROTON_LOG=1 to the launch options didn't seem to generate a log. Does anyone have any idea what's going on? I'm using manjaro KDE and GloriousEggroll's version of proton, in case its relevant. trying other versions of proton didn't fix it.
Edit: it's suddenly working after a reboot.
@sidok LOL, I was going to tell you to try rebooting.
I have the same problem. It works some times, then it stops. I think it stops after putting my computer to sleep. Or if I close steam. I don't know yet because I didn't try to troubleshoot it I just reboot because I just want to play.
Anyone else with the same problem?
Void Linux, Linux 5.5.14_1, i3 window manager, Lenovo Legion Y720, Quad Core Intel Core i7-7700HQ, Nvidia GeForce GTX 1060
Running GloriusEggroll's Proton GE-3 too. No parameters at all added.
@KaeKun Only times I've had these issues are when:
sleep 10s &&
before autostart command fixes thisSorry if that's dragging the issue a bit off topic, but hope that helps
@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.
I ended up using the AMDVLK Debian/Ubuntu package from https://github.com/GPUOpen-Drivers/AMDVLK/releases and changed my launch config to reference VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json
@sidok LOL, I was going to tell you to try rebooting.
I have the same problem. It works some times, then it stops. I think it stops after putting my computer to sleep. Or if I close steam. I don't know yet because I didn't try to troubleshoot it I just reboot because I just want to play.
Anyone else with the same problem?
Void Linux, Linux 5.5.14_1, i3 window manager, Lenovo Legion Y720, Quad Core Intel Core i7-7700HQ, Nvidia GeForce GTX 1060
Running GloriusEggroll's Proton GE-3 too. No parameters at all added.
Facing the same issue, I tried restarting steam app, just in case
Now will see if it works after relogging
Did not have this issue with distro version. Might get back to it.
Fyi, related Bug over at mesa radv development tracker
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2684#note_455985
Hello, with the latest Nvidia Vulkan beta drivers, the game runs smooth (considering my rig) in windowed mode on low.
However, I am experiencing a crash when recovering the first rune in the second level. It might be linked with a embedded movie playing. A quick glimpse in the logs mention an HAVOK utility failing to launch but I don't know if this is the root cause.
System: Linux 5.5.13-arch1-1
CPU: Amd Ryzen 2700X
16 Go RAM
GPU: Nvidia GTX 960
Drivers: 440.66.07
Proton log is here: https://we.tl/t-UbFe0fWrMo
For anyone running Ubuntu 18.04 with Linux kernel 5.3.0, I've found this to finally make it work: https://www.protondb.com/app/412020#_8gOCAMdq
Before that, I would get a segfault even with all the tweaks in this thread. After adding the option and rebooting, the game just worked. System:
Context: for kernels <5.4, you need to add clearcpuid=514
to the kernel boot options: https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4-UMIP-Spoofing
@GirardR1006 If you disable tutorials in the in-game menu does the crash disappear?
@teotomic thanks for that. Disabling the umip
instruction fixed all of my other Denuvo games but for some reason Doom Eternal is still not working. I'll wait for the 440.66 drivers to get pushed to stable.
Here's the Proton issue tracking kernel 5.3 and Ryzen 3xxx CPUs: issue 2927
Hey guys, I'm at my wit's end here and I could use some help.
Here's my system specs:
Vulkan-Loader
, but vulkaninfo
just won't recognize them.I had run the game successfully with good performance before, but I had to format my laptop because I messed up something else and I couldn't fix it. So I'm on a clean install, except for the issues above.
Here's an excerpt from my Proton logs:
89.589:002f:0035:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:0036:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:0038:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:0039:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:003b:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:003c:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
89.589:002f:0035:trace:seh:RtlVirtualUnwind type 1 rip 1403973c0 rsp 4a7ffe8
89.589:002f:0035:trace:seh:dump_unwind_info **** func 3973c0-397424
89.589:002f:0035:trace:seh:dump_unwind_info unwind info at 0x14317336c flags 0 prolog 0xa bytes function 0x1403973c0-0x140397424
89.589:002f:0035:trace:seh:dump_unwind_info 0xa: movq %rbx,0x38(%rsp)
89.589:002f:0035:trace:seh:dump_unwind_info 0xa: subq $0x20,%rsp
89.589:002f:0035:trace:seh:dump_unwind_info 0x6: pushq %rdi
89.589:002f:0036:trace:seh:RtlVirtualUnwind type 1 rip 1403973c0 rsp 528ffe8
89.589:002f:0036:trace:seh:dump_unwind_info **** func 3973c0-397424
89.589:002f:0036:trace:seh:dump_unwind_info unwind info at 0x14317336c flags 0 prolog 0xa bytes function 0x1403973c0-0x140397424
89.589:002f:0036:trace:seh:dump_unwind_info 0xa: movq %rbx,0x38(%rsp)
89.589:002f:0036:trace:seh:dump_unwind_info 0xa: subq $0x20,%rsp
89.589:002f:0036:trace:seh:dump_unwind_info 0x6: pushq %rdi
89.589:002f:003d:trace:seh:call_teb_handler handler at 0x7bd0d2c0 returned 1
Unhandled exception: divide by zero in 64-bit code (0x00007f45e757d33d).
89.602:005e:005f:fixme:dbghelp:elf_search_auxv can't find symbol in module
Register dump:
rip:00007f45e757d33d rsp:0000000004a70e50 rbp:0000000004a71320 eflags:00010246 ( R- -- I Z- -P- )
rax:0000000000000100 rbx:0000000000000000 rcx:00007f45ec0008de rdx:0000000000000000
rsi:000000007da5bbb8 rdi:0000000000000000 r8:0000000000000000 r9:00007f45ec005180 r10:0000000004a71270
r11:0000000000000007 r12:0000000004a71250 r13:0000000000008080 r14:000000000000000a r15:0000000000000000
Stack dump:
0x0000000004a70e50: 0000000000000000 0000000004a7c758
0x0000000004a70e60: 0000000000000001 ffffffffffffff90
0x0000000004a70e70: 0000000004a71190 0000000004a7c740
0x0000000004a70e80: 00007f45ec1dd8d0 00007f45ec0d8a30
0x0000000004a70e90: 00007f45ec005140 00007f45ec17e080
0x0000000004a70ea0: 00007f45ec005170 000000007d86bd10
0x0000000004a70eb0: 0000000000000003 0000000000000080
0x0000000004a70ec0: 000000007da5bbb8 000000007da5bba0
0x0000000004a70ed0: 0000000000000000 0000000000000000
0x0000000004a70ee0: 0000000000000000 000000770000007c
0x0000000004a70ef0: 0000005b0000006e 00007f45e77a2472
0x0000000004a70f00: 00007f45e77a20f0 00007f45ec4c3ad0
Backtrace:
=>0 0x00007f45e757d33d in libvulkan_intel.so (+0xa633d) (0x0000000004a71320)
0x00007f45e757d33d: idivl %edi,%eax
I have no idea what's going on, other than it could be related to Vulkan because of the backtrace. What should I look into?
Hello @thebozzcl, since the backtrace points at libvulkan_intel.so and you're trying to use the nVidia proprietary driver, you could try avoiding the Intel vulkan driver entirely with something like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json" %command%
in the game's launch options.
@kisak-valve thanks for the suggestion! Unfortunately it didn't work, I'm getting the same error. I wonder why the game insists on using the Intel Vulkan driver.
EDIT: I just realized I missed the "V" when copying the launch options that @kisak-valve provided. Who knows, it might have worked. Instead, I took the hard route and re-installed the whole OS, then installed Vulkan from its repositories and the nVidia 440.66.07 drivers. I got it to work again, thankfully.
Here's exactly what I did, in case somebody needs to know:
Vulkan-Headers
, Vulkan-Loader
and Vulkan-Tools
from their repos. If this works, you should be able to see version 1.2.136 when you run vulkaninfo | less
.sudo apt-get build-dep libvulkan1 && sudo apt-get install cmake
to install any dependencies you would need.sudo apt-get install libglvnd-dev
.CTRL-ALT-F3
(or some other F key).sudo apt-get purge nvidia* && sudo apt-get autoremove
(CAREFUL, look closely at what these commands are trying to uninstall)sudo service gdm stop
or whatever desktop manager you're using. Type CTRL-ALT-F3
or whatever again to go back to your terminal instance.nvidia-drm
is unloaded by running sudo modprobe -r nvidia_drm
.chmod +x ./NVIDIA-[whatever].run && sudo ./NVIDIA-[whatever].run
. During the install, I installed both the 32-bit binaries and the DKMS module. DO NOT UPDATE THE X11 CONFIGURATION, at least for me that broke my system on reboot.nvidia-smi
. At least for me, it detected the new drivers right away. It might also say there's a mismatch, but I think that only happens if you don't purge the old drivers beforehand.sudo ./NVIDIA-[whatever].run --uninstall
), check /etc/X11
for changes (files backed up by nVidia, for example) and undo those changes.Sorry for the wall of text, but I'm a Linux noob and I hope something like this could help somebody else.
@GirardR1006 If you disable tutorials in the in-game menu does the crash disappear?
Yes it still crashes, the tutorial window is not in cause here. Rather, it is the window showing runes choice that makes the game crash.
@GirardR1006 I'm running a very similar setup and wasn't able to reproduce the issue on that rune or another rune. The crash log says it's Faudio related, so all I could suggest is toggling different audio settings i.e speaker <> headphone mixing, disabling open voice chat etc. I've tried everything related to that to reproduce, but no dice.
GE-5.5 and Proton 5.0-6 RC were released today so you could give those a try. Think I'll put that through some testing as well see if its fixed any current issues.
If all else fails could you post the results of pacmd list-sources > pa.txt
(just upload the resulting pa.txt in the home directory). If anyone else gets the exact same crash maybe there's something specific setting it off.
So, the issue of the game suddenly locking up with a black screen when alt-tabbing or changing resolution / switching between windowed/fullscreen is still a thing.
Other than that, with the 440.66.08 drivers and proton 5.0-6 I've noticed a monumental improvement in performance, being able to maintain 60 FPS even on the highest settings (excluding texture pool size, my 1060 doesn't have enough VRAM).
I've seen the benchmarks showing that it performs better than on Windows now, but I didn't think it would make such a difference.
Edit: I used to have audio stuttering before, but with the perf improvements it's all gone, so it may just have been excessive cpu load (my poor i5-6400...)
Proton 5.0-6 RC and 5.5-GE-1 behave identically to 5.4-GE-3 for me.
Still need to start game with 48Khz audio to prevent crackling, and the fullscreen alt-tab freezing remains.
Wasn't able to reproduce a rune crash on any version.
@kisak-valve - I wanted to point out that the "hey its working!" reports on Proton DB are generally following into two camps:
For some of us on Ubuntu 19.10 with an AMD GPU, we cannot get a compatible libvulkan1 (the icd loader) as it is at 1.1.114.0 and the upcoming LTS (20.04) is at 1.2.131.2. The Oibaf PPA, which usually pulls from Git, still doesn't have a 1.2.135 or better Vulkan package. I even thought about grabbing the .deb files manually from Debian unstable, but they are also locked at 1.2.131.2. Don't forget that the Mesa version shipping with 20.04 will be locked to an older version for 6 months.
So with even Ubuntu 20.04 LTS missing minimum requirements to get DOOM Eternal running, what is the best method on getting us suport? Do we start putting these drivers into Proton releases, Steam runtimes, or some other better method? Do we try to get the Ubuntu team to update their Vulkan driver before the 20.04 release even if Debian unstable doesn't have it yet?
Somebody previously posted this:
https://pastebin.com/gjzLKV7V
I don't know if it works for I use Arch.
Somebody previously posted this:
https://pastebin.com/gjzLKV7VI don't know if it works for I use Arch.
If you go to https://packages.lunarg.com/vulkan/ it looks like the maximum version is 1.2.131. so I am still in the same boat. Btw, I created a bootable USB for Manjaro 19.02 and I am so close to making the switch away from Ubuntu. It has been fine the past few years, but it is way too out of date and when the new version releases on April 23rd, I'm still going to be in the same boat.
Ubuntu is nice if you want to build a Docker image or run a server, but for gaming, it is really difficult.
EDIT: 1.2.135 may be tucked in there in the testing area, so I may give it a shot. I'm still pondering on switching away though.
I tried the command and had to change the URL:
sudo wget -qO /etc/apt/sources.list.d/lunarg-vulkan-testing-bionic.list https://packages.lunarg.com/vulkan/testing/lunarg-vulkan-testing-bionic.list
but it had the potential to mess with the system so I stopped for now:
1 package can be upgraded. Run 'apt list --upgradable' to see it.
N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://packages.lunarg.com/vulkan/testing'
The following packages will be REMOVED:
libgl1:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386 libglx-mesa0:i386 libglx0:i386 libvulkan1:i386
mesa-vulkan-drivers:i386 steam:i386
The following packages will be upgraded:
libvulkan1
1 upgraded, 0 newly installed, 8 to remove and 0 not upgraded.
@btegs if that doesn't work, building Vulkan from the repos is not hard.
https://github.com/KhronosGroup/Vulkan-Headers
https://github.com/KhronosGroup/Vulkan-Loader
https://github.com/KhronosGroup/Vulkan-Tools
Before you start, try running sudo apt-get build-dep libvulkan1
in case you're missing any dependencies. Each repo has instructions on how to build, but they all will be very similar:
git clone https://github.com/KhronosGroup/Vulkan-$something.git
cd Vulkan-$something
mkdir build
cd build
../scripts/update_deps.sh # Not all of them have this, IIRC
cmake ..
make
sudo make install
EDIT: also, in case it helps, I listed everything I had to do to get this to run in my case in this comment: https://github.com/ValveSoftware/Proton/issues/3654#issuecomment-609094355
@btegs if that doesn't work, building Vulkan from the repos is not hard.
https://github.com/KhronosGroup/Vulkan-Headers
https://github.com/KhronosGroup/Vulkan-Loader
https://github.com/KhronosGroup/Vulkan-ToolsBefore you start, try running
sudo apt-get build-dep libvulkan1
in case you're missing any dependencies. Each repo has instructions on how to build, but they all will be very similar:git clone https://github.com/KhronosGroup/Vulkan-$something.git cd Vulkan-$something mkdir build cd build ../scripts/update_deps.sh # Not all of them have this, IIRC cmake .. make sudo make install
EDIT: also, in case it helps, I listed everything I had to do to get this to run in my case in this comment: #3654 (comment)
Thanks for the feedback. Since I am using an AMD GPU and everything is tied to MESA for the drivers, I was getting that warning about my MESA package being removed. I suppose your case is different due to the Nvidia drivers not tied to the base MESA package and are more isolated.
@btegs if that doesn't work, building Vulkan from the repos is not hard.
https://github.com/KhronosGroup/Vulkan-Headers
https://github.com/KhronosGroup/Vulkan-Loader
https://github.com/KhronosGroup/Vulkan-Tools
Before you start, try runningsudo apt-get build-dep libvulkan1
in case you're missing any dependencies. Each repo has instructions on how to build, but they all will be very similar:git clone https://github.com/KhronosGroup/Vulkan-$something.git cd Vulkan-$something mkdir build cd build ../scripts/update_deps.sh # Not all of them have this, IIRC cmake .. make sudo make install
EDIT: also, in case it helps, I listed everything I had to do to get this to run in my case in this comment: #3654 (comment)
Thanks for the feedback. Since I am using an AMD GPU and everything is tied to MESA for the drivers, I was getting that warning about my MESA package being removed. I suppose your case is different due to the Nvidia drivers not tied to the base MESA package and are more isolated.
Oh yeah, I missed that part of your post. Sorry it didn't help.
I notice that some people have mentioned issues with Alt+Tab, but I have found one which is slightly different to those that have been mentioned.
When I press Alt+Tab during gameplay, and then go back into the game, the tab key is no longer recognised. This doesn't happen with any other games. I can fix it by switching between fullscreen/borderless/windowed mode, but then the next time I press Alt+Tab again, the problem comes back again.
Hello Proton maintainers!
Doom Eternal runs well with Proton 5.0-6 RC testing.
Played one level without noticing problems in gameplay.
Alt+Tab though is giving problems. As soon I want to go back to the game, all I get is a black screen.
Need to end the game by process manager.
System:
Linux Mint 19.3 (Ubuntu 18.04) with cinnamon Desktop (compositing off for fullscreen).
Force Composition Pipeline is set to off in nvidia-settings.
Kernel: 5.5.14
Nvidia RTX 2080 Ti with driver 440.66.07
Proton log:
https://drive.google.com/open?id=1AKaOhfGmLf7oGTEOGYvvba0vMGwZ9FZU
All I did for the log was: start the game, go to continue campain, Alt+Tab, Alt+Tab back, end process.
Update: need to reset all my game graphics settings, when switching between Proton versions (also applies to Wolfenstein II).
@GirardR1006 I'm running a very similar setup and wasn't able to reproduce the issue on that rune or another rune. The crash log says it's Faudio related, so all I could suggest is toggling different audio settings i.e speaker <> headphone mixing, disabling open voice chat etc. I've tried everything related to that to reproduce, but no dice.
GE-5.5 and Proton 5.0-6 RC were released today so you could give those a try. Think I'll put that through some testing as well see if its fixed any current issues.
If all else fails could you post the results of
pacmd list-sources > pa.txt
(just upload the resulting pa.txt in the home directory). If anyone else gets the exact same crash maybe there's something specific setting it off.
thank your for suggesting GE custom proton build, the issue seems to have disappeared when using 5.5-GE1!
When I press Alt+Tab during gameplay, and then go back into the game, the tab key is no longer recognised. [...] I can fix it by switching between fullscreen/borderless/windowed mode, but then the next time I press Alt+Tab again, the problem comes back again.
@SuperMatt I have noticed this as well, for me pressing Alt to bring up current objectives gets the Tab key working again.
If I map the menu to something else it works everything single time with no issue though I have seen the Tab issue.
So in other words it's as if the game is assuming that the alt key is constantly depressed. That's useful to know. Maybe re-mapping the alt key so that it is no longer the current objective, it might fix things.
I can't figure out why it's happening, but on the Urdak level, I'm getting a hard crash of my computer. The game will freeze up and I have to reboot. When I reboot, systemd drops me into an emergency shell, but it says it can't access tty and I can't type. I can fix it if I run the recovery boot option in rEFInd, where it will say it's recovering my journal.
@PopeRigby I am having a similar issue on "Destroy The Super Gore Nest". I'm not convinced my issue is dependent on the level. I also do not get dropped into an emergency shell. I do have to press the hard reboot on my tower. Another strange thing I noticed was that while the game was frozen so was the back light on my CAPS LOCK key.
I was trying to look through my systemd logs but I couldn't find the error it showed me.
hum... Mine just dropped me to my desktop just now.
I'm running a Radeon 5600XT and mesa-git started having graphical corruption issues, so I moved back to Mesa 20.0.4, which doesn't have any graphical issues, but the game occasionally totally locks. Unlike earlier hardlocks I can usually SSH in and kill the process, but it's a weird issue nonetheless. It might be similar to the issues you're encountering.
Since I didn't experience it so much in mesa-git, it might be fixed in the next stable release... we can only hope.
Nvidia just released 440.82 stable driver meaning the beta vulkan driver is not needed anymore to play.
Arch Linux has it packaged already.
This may help some with audio problems.
If you have protontricks installed you can tell wine to use alsa instead of pulseaudio.
protontricks 782330 sound=alsa
@TheGreatMcPain guess thats a neat trick :)
But also this could help: https://github.com/ValveSoftware/Proton/issues/3721#issuecomment-610593779
For me any resize of the game window causes the freeze (the window stays black after that), I think we can include Alt+Tab to this. It also freezes if any window appears on top of the game window, including Steam notifications (about new messages or received collectible cards). The last line in the log (on window resizing) says: Flushing device resizeSwapChain: true, resizeViewDest: false, resizeImageNeedsFlush: false
. I use Awesome WM so I can switch the window to fullscreen and back with just keyboard shortcuts.
@AllKind Interesting, I wonder if that would help DOOM 2016's sound issues where if your sound card's sample rate was different from 44.1K or 48K the audio would be a jarbled mess.
Although, this happens in Windows too.
I am using the new stable NVIDIA driver (440.82) and need to report that it has not fixed my crashing issue. I am also using the beta [next] 5.0-5 version of Proton.
On another note: is there a way to view a list of Doom Eternal 's previous updates? When I click _"View Doom eternal update history"_ the most recent one listed is March 24th.
Just ran the game on arch with new stable NVIDIA driver (440.82) using the Proton-5.5-GE-1 package. Game ran fairly well, a few minor stutters every now and then but the game is now playable.
I did notice the dynamic resolution was a little lower than when running it on windows too but overall it is very playable now.
Edit: Took my launcher options out as it looks like they have a few typos in them.
My specs are: the latest NVIDIA driver 440.82, GTX 1070, i7-7700k, Debian testing, Proton 5.5-GE-1. After setting the launch parameters to +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
I'm able to play the game and it's smooth as butter but these freezes are easily reproducible and inevitable. The easiest way to trigger the freeze is to switch to windowed mode from fullscreen (and back if it doesn't happen right away). It's like any invalidation of the window makes it stop rendering (the sound keeps playing). Be it resizing or covering the window with something else, a desktop or Steam notification. So I thinkg the safest way to play is to launch Steam in offline mode and close the browser, messenger etc. so that nothing suddenly pops up.
Running the game in offline mode isn't necessary, if you want online features you can edit $HOME/.steam/steam/resource/styles/steam.styles:
Change Notifications.Stacksize "3" to "0", then restart Steam.
My specs are: the latest NVIDIA driver 440.82, GTX 1070, i7-7700k, Debian testing, Proton 5.5-GE-1. After setting the launch parameters to +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1 I'm able to play the game and it's smooth as butter but these freezes are easily reproducible and inevitable. The easiest way to trigger the freeze is to switch to windowed mode from fullscreen (and back if it doesn't happen right away). It's like any invalidation of the window makes it stop rendering (the sound keeps playing). Be it resizing or covering the window with something else, a desktop or Steam notification. So I thinkg the safest way to play is to launch Steam in offline mode and close the browser, messenger etc. so that nothing suddenly pops up.
I confirm that this is also happening to me. Same GPU and software.
Running the game in offline mode isn't necessary, if you want online features you can edit $HOME/.steam/steam/resource/styles/steam.styles:
Change Notifications.Stacksize "3" to "0", then restart Steam
I confirm that this has fixed the issue for me.
Here's my Proton log. I started the game in Windowed mode, went to settings (not even loading the save) switched to fullscreen (nothing visually changed but the window occupied the entire screen area before that already) and then back to Windowed. At that point the window went black but the music continued playing. I had to kill the game process manually after that.
Considering how easy it is to reproduce it must be something trivial. Doesn't mean it would be trivial to fix of course.
This line looks suspicious in particular:
116929.314:0033:0036:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
For other tinkers like myself, the log makes more sense after filtering it through grep -v seh
. This message is indeed related to the issue (not necessarily it's the culprit but looks like it is), from MSDN description:
Sent when the window background must be erased (for example, when a window is resized). The message is sent to prepare an invalidated portion of a window for painting.
And that's exactly what happens, either resize or erasure after another window covers the game's one. This fixme is ancient, there are results in Google from 2008. Maybe it's time to finally do what it asks :smile:
I read the Wine source a bit. So this message originates from pack_message
function that serializes the window message for interprocess communication: https://github.com/wine-mirror/wine/blob/a98ca88dd1139ad8e16e63fbb349c2fc5e9ad332/dlls/user32/message.c#L757
Since WM_ERASEBKGND isn't supported it's not sent. My speculation is that Doom relies on this message to restart the renderer after the window resize or any other external interference and it never arrives so the renderer gets suspended indefinitely. I think it shouldn't be hard to implement this looking at the other examples nearby and this particular message is less complex than WM_CREATE for example. However, if it wasn't implemented for at least 12 years now it could be much harder than it seems. Let's hope it's just that no one cared enough until now.
Another test with the Proton I compiled myself resulted in no WM_ERASEBKGND fixme lines so this theory may be not correct. I resized the window manually using a WM hotkey and it froze as usual. But there were no related messages in the log. Looks like they only appear if I change the window size from the options.
My specs are: the latest NVIDIA driver 440.82, GTX 1070 ti, R5 3600x, Ubuntu 18.04, Proton 5.5-GE-1. When I try to launch DE, I get the pop up below. Any ideas to fix this is greatly appreciated.
@chanakaya just press Play, it should launch normally.
@rkfg Already tried that...It just exits :(
@chanakaya then check the logs, try to launch it with PROTON_LOG=1 %command% +in_terminal 1 +com_skipIntroVideo 1 +com_skipKeyPressOnLoadScreens 1 +com_skipSignInManager 1
and look in ~/steam-782330.log
for clues.
@chanakaya it's possible you hit the Denuvo (drm - copyright protection). Did you start the game more than 5 times? You migh just need to wait 24 hours.
Some1 way above in that thread posted the exact error. If you find that (might take a day haha), you could compare that to your proton log.
The newest official proton release candidate contains a drm fix (I don't think that's already in 5.5-GE-1). https://github.com/ValveSoftware/Proton/issues/3721
Btw: you can disable the driver warning in the launcher.cfg (how to is posted a dozen times in this thread).
Btw: you can disable the driver warning in the launcher.cfg (how to is posted a dozen times in this thread).
Offtopic: might not be that easy considering this wonderful GitHub "feature":
How to load all the comments and/or search them?
EDIT: found this extension, install and Alt+Click this button to load 200 comments instead of 60. A bit better but I'd prefer good old pagination and proper search instead.
I see a lot of comments here saying to use Vulkan 1.2... I have nvidia 440.82 drivers installed and vulkan info claims Instance Version is 1.2.131, but when I run with Proton 5.4GE3 the performance stats in doom claim that i'm still on Vulkan 1.1.119. Is there a launch option I should be adding to force it to use 1.2?
@giblitz Vulkan-loader 1.2... Is only required to launch the game, so if it runs then you should be good to go, but if you really want 1.2 you'd need the nvidia vulkan beta drivers.
Hi there!
I have been playing the game with the AMD-PRO drivers for a few days now and it runs great, but for some reason Battlemode doesn't work on Linux for me, I also tried on a Windows VM, and there it gets to a match just fine, is there any workaround for this?
My config:
OS: Solus 4.1 (I disabled the Steam Linux Integration, so Steam would use the bundled runtime for the newest vulkan header/loader)
GPU: RX 5700 XT (Mesa 19.3.4)
Proton Version: 5.5-GE-1 (Also tried with 5.4-GE-3)
Launch Options: VK_ICD_FILENAMES=/home/jojo/Documents/Drivers/AMDGPU-PRO/amd_icd64.json gamemoderun %command% +com_skipIntroVideo 1
@zKhrona does it also freeze with black screen for you when you resize the window or if another window appears in front of it? I wonder if it's a driver issue or Wine's.
@rkfg I have no experience at all in this, but I remember early in the thread people mentioned that wine currently doesn't have true support for VK_EXT_full_screen_exclusive, only workarounds. Could that be what's causing the issue?
@rkfg Luckily it doesn't, I saw some people talking about this issue here, but mine resizes through the menu just fine. I'm not able to alt tab the game, but changing workspaces work, even tho the mouse is still hooked to the game, so I can't use it. I don't know if the fullscreen issue is related to driver, but it could be working on mine because I'm using the PRO drivers.
Wine log from my hang just by switching virtual desktops away and then back.
Really hope it can be resolved, it's by far the most impactful bug remaining in this game
@75AngryDucks I think no because it happens when I just resize the game window that's already in the windowed mode, not fullscreen.
@zKhrona Does it work both ways to windowed and back if you do it several times? If yes then it really could be an NVIDIA driver issue I think.
After playing the game more, I found that I can move my mouse outside the game's window if I'm in a menu in either a mission or the Fortress of Doom and change workspaces to access my Desktop, as alt tab doesn't work for me even on Windowed mode. Unfortunately Battlemode is still not working for me, every time I try to find a match the game just say it can't find any. On Windows it works normally.
@rkfg I tried changing the resolution and screen ratio multiple times, seems to be working fine for me, it freezes for 2 or 3 seconds upon changing it, but that's all.
@zKhrona Great, thanks for checking it. Then it's likely not a Wine issue at all. On a side note, I made a makeshift patch for that WM_ERASEBKGND message and all it did was remove the fixme
lines in the log, the freeze itself wasn't fixed. Anyway, was worth a try. The issue is probably on the driver side.
After lurking in this thread since the day the game dropped, I can finally report success as I've finally played my first couple of hours of DOOM Eternal on Linux. Important to note is that unlike most of people in this thread I've bought the game from Bethesda.net, not from Steam, which complicates things quite a bit.
Configuration:
OS: Ubuntu 18.04
GPU: NVIDIA Quadro RTX 4000 (inside a Thinkpad P53)
My minimal configuration walkthrough:
vulkan-loader
via https://packages.lunarg.com/ to the latest 1.2.x. This is crucial if you are not playing on Steam.proton_dist.tar.gz
inside it gets unpacked to dist
, which is what Lutris is looking for. Otherwise, Lutris won't see the runner. It you are brave, you can unpack this tar.gz
yourself, just peek where other Proton versions have put their dist
directories. helper.sh
trick).+in_terminal 1 +com_skipIntroVideo 1 +com_skipSignInManager 1
, +com_skipIntroVideo
being the important one, since otherwise you'll get a hang after one second of Bethesda logo video.Hope this helps some poor soul who is struggling to configure this properly yet.
How to load all the comments and/or search them?
@rkfg Threw together a simple user-script to load all comments: https://greasyfork.org/en/scripts/400462-git-hub-unroll-comments. Tested only in Firefox and I must say that after loading all comments on this page it gets a bit laggy occasionally (pagination would be better, but doing that in a user-script would probably break things like live adding of new comments or edits).
Update to testing Proton 5.0.6 RC :
Mouse acceleration is different to previous versions and to the GE releases.
It's much faster and doesn't seem to be constant. If I manage to make it nicely playable for me, using the other versions results in extremely slow mouse moving.
(and still, Alt+Tab makes the game go black. Alt+Tab doesn't go back. Pressing Alt once and then Alt+Tab, goes back to game, but yeah black only...)
Proton log:
https://drive.google.com/open?id=1fJVizLLrEeOjkoODDFrbQLhEk7gCdsgi
kernel 5.6.3
latest stable nvidia drivers 64-440.82
linux mint 19.3 cinnamon DE
ROCCAT Kone Pure Owl-Eye Mouse
Does anyone else have problems signing in to Bethesdanet? Breaks Battlemode for me, unfortunately.
Are these crashes only happening on Nvidia cards?
@rkfg I have no experience at all in this, but I remember early in the thread people mentioned that wine currently doesn't have true support for VK_EXT_full_screen_exclusive, only workarounds. Could that be what's causing the issue?
Alt+Tab in Doom Eternal under 5.4-3 and 440.82-x drivers is guaranteed permanent blackscreen. Also Steam Overlay is also problematic. Game runs solid otherwise in Vulkan w/ 1080Ti
@PraetorianSC4 The Steam Overlay is known to decrease performance in DOOM Eternal, it's not a Wine/Proton issue. A comment lists a 5fps boost, but for me it was more like doubling the FPS (running a 5700XT w/ Mesa 20.0.4 in fairness).
Another Reddit post said that it was the FPS counter causing issues, so you could try disabling that and instead either using DOOM Eternal's built in performance metrics, or using the likes of MangoHud which I personally prefer and use myself.
@willpiam I'd like to chip in and say that running the latest version of Vulkan and Mesa stable on Arch doesn't have any issues when you Alt+Tab, aside from the documented Dossier bug. So it seems like this is an Nvidia issue.
Hey guys, FYI just in case someone will run into the same issue as I did.
I got DOOM Eternal running perfectly on Ubuntu 18.04.4 with Nvidia Driver 440.82 from graphics-drivers PPA and Proton-5.4-GE-3.
However after installing some updates recently it ceased to work - just kept crashing at startup. Launching steam with PROTON_LOG=1 revealed the following message in the log:
FATAL ERROR: Please update your driver: VK_EXT_full_screen_exclusive is required.
After fiddling with that for a while by looking into /var/log/apt/history.log I noticed that with recent updates I got libvulkan1 and mesa-vulkan-drivers packages installed which weren't installed before.
Removing both fixed the issue for me, so I guess those cause some kind of conflict with Nvidia's Vulkan stuff hence info about extensions driver actually supported was incorrect.
Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.
If you were to re-add libvulkan1, then go to <steam install dir>/ubuntu12_32/steam-runtime
and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.
With the new nvidia drivers released today on rpmfusion I've had a chance to re-test on both of my systems.
DOOM Eternal now seems to be playable.
Machine 1 (Desktop):
CPU: i7-4770
RAM: 32GB
GPU: GTX 1080ti
Drivers: 440.82
Distro: Fedora 30
Proton: Proton-5.4-GE-3
Launch Options: None
Machine 2 (Laptop):
CPU: i7-8750H
RAM: 16GB
GPU: RTX 2060
Proton: Proton-5.4-GE-3
Drivers: 440.82
Distro: Fedora 30
Launch Options (for PRIME offloading): __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
Initially I had some audio crackling, but it seems to have resolved itself.
I've got a crash log for that hard crash I was talking about earlier:
https://send.firefox.com/download/945b855f1dd20e0d/#dP9yXbTc4PGFlF5mkZL1EQ
Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.
If you were to re-add libvulkan1, then go to
<steam install dir>/ubuntu12_32/steam-runtime
and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.
Hi @kisak-valve thanks for your suggestion, it worked perfectly :+1: Actually it saved the day since later I found out that removing libvulkan1 broke something else, so super happy now everything works fine, thanks a lot!
Hello @megaden, libvulkan1 1.1.70 from 18.04.4 is known to be too old for this game. By adding it to your system it got preferred over the 1.2.135 variant in the steam runtime because Steam's library pinning logic failed to detect that a minor change happened.
If you were to re-add libvulkan1, then go to
<steam install dir>/ubuntu12_32/steam-runtime
and move/remove the pinned_libs_* folders, that would cause Steam would regenerate the pinned_libs_* folders on next start. After that the game should continue to work as it was before.
This also solved my issues on Ubuntu 18.04. Thanks!
Hello, in the interest of making usable feedback more accessible moving forward with this game, I'm archiving this issue report and we'll continue discussing Doom Eternal on #3773.
If you wish to continue receiving notifications about Doom Eternal, go to #3773 and click the subscribe button on the right side of the issue report.
Most helpful comment
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.
Here is another variant that works better:
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).