安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
Oodle is a common deceompression method used by Unreal engine games.
just do a Google search for: oodle intel instability
There are threads and forum posts that can explain it in much better detail than I can.
I already uninstalled the game cause trying to start a new game, the game crashed and I don't feel like going through a bunch of hoops to get the game working, and if this game isn't going to work because of incompetent Devs, forget it...
Do you have a 13th or 14th gen Intel CPU? I'm not saying it is, or is not your particular issue. There is a good chance it's related to instability if it's a 13900K or 14900K CPU.
I have a couple of systems. One of them with a 13900K that would crash playing Suicide Squad:KTJL, another Unreal Engine game, with the same "out of memory" error. The strange thing is, out of all the games I play, it was only that game. It would crash anywhere from trying to launch, to 5-10 minutes into the game, it felt random. After BIOS and microcode updates, knock on wood, the CPU has been stable.
I have no idea where else your posting, all I can go by is the original post that I noticed. So I don't who's telling you your hardware is crap. I'm sure it's not. If you haven't updated your BIOS, I wouldn't wait too long.
https://www.radgametools.com/oodleintel.htm
--
Intel Processor Instability Causing Oodle Decompression Failures
There is a confirmed hardware problem affecting 13th and 14th generation Intel Core processors (13xxx and 14xxx series) that manifests as general system instability and causes, among other things, Oodle Data decompression failures and crashes in games built with Unreal.
When starting an Unreal Engine-based game, the most common failure is of this type:
DecompressShader(): Could not decompress shader (GetShaderCompressionFormat=Oodle)
However, this problem does not only affect Oodle, and machines that suffer from this instability will also exhibit failures in standard benchmark and stress test programs. Any programs which heavily use the processor on many threads may cause crashes or unpredictable behavior. There have been crashes seen in Adobe Premiere, RealBench, CineBench, Prime95, Handbrake, Visual Studio, and more. This problem can also show up as a GPU error message, such as spurious "out of video memory" errors, even though it is caused by the CPU.
The root cause is now confirmed by Intel to be rapid aging of clock signal circuitry in the chip due to a confluence of several other issues. This is actual physical wear of the chip itself, and once this deterioration has occurred, it is sadly irreversible. Affected parts need to be replaced; the process is outlined here.
As of this writing (Oct 1, 2024), new BIOS updates are just being released that avoid the operating conditions causing damage to the circuitry. If you are using a pre-built laptop or desktop PC, the vendors are (or at least will be shortly) distributing BIOS updates containing this workaround. It is important to install these updates ASAP before symptoms manifest. Once the crashes start, it's too late for a software solution! If you built your machine yourself, check your motherboard vendor's web site for an updated BIOS image.
You might be fine if it's caught in time.
I wouldn't leave it to chance. I would go into the BIOS and check to see if you're set to "Intel Default Settings" or something else like "vendor optimized settings". Wording varies by board manufacturer.
In my case I *think* I caught mine in time. I haven't had any Unreal engine game crashes since. My system crashed once or twice. I chalked it up to .. ♥♥♥♥ happens, until I saw reports on news sites and took action.
Clearly its everyone else's fault that you got scammed by Intel.