search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.58k stars 1.07k forks source link

Doom Eternal (782330) - Initial month of feedback #3654

Closed oscarcp closed 4 years ago

oscarcp commented 4 years ago

Compatibility Report

System Information

I confirm:

steam-782330.log

Symptoms

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

Reproduction

dpanter commented 4 years ago

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

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

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

MuchiMuchiPink commented 4 years ago

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

oscarcp commented 4 years ago

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

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

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

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

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

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

FTL-Space-Warp commented 4 years ago

Did anone tryy with 440.66.03?

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

xDShot commented 4 years ago

Crash reports are enabled with +com_enableCrashHandler 2

xDShot commented 4 years ago

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

APoniatowski commented 4 years ago

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

farfalleflickan commented 4 years ago

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

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

JusterK commented 4 years ago

steam-782330.log

jalabb commented 4 years ago

Just tried 440.66.03, it doesn't change anything.

silviucc commented 4 years ago

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.

outergod commented 4 years ago

steam-782330.log

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

comminux commented 4 years ago

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

We need to try use this leaked executable file.

outergod commented 4 years ago

steam-782330.log

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

oscarcp commented 4 years ago

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

outergod commented 4 years ago

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

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

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

MuchiMuchiPink commented 4 years ago

@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 commented 4 years ago

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

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

mozo78 commented 4 years ago

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

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

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

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

Full log: steam-782330.log

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

gardotd426 commented 4 years ago

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 .

scottlinux commented 4 years ago

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

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

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

MuchiMuchiPink commented 4 years ago

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

rassie commented 4 years ago

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

MuchiMuchiPink commented 4 years ago

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.


00d5:fixme:bcrypt:BCryptCreateHash ignoring object buffer
00d0:fixme:bcrypt:BCryptCreateHash ignoring object buffer
0197:fixme:bcrypt:BCryptCreateHash ignoring object buffer
wine: Unhandled exception 0x80000003 in thread d5 at address 0000000140822876 (thread 00d5), starting debugger...```
mozo78 commented 4 years ago

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

FTL-Space-Warp commented 4 years ago

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

outergod commented 4 years ago

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

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

APoniatowski commented 4 years ago

additional steps taken:

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

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

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

mozo78 commented 4 years ago

@Guy1524 Can you fix it like MK11 :)

favonius85 commented 4 years ago

Another report with some different AMD hardware.

System Information

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

steam-782330.log sysinfo.txt

rkfg commented 4 years ago

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

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

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

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

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

gardotd426 commented 4 years ago

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:...\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 ( and Vulkan developer driver

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

APoniatowski commented 4 years ago

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

rkfg commented 4 years ago

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

OrdinaryMagician commented 4 years ago

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

rkfg commented 4 years ago

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

mozo78 commented 4 years ago

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

gardotd426 commented 4 years ago

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 .

APoniatowski commented 4 years ago

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

gardotd426 commented 4 years ago

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

mozo78 commented 4 years ago

Ah, I see. Thanks :)

dxgldotorg commented 4 years ago

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

zaggynl commented 4 years ago

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

stevenpitts commented 4 years ago

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?

outergod commented 4 years ago

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

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

PraetorianSC4 commented 4 years ago

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

Not necessarily?

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

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

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

MacroHard-sys commented 4 years ago

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

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

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

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

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

mozo78 commented 4 years ago

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.

stevenpitts commented 4 years ago

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

MacroHard-sys commented 4 years ago

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