My packaged game gives this error on some computers, crashes and does not start. what would be the reason?
Full error in crash log;
LowLevelFatalError [File:D:\build\++UE5\Sync\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 385]
DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 60 Group IoStoreHash:1416d1bedd464b36c6065209 Group NumShaders: 24 Shader Index: 848 Shader In-group Index: 60 Shader Hash: 73F4BA3A279CE25890BD4B75BC91A9E1EC76F15A
From what i seen, it happen on latest intel cpu due to their high frequency / bios setting.
Some people have tried running on win 8 compatibility with run as admin, and others modifying the cpu speed with Intel XTA but it might not be the best solution to recommend your clients to modify their bios especially cpu clock if something wrongly set.
It also seem to happen on specific map or specific textures on other games.
If you are using the latest intel series, and using manufacture motherboard like ASUS, they have rank up the cpu frequency(even on default), so you will need to set your cpu frequency to Intel Baseline in your bios.
Hi, i got same problem with new subnautica 2. But i have i5 9400f) how i can fix it? i`m aint boost my CPU
Fatal error: [File:D:\BuildAgent\work\95c8170b68ca015d\UE\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 491]
DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 440 Group IoStoreHash:0bd433b23f289face593ff09 Group NumShaders: 3 Shader Index: 6548 Shader In-group Index: 440 Shader Hash: EDEBF0F33E456976A95E2FCE067621EDB364F023. The CPU (Intel(R) Core™ i5-9400F CPU @ 2.90GHz) may be unstable;
Same here with Subnautica 2 and am running a i5-14600K at 3.50Ghz with 32Gb RAM. I’ve updated my Nvidia drivers for my RTX 4700 and tried all of the Window and game tweaks and fixes suggested short of updating the bios and none have worked. I have a bunch of games that all work, it is just Subnautica 2 that doesn’t. I’ve read that this is a known problem for some 14 & 15 gen CPUs but I don’t want to risk updating the bios and it somehow go wrong and I lose the C: drive.
