U5 engine error Could not decompress shader

[Necrophor]

Has anyone encountered this and found a fix for it?

LowLevelFatalError [File:D:\_Gunfire\UE5\UE5-Gunfire\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 354] ShaderCodeArchive::DecompressShader(): Could not decompress shader (GetShaderCompressionFormat=Oodle)

I've done just about everything under the sun outside of wiping my OS install and fresh installing it. Any help that can be given would be greatly appreciated.

Edit: As a note i can sometimes get the game to run without changing anything its when I hit loading zones that it will crash out which is probably why sometimes its crashes on launch and sometimes it doesn't. Windows 8 compatibly didn't change anything adding the d12 and d3d stuff to the command line just made it hard crash when starting. I've cleared my cache made the cache bigger re downloaded verified lowered settings the crash still eventually happens. under clocked my gpu. I havent found a decent source for my cpu so i havent done anything to it myself. but its currently set to normal in bios. with ai tweak off. or manual.

Specs
GPU: Asus Rog Strix 3080TI
MB: Asus Tuff Z790-plus wifi
CPU: i9-13900k
64gb ram ddr5
win 11 64 bit

[Calas king]

nope welcome to the family of having the same F,ucking problem. had it since launch and nothing has fixed it and i mean nothing. they said the patch from a few hours ago fixed crash issues but it sure as hell hasn't for me

[Just Dusk]

Nope cant even launch the game since the new patch. It LITERALLY crashes me to BIOS before it even launches now since the new update

[Belmont]

Welcome to the family. Specs are pretty much exactly as yours, except mine are MSI GPU and MB. 3080ti and 13900k, 64gigs of RAM, fully updated Win 11 all drivers up to date.

The only way I can get mine to run is by putting -d3d12 in the command line, run the game in Windows 8 compatability mode, and crank everything WAY down.

Hogwarts had this problem too. It's an Unreal issue, and devs keep walking into it. I have no idea why, no idea how this is such a hard fix. Oodle is a PS5 shader decompression or something along those lines, so they were basically leaving portions of the game ported to PC using PS5 code. Not sure if that's standard practice these days or what, but for some unearthly reason Remnant II absolutely hates the 13900k.

[Arc]

Originally posted by Belmont:

...

It has nothing whatsoever to do with PS5, other than it is being used there as well.

http://www.radgametools.com/oodle.htm

Note, Oodle was implemented into UE4 a while ago:
https://docs.unrealengine.com/4.27/en-US/TestingAndOptimization/Oodle/

And is still there in UE5 which is what R2 use:
https://docs.unrealengine.com/5.0/en-US/using-oodle-in-unreal-engine/

From what I could see on this forum, vast majority of reported "Could not decompress shader" errors come from 13900K/S users.

So perhaps the problem is the big.LITTLE architecture, or perhaps these CPUs are notoriously unstable unless fine-tuned (and on some boards, these CPUs are likely running out-of-spec).

[bluewolf644]

