Closed oscarcp closed 4 years ago
Doom Eternal not starting
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3655. @APoniatowski posted on 2020-03-20T00:48:54:
soon...
Game crashes on start
-install -start
@oscarcp commented on 2020-03-20T00:49:39:
Crap, we both started the ticket at the same time. Shall I put mine as duplicate?
Hello @oscarcp, my understanding is that this game will need an updated video driver stack. I'm not sure of everything that is needed, but vulkan-loader 1.2.135 should be one of the requirements. This is rare, but Arch's vulkan-loader is currently too old. Opting into Steam's beta client, then completely closing steam and running Steam with steam-runtime
should at least cover that requirement. It may also need a bleeding edge video driver version.
Hello @oscarcp, my understanding is that this game will need an updated video driver stack. I'm not sure of everything that is needed, but vulkan-loader 1.2.135 should be one of the requirements. This is rare, but Arch's vulkan-loader is currently too old. Opting into Steam's beta client, then completely closing steam and running Steam with
steam-runtime
should at least cover that requirement. It may also need a bleeding edge video driver version.
Updated nvidia drivers to 440.64 and my current vulkan-icd-loader is 1.2.132. There doesn't seem to be any more recents version, at least packaged. I'll investigate and see if I can update.
switched to steam beta and using steam linux runtime, instead of proton. had an error where the idlauncher binary was missing, so running game file verification... might need to reinstall though
nope... missing executable (idtechlauncher.exe). last ditch effort now is reinstalling the game
Hello @APoniatowski, if you tested with the Steam Linux Runtime compatibility tool, that's a container for running Linux games on Linux. Selecting it is expected to fail because Proton is then not used to handle Windows games.
I should have clarified that the Steam runtime (not the compatibility tool) update in today's Steam client beta update contains the 1.2.135 vulkan loader.
aaah, figured.
However, I did run it with proton, before trying the compatibility tool. still crashed unfortunately
Is there a file called DOOMEternalx64vk.exe?
@APoniatowski @kisak-valve I'm pretty sure what @kisak-valve was saying is that the "Steam Linux Runtime" compatibility tool is a replacement for (and conflict with) Proton, BUT that running the steam-runtime
version of Steam instead of steam-native
on Arch-based distributions uses the Steam runtime libraries, not the compatibility layer, and that's what's been updated to vulkan loader 1.2.135.
Here goes an update. I've updated vulkan-headers and vulkan-icd-loader both to 1.2.135 (I've modified the AUR files, I'll publish the changes tomorrow). As for the nvidia drivers, 440.64 is the latest available (latest beta available is 440.26).
I've also tried Steam beta and non-beta, running each natively and as runtime from terminal. Nothing has worked so far :(
@oscarcp That doesn't help Valve fix anything. You need to post the logs for each attempt, so they can see what changes, and what doesn't. Don't just say "it didn't work."
@gardotd426 I should've clarified on my part as well. I only run steam-runtime (had to double check)
@kisak-valve Here's an updated log, after opting in for the beta and updating it, reinstalling the game and starting it again
@oscarcp also, you couldn't have updated the AUR files for vulkan-icd-loader
, it's in the repos, there is no vulkan-icd-loader
AUR package. vulkan-headers
is also in the official repos, not AUR, although there is a vulkan-headers-git
AUR package. But that's irrelevant anyway as that's for development, you don't need any vulkan-headers
package installed.
also, you couldn't have updated the AUR files
You can obtain the PKGBUILD for the package via ABS and modify that though. I'm almost certain that that's what they meant.
FWIW I did the same (requires vulkan-headers-git to build) but it still fails with the exact same log that OP posted.
I see lots of from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored
and from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored
errors in the log, now that I look at it
ERROR: ld.so: object '/home/sizigee/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/sizigee/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
@doitsujin Philip, yeah that is true, but that's not what they said so I didn't think that's what they meant. But that's fair enough.
Any ideas?
@APoniatowski I know that there are always a ton of those errors regardless, that are supposed to be ignored, but you're right it looks like a lot lot more than usual
@gardotd426 regou're right, so here goes:
Regarding the AUR, yes, I've downloaded the PKGBUILDS, regenerated the sha256sum and compiled them. Regarding headers, the loader deepends on the headers vulkan-icd-loader 1.2.135 PKGBUILD: https://gist.github.com/oscarcp/9b54ea7f6bd4eb4144bd4e5e980f2c4c vuikan-headers 1.2.135 PKGBUILD: https://gist.github.com/oscarcp/4c4fb71fa380015b722172f308d406b1
looked at the launcher.cfg for doom eternal and saw this:
rgl_minNvidiaDriverVersion 44261
and changed it to my version:
rgl_minNvidiaDriverVersion 44064
still didn't work, for those who thought about mucking in cfg's... the only other cfg's there, are package and candidate details
The logs are huge, but so far they have the same errors, from what little I've been able to go over.
I would suggest AMDVLK over RADV if either of you were running AMD, but seems like we don't have anyone trying this with an AMD card yet.
EDIT: Removed WINED3D
reference, somehow forgot this game was Vulkan only with no OpenGL or DX
The game uses Vulkan, so wined3d/dxvk makes absolutely no difference whatsoever.
FWIW I am using an AMD card.
tried WINED3D
now... same result, unfortunately.
@doitsujin, duh, I completely forgot this one was Vulkan-only, I was thinking of how DOOM 2016 had an OpenGL version.
Have you tried AMDVLK or anything like that? Are you getting the same sorts of errors as the guys with the Nvidia cards?
I'm experiencing the exact same symptoms on AMD hardware.
come to think of it... is there a way to run DOOMEternalx64vk.exe
instead of the launcher? I know launchers can be wonky for some/most games
@gardotd426 yes, this is not a driver issue.
FWIW I'm trying to build a current wine version with https://github.com/ValveSoftware/wine/pull/85 applied, but so far I'm having issues rebasing the patch.
@APoniatowski try it in Lutris. If anyone has enough storage and a fast enough internet connection I would suggest maybe also trying to run it in Wine Steam.
@doitsujin lol it's always something, isn't it. Hopefully that will fix it once you get it figured out.
Hello,
same here Doom Eternal won't start.
Linux Mint 19.3 Kernel 5.5.9 Nvidia driver 440.64 steam & steam beta. Proton 5.0-4
How do you guys create those detailed logs? So I can also contribute one if wanted.
This is what I get when running steam from a terminal:
```
>>> Adding process 27762 for game ID 782330
ERROR: ld.so: object '/home/ellen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 27826 for game ID 782330
Game update: AppID 782330 "", ProcID 27826, IP 0.0.0.0:0
RecordSteamInterfaceCreation (PID 27826): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 27826): SteamUser020 / User
RecordSteamInterfaceCreation (PID 27826): SteamUser017 / User
RecordSteamInterfaceCreation (PID 27826): STEAMAPPS_INTERFACE_VERSION006 / Apps
wine: Unhandled page fault on write access to 0000000023377774 at address 0000000148D71006 (thread 003e), starting debugger...
ERROR: ld.so: object '/home/ellen/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
>>> Adding process 27828 for game ID 782330
Unhandled exception: page fault on write access to 0x23377774 in 64-bit code (0x0000000148d71006).
Register dump:
rip:0000000148d71006 rsp:000000000092e758 rbp:0000000023377774 eflags:00010217 ( R- -- I -A-P-C)
rax:000000015bb567c2 rbx:000000015bb567c2 rcx:0000000023377774 rdx:000000015bb567c2
rsi:0000000157529f99 rdi:0000000023377774 r8:0000000072cc6fe6 r9:0000000023377774 r10:000000015bd128ac
r11:000000000092e91e r12:000000004bb38659 r13:000000014050f850 r14:000000002319d1de r15:000000015bb567c2
Stack dump:
0x000000000092e758: ffffffff9b2f4a10 0000000000014b1b
0x000000000092e768: 0000000000000000 000100000092f780
0x000000000092e778: 0000000000000000 0000000000000000
0x000000000092e788: b2fe000000000000 f9c00000000120db
0x000000000092e798: 0001000000000092 0001000000000000
0x000000000092e7a8: b882000000000000 0000000000015b01
0x000000000092e7b8: 04b1000000000000 0000000000015d88
0x000000000092e7c8: 0000000000000000 0001000000000000
0x000000000092e7d8: 0000000000000000 0000000000000000
0x000000000092e7e8: 0000000000000000 9290000000000000
0x000000000092e7f8: 0000000000015551 00fc000000000000
0x000000000092e808: 0000000000000000 0000000000000000
Backtrace:
=>0 0x0000000148d71006 EntryPoint+0xea8fbfe6() in doometernalx64vk (0x0000000023377774)
0x0000000148d71006 EntryPoint+0xea8fbfe6 in doometernalx64vk: movq %r13,0x00000000001da596(%r14)
Modules:
Module Address Debug info Name (127 modules)
PE 930000- a2c000 Deferred oo2core_8_win64
PE 62140000- 62144000 Deferred uxtheme
PE 637c0000- 6383d000 Deferred winmm
PE 64340000- 64346000 Deferred winhttp
PE 64940000- 64943000 Deferred shcore
PE 64c80000- 64c83000 Deferred steamclient64
PE 64d40000- 64d44000 Deferred vulkan-1
PE 65000000- 65028000 Deferred ole32
PE 65600000- 6561e000 Deferred xinput1_3
PE 65780000- 65784000 Deferred version
PE 66440000- 66449000 Deferred msacm32
PE 68a40000- 68a48000 Deferred shlwapi
PE 6a100000- 6a108000 Deferred oleaut32
PE 6a700000- 6a70f000 Deferred setupapi
PE 6afc0000- 6afc3000 Deferred msimg32
PE 6b2c0000- 6b2df000 Deferred wininet
PE 6b880000- 6b883000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bec4000 Deferred imm32
PE 6c0c0000- 6c0c4000 Deferred wsock32
PE 6d9c0000- 6d9cb000 Deferred mpr
PE 6e340000- 6e343000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6e6c3000 Deferred api-ms-win-core-localization-l1-2-1
PE 6e780000- 6e797000 Deferred oleacc
PE 6f480000- 6f484000 Deferred gdiplus
PE 6fbc0000- 6fbc4000 Deferred rpcrt4
PE 71240000- 71245000 Deferred jsproxy
PE 7b000000- 7b003000 Deferred kernelbase
ELF 7b400000- 7b681000 Deferred kernel32
@AllKind launch the game with "PROTON_LOG=1" (no quotation marks), it will automatically create a log file named "steam-gameid.log" in your /home/ directory, in this case its name will be "steam-782330.log". Then you can upload that file using the attachment system right below the comment-box.
@AllKind you can also go to the game's properties in Steam and go to the launch options, and put PROTON_LOG=1 %command%
, that way you'll get the log whether you launch from a terminal or not.
steam-782330.log I'm having the same issue. I'll upload my Proton log, just on the off-chance it can be helpful in any way.
I can confirm I'm having the same issue.
GTX 1080 Ti Driver/LLVM version: nvidia 440.64 Kernel version: 5.5.8 Proton version: 5.0-4
Same experience on my end. The game launches, I see the tray icon, and then the game exits. Nothing but the icon ever draws on screen. I'm not dumped out of the loading screen or main menu or anything.
I tried running it with AMDVLK, and that is the run this log is for.
Debian Testing (mostly) Kernel 5.5.0 RC5 Proton 5.0-4
AMD TR 2990WX AMD Radeon VII 96 GB RAM
amdvlk/Ubuntu 18.04,now 2020.Q1.3 amd64 [installed] libvulkan-dev/testing,unstable,now 1.2.131.2-1 amd64 [installed] libvulkan1/testing,unstable,now 1.2.131.2-1 amd64 [installed] mesa-vulkan-drivers/experimental,now 20.0.0-1 amd64 [installed] vulkan-tools/testing,now 1.1.126.0+dfsg1-1 amd64 [installed,automatic] vulkan-utils/testing,testing,now 1.1.126.0+dfsg1-1 all [installed]
Here is my log as well. Same issues mentioned above.
OS: Arch Linux KERNEL: 5.5.8-zen1-1-zen CPU: AMD Ryzen 5 2600 Six-Core GPU: NVIDIA GeForce GTX 1070 GPU DRIVER: NVIDIA 440.64
Same issue as mentioned above. The game will appear as "playing" on Steam, and then nothing will happen, followed by being returned to "Online" status.
Same issue as all the others:
GPU: AMD RX480 Driver: AMDGPU-Pro-19.50-967956 Vulkan Instance Version: 1.2.131 Kernel: 4.15.0-91 (Linux Mint 19.3)
Same issue: steam-782330.log
GPU: 8 GB GTX 1070 Driver: 440.44 OS: Pop!_OS 19.10 Proton version: 5.0-4
Using the Steam Beta client.
I do get an error message when starting the game
Unable to initialize SteamAPI. Please make sure Steam is running and you are logged in to an account entitled to the game.
Here my log: steam-782330.log
I get this message when starting the game using Proton 3.16-9
Log when forcing proton 5.0-4: steam-782330.log
Tried with steam-runtime with the beta mentioned above and get the same problem it crashes shortly after running.
GPU: Nvidia RTX 2080 CPU: i7 7820HK OS: Arch Graphics Driver: 440.64-5 Kernel: 5.5.10-arch1-1
Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.
Tried with Proton-5.4-GE-1, i get attached screen, and then crash after clicking play.
Out of curiosity, which version of the NVIDIA driver do you have installed?
I have the same problem as the original poster, just gives me the Wine system tray and then stops.
I am running: Fedora 31 i7-3770K GTX 1050Ti, driver v. 440.64. steam-782330.log
Out of curiosity, which version of the NVIDIA driver do you have installed? 440.64-0ubuntu0~0.18.04.2
I just tried Prton-5.4-GE-1 too and got the GPU Driver Error page @xA8EYLgMSN43oEHC did above too. I am using arch so the version of the driver I have is 440.64-5.
Steam log on proton-5.4.GE-1, i am using: elementary OS 5.0 GPU: gtx 1050ti driver 440.64 steam-782330.log
Adding logs for proton 4.11 and 5.0.4 along with steam hw and lib info: steam-782330_proton411.log steam-782330_proton504.log steam_hw_info.txt
Thanks @rabidlassie & @gardotd426 here with proton log... steam-782330.log
Linux Mint 19.3 Kernel 5.5.9 Nvidia driver 440.64 steam beta. Proton 5.0-4
Here goes an update. I've updated vulkan-headers and vulkan-icd-loader both to 1.2.135 (I've modified the AUR files, I'll publish the changes tomorrow). As for the nvidia drivers, 440.64 is the latest available (latest beta available is 440.26).
Not true, latest driver is vulkan dev beta 440.66.03 which is for Vulkan 1.2:
Compatibility Report
System Information
I confirm:
steam-782330.log
Symptoms
The game starts, opens the system tray of wine, then closes abruptly.
Reproduction