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
Here is my thread talking to one of the devs:
https://steamcommunity.com/app/835960/discussions/1/4030221179840727881/
I just ended up refunding it.
I'll try reverting video drivers - if that doesn't work I will have no choice but to refund the game I guess. Sad because I was really looking forward to this one.
Display settings -> graphics setting -> hardware-accelerated GPU scheduling
It should be enabled.
I believe you're looking at a general protection fault or something else related to the CPU. Many people with i13900k's see an oodle error and not just with this game but with many. Its natural that other CPUs may also see the issue but many computers don't.
https://www.reddit.com/r/intel/comments/13o29w5/13900k_will_no_longer_run_dx12_games_crashingctds/
i13900k same as you:
" Update 07/23 - All issues fixed after a CPU and Motherboard replacement.
Update 09/23 - Issues are returning. Fortnite has again become unstable, this time CTDs when in-game, with the Fortnite Log reporting "Could not decompress shader group with Oodle",
Update 10/23 #2 - PC back up and running, with a new motherboard too (bonus) and all is well again. Will continue to monitor and run OCCT tests weekly. "
The person there since then reports further on the subject.
Technically, that person replacing the CPU and mobo would very likely also have a different CPU driver, firmware and different BIOS version and settings, etc. So there could be ways to workaround it.
Its also in theory possible for oodle to workaround a general protection fault of hardware where the manufacturer doesn't fix it but they also may not feel its for them to do. However, some software devs do fix software in that situation.
I kept this as short as I could and didn't include all things. You may feel a certain way about it. That's up to you to decide whatever you want. I'm done with it from here.
Shame on Intel for selling faulty CPUs and not doing nearly enough to rectify their errors. I'm only buying AMD from now on.
For others who have this issue with 13th or 14th gen Intel processors and find this thread, there are numerous YouTube videos out there about how to check if your processor is affected. If so, reach out to Intel and demand a refund...and then get a new processor and play this awesome game! :)
https://www.anandtech.com/show/21484/intel-raptor-lake-instability-faults-voltage-microcode-fix-in-august