Try running in win 8 compatibility mode, for me and others with this problem it helps out a lot. Just don't run it in admin mode as that changes the save location and you can't do multiplayer with it (don't think the patch fixed this).

[Belmont]

Originally posted by Arc:

Originally posted by Belmont:

...

It has nothing whatsoever to do with PS5, other than it is being used there as well.

http://www.radgametools.com/oodle.htm

Note, Oodle was implemented into UE4 a while ago:
https://docs.unrealengine.com/4.27/en-US/TestingAndOptimization/Oodle/

And is still there in UE5 which is what R2 use:
https://docs.unrealengine.com/5.0/en-US/using-oodle-in-unreal-engine/

From what I could see on this forum, vast majority of reported "Could not decompress shader" errors come from 13900K/S users.

So perhaps the problem is the big.LITTLE architecture, or perhaps these CPUs are notoriously unstable unless fine-tuned (and on some boards, these CPUs are likely running out-of-spec).

I don't think any amount of tuning would help, as I attempted both manual stable overclock, the generic boost overclock that MSI includes in their bios, and no overclock. None of the settings worked for me.

Tried turning off my RAM's OC as well, and tried tweaking my 3080ti's by removing my undervolt. No combination of any really helped at all.

The only thing that managed to get me into the game was Win8 compatability mode, and the -d3d12 command prompt line. Until I had both of those, it wouldn't even boot up after this patch.

Before the patch, I was able to boot just using the Win8 compatability work around.

[• Ƀеllе ɱоя₸ [Flouiz]]

We're so many to experience issue with recent games with high config. I'm surprised there is still no lawsuit

[Grimzy]

Originally posted by Belmont:

Originally posted by Arc:

It has nothing whatsoever to do with PS5, other than it is being used there as well.

http://www.radgametools.com/oodle.htm

Note, Oodle was implemented into UE4 a while ago:
https://docs.unrealengine.com/4.27/en-US/TestingAndOptimization/Oodle/

And is still there in UE5 which is what R2 use:
https://docs.unrealengine.com/5.0/en-US/using-oodle-in-unreal-engine/

From what I could see on this forum, vast majority of reported "Could not decompress shader" errors come from 13900K/S users.

So perhaps the problem is the big.LITTLE architecture, or perhaps these CPUs are notoriously unstable unless fine-tuned (and on some boards, these CPUs are likely running out-of-spec).

I don't think any amount of tuning would help, as I attempted both manual stable overclock, the generic boost overclock that MSI includes in their bios, and no overclock. None of the settings worked for me.

Tried turning off my RAM's OC as well, and tried tweaking my 3080ti's by removing my undervolt. No combination of any really helped at all.

The only thing that managed to get me into the game was Win8 compatability mode, and the -d3d12 command prompt line. Until I had both of those, it wouldn't even boot up after this patch.

Before the patch, I was able to boot just using the Win8 compatability work around.

You should read intels latest statement on this exact issue, they even tell you what your optimal profile in bios should be to avoid crashing.

[NøiSyBøY]

Originally posted by Grimzy:

Originally posted by Belmont:

I don't think any amount of tuning would help, as I attempted both manual stable overclock, the generic boost overclock that MSI includes in their bios, and no overclock. None of the settings worked for me.

Tried turning off my RAM's OC as well, and tried tweaking my 3080ti's by removing my undervolt. No combination of any really helped at all.

The only thing that managed to get me into the game was Win8 compatability mode, and the -d3d12 command prompt line. Until I had both of those, it wouldn't even boot up after this patch.

Before the patch, I was able to boot just using the Win8 compatability work around.

You should read intels latest statement on this exact issue, they even tell you what your optimal profile in bios should be to avoid crashing.

Link please ?

[Arc]

https://www.radgametools.com/oodleintel.htm

https://www.anandtech.com/show/21389/intel-issues-official-statement-regarding-14th-and-13th-gen-instability-recommends-intel-default-settings

Also: Told ya, long before this got into mainstream media.

[Arc]

This error only ever appears if the CPU or memory subsystems get the files corrupted or if the files are corrupted on disk due to other errors (mostly damaged disk or errors during download).
Circling back to "but it's only in THIS game" isn't really going to help you in any way, much less when you already complained about overheating issue during Nightingale test round.

If that's not a dead giveaway of a hardware failure then i don't know what is.

[~xWraithx~]

Originally posted by Arc:

This error only ever appears if the CPU or memory subsystems get the files corrupted or if the files are corrupted on disk due to other errors (mostly damaged disk or errors during download).
Circling back to "but it's only in THIS game" isn't really going to help you in any way, much less when you already complained about overheating issue during Nightingale test round.

If that's not a dead giveaway of a hardware failure then i don't know what is.

post was made under wrong game sorry, Overheat issue in Nightingale was due to ICUE app update not game. I will fix that post. thanks

Shader decompression issue in cpu under Greyzone. was were i intended for the post.. not sure how it got hear. sorry. Remnant II works great for me!

[Wallstrider]

Go to your BIOS then in an advanced CPU settings and disable an Intel Turbo Boost if you have an INTEL CPU of course