search

ValveSoftware / Proton

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

[379720] DOOM (2016) #3548

Open DAMO238 opened 4 years ago

DAMO238 commented 4 years ago

Compatibility Report

System Information

I confirm:

Symptoms

Game does not launch, error message in blue box is shown below:

Configured log listener print-redirect tags Added structured log listener print-redirect Added structured log listener mp-cloud-gobbler 2020-02-21T20:58:08.317+00:00 LOG: Process started Added structured log listener aws-kinesis-logger Winsock Initialized ------ Initializing File System ------ Current search path:

idRenderSystem::Shutdown() Shutting down OpenGL subsystem

FATAL ERROR: wglCreateContextAttribsARB failed

Proton Logs:

https://gist.github.com/DAMO238/87121b4a885a0d4b92e70a9b18a0bc19

Reproduction

Simply start the game from steam with all default settings.

kisak-valve commented 4 years ago

Possible workarounds in #69, #488.

DAMO238 commented 4 years ago

Thanks for the advice. I tried all workarounds linked and none of them worked unfortunately (although I did realise I have been dumb and forgot to configure nvidia drivers lol)

Darxus commented 3 years ago

When I use the default OpenGL, the audio constantly goes off for a second. But it doesn't crash.

When I change the game's internal settings to Vulkan, the graphical performance is much better, the audio is fine, but it occasionally crashes. Many of the protondb reports mention switching to Vulkan causes crashing: https://www.protondb.com/app/379720

I'd be more interested in fixing Vulkan.

Are there instructions somewhere for collecting the most useful info from a crash?

From a Vulkan crash, $HOME/steam/steamapps/compatdata/379720/pfx/drive_c/users/steamuser/Saved Games/id Software/DOOM/base/Crash.dancer.00001.html contains:

Callstack Function(desc)              Line Bytes File       Process Address
---------------------------           ---- ----- ----       ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ...  +     0x41cb2105 ?       

Register Info                
---------------------------  
EDI:    0x0000000000000001  ESI: 0x0000000000000000  EAX:   0x0000000000000002
EBX:    0x00007F6FBCE69184  ECX: 0xFFFFFFFFC291D604  EDX:   0x0000000000000001
EIP:    0x0000000141CB2105  EBP: 0x0000000008007D30  SegCs: 0x0000000000000033
EFlags: 0x0000000000010283  ESP: 0x0000000008007BB0  SegSs: 0x000000000000002B

Exception Info               
---------------------------  
ExpCode:          0xC0000005 (Access Violation)
ExpFlags:         0         
ExpAddress:       0x0000000141CB2105 

Build & Runtime Info        
--------------------------- 
User:             steamuser        
Version:          20180321-154133-liver-goldenrod        
File Path:        Z:\home\darxus\.local\share\Steam\steamapps\common\DOOM\DOOMx64vk.exe        
System Time:      12/12/2020 22:10:18        
Build String:     20180321-154133-liver-goldenrod        
VT File Path:             
VMTR Override:    generated/pagefiles        
Launch Command:   "Z:\home\darxus\.local\share\Steam\steamapps\common\DOOM\DOOMx64vk.exe"  +r_renderAPI -2         

Memory Info                 
--------------------------- 
In Use:           34%      
MB Physical RAM:  4096        
MB Physical Free: 4096        
MB Paging File:   4096        
MB Paging Free:   4294965248        
MB User Address:  4096        
MB User Free:     4096        

CPU Info                    
--------------------------- 
Num Packages:     1        
Num Cores:        8        
Num Logical:      16        
CPU ID:           Generic        
CPU MHz:          3600

I'm slightly fascinated that it's entirely a text file wrapped in a pre element in an html file.

Gert-dev commented 3 years ago

I can confirm that I also experience crashes with the Vulkan renderer: in half an hour I've experienced 7 crashes already at various points of the game: four times in the main menu and three times in-game, either during combat or sometimes just while walking around. I've switched to OpenGL now and it hasn't crashed so far.

My crash logs are mostly the same as Darxus', but the stack trace seems to be the same, empty, or this one:

Callstack Function(desc)              Line Bytes File       Process Address
---------------------------           ---- ----- ----       ------- -------
** UNKNOWN **(** FUNC_PARAM_ERROR **) ...  +     0x64344108 ?       
** UNKNOWN **(** FUNC_PARAM_ERROR **) ...  +     0x7bc67f76 ?

Most Proton reports recommend switching to Vulkan for its performance reasons, but, contrarely, my personal experience has been a bit disappointing after having high expectations due to the platinum rating from the community.

Shallrath commented 1 year ago

It also crashes for me when using Vulkan. Usually it crashes instantly, sometimes I can play for a few seconds. This has been introduced a few months ago, before I could play perfectly on Vulkan.

Gibitwit commented 5 months ago

For me on Nobara Linux the game freezes shortly after gameplay starts or during the level title cinnematic.

I found this while trying to fix the freezing. https://gitlab.freedesktop.org/mesa/mesa/-/issues/10910

braiam commented 2 months ago

Every time a checkpoint is reached, or doomguy dies and there's one other element of combat that I haven't been able to identify, the game start stuttering hard, dropping to ~5 FPS. According to the in-game measures it's a CPU utilization issue.

simifor commented 1 month ago

@braiam couldn't really reproduce here, but that vaguely sounds like you could be running out of ram or vram. Could you monitor your v/ram usage to see if it's related? also add PROTON_LOG=1 %command% to the game's launch parameter and close the game when the issue appears, then upload steam-379720.log which will be created in your home folder (compress it if it's too big)