The Doom Curse (freezing for 10-30 seconds in certain unknown areas)

[acoustic geode]

Playing for the first time today, fps is pretty good especially for how nice the game looks. Occasionally i will walk near (like less than 5m) some object or area or i dont know that will curse me with really bad freezing, freezes my whole pc. friend called it the door of doom when it happened on a door? so im calling it the doom curse

i am also asking about this in the protondb discord, as i am running this on linux and the system log reveals kernel errors when it happens

[green parcel]

huh, I'm actually running into the same issue, the behavior is what I find kinda odd, I had it happen yesterday during my first 2 or 3 matches and then I played like four matches without experimenting this issue

I would say it happens at random times but it seems to occur when loading something, I am unsure, but at my first match today it happened at the very beginning of the match and then when I entered Potsville and on a different match it happened when turning on the generators, these might be coincidences ofc

also, I've seen other posts about this and it seems like it is a Linux with AMD issue, I am yet to see someone experiencing the same on a Linux/Intel or Linux/Nvidia setup

did you have any luck in the protondb discord?

[acoustic geode]

ive had a few possible solutions tried but none have worked unfortunately. currently im fresh installing on a spare ssd, to see if a clean OS fixes anything. im using endeavourOS. why is there a 15 minute slowmode here

[green parcel]

Alright, I will see if I can find anything when I get home from work, I'm using Arch btw, so we should have similar results

Thanks for your help! Looking forward to see if a clean install does anything

[acoustic geode]

unfortunately same issue. i cant upload the logs cause of permissions.

[acoustic geode]

for those in the arch linux discord server, where ive had the most activity around this, heres the thread https://discord.com/channels/399812551963049995/1362559592093188166

[green parcel]

I just played 3 matches without a single freeze and two of them were actually from start to extraction, I am yet to confirm if it is working or if it is a coincidence, but I just tweaked the in-game graphics and display options

Change sampling from AMD FSR to TSR and left it at "Native Anti-Aliasing", I also changed all the graphics to low except for:

• View Distance: Ultra
• Gore Quality: High
• Physics Quality: High
• Animation Quality: Very High

I didn't follow any method or order, just didn't feel like playing with low view distance or animation quality hahaha I will try to play a few more matches with this configuration in order to verify if the freezes actually stopped or if it is a coincidence.

Then I'll try to zero out the mitigation to the graphics adjustment or the Sampling from AMD FSR to TSR, but yeah, two matches from start to extraction without any freezes, baby!

I am running an AMD Ryzen 7 5700X and a Radeon RX 7700 XT at 1080p

[green parcel]

Alright, I tested with everything on very high and got no issues, it seems like the crashing really is having the Sampling on AMD FSR or atleast that's what has worked for me.

Just noticed there was an update during the day so it might also be that lol

[acoustic geode]

it wasnt the update, at least for me. still crashed when i tested a couple hours ago. ill try the settings you listed

[strange burrow]

Same here tho my case is 5 sec freeze but later it gets to 1-2 sec only

[acoustic geode]

@green parcel @upper cargo the issue was indeed the FSR

i still reported it cause yknow, big bug. apparently this server doesnt like the f word?

[green parcel]

That's neat! I actually got a freeze at the very extraction of a level, so it might not be perfect but it was a freeze in like 7 hours of gameplay

Also, for future reference, where do you file a bug such as that? And yeah, the server does not like swearing, my message got blasted lol

[acoustic geode]

https://gitlab.freedesktop.org/mesa/mesa/-/issues/13015 i reported it here since radeon-vulkan is from mesa

[acoustic geode]

intel XeSS also seems to cause freezing

[upper cargo]

yeah the freezing is definitely still happening even though I'm on Native AA

[green parcel]

Nevermind that last freeze I had, I'm an idiot and enabled FSR back for further testing and forgot hahaha

Using Native AA it works fine

[small heart]

Yes I had this on a nightmare match but thankfully for some reason after I died, the game let me keep my character

[strange burrow]

Lmao nice

[pseudo hawk]

I get the random freezes playing this on steam deck. Other than that it’s runs pretty damn good for me

[strange burrow]

It’s compatible w/ Deck? Nice

[pseudo hawk]

Well under compatibility it says unknown, but decided to try anyways during free weekend. Tweaked some settings and got it running decent. Enough to extract a few times. The freezing problem is what screws me over sometimes

[acoustic geode]

im still getting the freezing on taa native unfortunately
less common but it is still happening

[acoustic geode]

had two unrecoverable freezes last night

[upper cargo]

rip. im still getting them but much less common now

[acoustic geode]

same yeah

[strange burrow]

Prolly due to less free weekend folks clogging the connection and rubberbanding

[acoustic geode]

new mesa driver update, gonna test it

[green parcel]

@acoustic geode did you had a chance to test it? how did that go?

[acoustic geode]

havent had any issues so far!

[acoustic geode]

ive gotten 3 freezes within the last few hours (first time since the game update). 1 recovered after 5 seconds, the other two i had to force close the game. the error messages in the log are the same. i have not updated my pc since the last mesa update, which i will do now and see if anything changes. i doubt it will since theres not any driver updates for me

amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32783)
amdgpu:  in process GameThread pid 46288 thread vkd3d_queue pid 46445
amdgpu:   in page starting at address 0x00008002a6e14000 from client 0x1b (UTCL2)
amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00401031
amdgpu:      Faulty UTCL2 client ID: TCP (0x8)
amdgpu:      MORE_FAULTS: 0x1
amdgpu:      WALKER_ERROR: 0x0
amdgpu:      PERMISSION_FAULTS: 0x3
amdgpu:      MAPPING_ERROR: 0x0
amdgpu:      RW: 0x0
amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:4 pasid:32783)
amdgpu:  in process GameThread pid 46288 thread vkd3d_queue pid 46445
amdgpu:   in page starting at address 0x00008002a6e0f000 from client 0x1b (UTCL2)
amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu:      MORE_FAULTS: 0x0
amdgpu:      WALKER_ERROR: 0x0
amdgpu:      PERMISSION_FAULTS: 0x0
amdgpu:      MAPPING_ERROR: 0x0
amdgpu:      RW: 0x0
amdgpu: Dumping IP State
amdgpu: Dumping IP State Completed
amdgpu: ring gfx_0.0.0 timeout, but soft recovered

note that this only returned AFTER the latest update

[dry jungle]

Thanks for the feedback! To help with the 'doom curse' issue, please try the following steps:

1. Verify your game files to ensure everything is up-to-date.
2. Update your graphics drivers.
3. Check for any background apps that may be causing conflicts.

Hope this helps!

[acoustic geode]

I have done all three of those (and more) multiple times. This is also on linux, not windows, so the same "common fixes" probably dont apply. You dont look like an official account, are you a bot?

[torpid rain]

It has a role that bots cant give

[acoustic geode]

true..

[torpid rain]

So yea its a offical account

[acoustic geode]

the profile pic and auto-responder type paragraph threw me