Doom Eternal not starting

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3655.
@APoniatowski posted on 2020-03-20T00:48:54:

Compatibility Report

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

System Information

soon...

I confirm:

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

steam-782330.log

Symptoms

Game crashes on start

Reproduction

-install
-start

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

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

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

steam-782330.log

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

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

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

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.

steam-782330.log

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

System Information

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

steam-782330.log

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:

@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

steam-782330.log

steam-782330.log

Me too.

Ryzen R7 3700x
5700XT
kernel 5.5.9
Proton 5.0.4

steam-782330.log

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

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

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

AMD TR 2990WX
AMD Radeon VII
96 GB RAM

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

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

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

steam-782330.log

steam-782330.log

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

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

Same issue as all the others:

steam-782330.log

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

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

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

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

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

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:

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

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:

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

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

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

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

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

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

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)

steam-782330.log

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

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.

steam-782330.log

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

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

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

We need to try use this leaked executable file.

steam-782330.log

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 the seh:virtual_unwind part, right?

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

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
module

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

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

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

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:

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

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

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

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

@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

steam-782330.log
sysinfo.txt

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 Memory

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

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

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

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

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

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:

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

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

@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

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

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:

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

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

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

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

@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 useRADV_PERFTEST=llvm`.

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

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

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:

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

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=sharing

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

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

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.

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!

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.

log (55MB)

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:

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

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

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

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

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.

steam-782330.zip

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 nvidia 440.64 on a GTX 1080 Ti, trying proton 5.0-5.

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

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

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

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

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

steam-782330.log

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

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!

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

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

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

@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

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

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

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

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

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

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

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

steam-782330.log

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

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

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)

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

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

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

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

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

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 inside DOOMEternal/base/ from the drm-free version, expect for the files ending with .streamdb and not the folders. That's nine files total.

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

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

@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

error.log

Vulkan Instance Version: 1.2.131

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

vulkan is old, you need to update manually

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

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.

System Info

EDIT: Sorry for photo rotations :(

@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",