Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
NP and I'm not sure man. I'm hoping a future update fixes it but for now this is the only way I've managed to get it to run.
The issue is that certain hardware configurations have the game trying to access a memory lane that doesn't exist, I think for shader compilation?
Anyway, it's a symptom of not having UE5 Engine fully up to date before compiling the game for it's live release. This is an old bug that popped up in a few other games and I think it's related to Ray Tracing or something.
It's not fixable without a patch.
My man, you're running a 13900k CPU and the game crashes whilst attempting to run shader decompression?
Your CPU is fried.
Have you updated to the latest BIOS for your motherboard and ensured the Intel profiles are in usage? These degradation issues are as common as dirt now, for 14th and 13th gen Intel CPUs. Quick Google is your friend.
Worst case, you'll need to RMA the CPU.
Specs:
Win 10
AMD 7700X
AMD 6600XT
RAM 64GB
This is literally the only game that does this on DX12. I can play any other game at max settings for as long as I want just fine. It is not a degradation issue, especially with builds like mine that aren't even a week old.
I found a way that fixes the DX12 for me