Just wanted to follow up on this. I have found that in stock settings, it’s not just Berlin, but Sapienza, Marrakesh, Miami, Santa Fortuna, and Mumbai. Whittleston Creek loads and runs fine, but I haven’t tried the last 3 of HM2. Also all of the rest of HM3 crash in the same way.
Things I have tried that did not work:
- Reinstalling / verifying
- Updating video and chipset drivers
- Lowering resolution and graphical features
@ptbd posted a few days ago and it definitely seems related to systems with RDNA2 cards. Berlin crash while loading *every single time* (PC/Epic) - #2 by MrBlarg
I have a Ryzen 7 3700x and a Radeon RX 6800. All other instances I’ve heard about were RDNA / RDNA2, most (possibly all) were Ryzen builds as well.
Looking at some of the suggestions in the reddit thread, I have found a way that can sometimes get the game to load and I was able to complete the campaign last night, however trying the same settings today still crash regularly:
- Limit the FPS in the radeon control panel to 30
- Completely max out all of the game’s graphics options (2x sampling of 1440p, everything High or Ultra if available, 1x vsync is enough, have not overridden memory safeguards)
There are a few things that I also do, but not 100% sure they contribute:
- Clear the shader caches in both the radeon control panel and delete the shader cache file in the AppSetting folder
- Doing only this, and nothing else, results in the same exact crash on the loading screen
- Turn off radeon overlay and video capture (can’t turn off epic’s overlay)
- Turn off radeon graphics options (anti-lag, sharpening, texture/tessellation, etc)
- Again, Frame Rate Target Control should be on and set to 30
With these settings, I can get Apex Predator to load and play for a few minutes. When loading, the first in-game camera move seems to trigger the crash (I did confirm though the event log that they were the exact same error codes at the same memory locations). Most (but not all) saves will only crash when the scene comes up or within a few seconds of gameplay.
It’s an odd and frustrating bug, and I’m happy to try out any reasonable suggestions or provide any diagnostic or log files. I even captured a trace with Process Monitor to see if there was a file issue (there was nothing conclusive).
EDIT (cross posting from the other thread, @Sakatak1972 might try this):
Update! I tried the TdrDelay trick and rebooted and then cleared both shader caches (clearing the radeon driver’s cache probably isn’t necessary, but it’s just a single click).
I’m now playing Congquing at 1440p @ 120+fps with all settings on high/ultra and anti-lag and enhanced sync enabled in the driver control panel.
From the reddit thread:
Simply go to: Start → Run → Type in “Regedit” and navigate to:
“Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers”
Create a key of type "DWORD (32-bit) for a 32-bit system. or a "QWORD (64-bit) for a 64-bit system.
Name it “TdrDelay” with a value of ‘10’ as “Decimal value”.
Reboot your system, launch the game, and the crashes won’t happen
