Failed to decompress (corrupted data)

This issue is still happening frequently.. any news from GGG?

"
2023/10/06 23:34:22 48955281 b740341a [INFO Client 240] [DOWNLOAD] Pre-downloading "Streaming/Content/Data/WorldAreas/MapWorldsCitySquare"
2023/10/06 23:34:22 48955281 32758d39 [INFO Client 240] [SHADER] Delay: OFF
2023/10/06 23:34:22 48955281 ca3a6a7f [INFO Client 240] Connecting to instance server at 160.202.166.107:6112
2023/10/06 23:34:23 48955359 ca3a4dbd [DEBUG Client 240] Connect time to instance server was 62ms
2023/10/06 23:34:23 48955437 1186a0e2 [DEBUG Client 240] Generating level 83 area "MapWorldsCitySquare" with seed 3205054115
2023/10/06 23:34:23 48955531 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:23 48955812 a0b45e09 [CRIT Client 240] [STORAGE] Failed to decompress (corrupted data)
2023/10/06 23:34:24 48956328 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:24 48956437 2d1efd8d [CRIT Client 240] [D3D12] Pipeline compilation failed [VS: , PS: ].
2023/10/06 23:34:24 48956437 1d2ca080 [CRIT Client 240] [RENDER] Pipeline generation failed. (Signature: "Metadata/EngineGraphs/base.fxgraph" "Metadata/EngineGraphs/disable_lighting.fxgraph" "Metadata/EngineGraphs/trail_default.fxgraph" "Metadata/EngineGraphs/trail_uv_distance.fxgraph" "Metadata/Effects/Graphs/General/BasicColour.fxgraph" "Metadata/Effects/Graphs/General/ForceAlphaTest.fxgraph" "Metadata/Effects/Graphs/General/LookupTexture.fxgraph" "Metadata/Effects/Graphs/General/ScaleMoveUV.fxgraph" )
2023/10/06 23:34:24 48956703 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:24 48956828 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:24 48957234 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:24 48957296 18778c4 [WARN Client 240] [SHADER] Uncompress error: [SHADER] Oodle: Failed to decompress
2023/10/06 23:34:25 48957453 2d1efd8d [CRIT Client 240] [D3D12] Pipeline compilation failed [VS: , PS: ].
2023/10/06 23:34:25 48957453 1d2ca080 [CRIT Client 240] [RENDER] Pipeline generation failed. (Signature: "Metadata/EngineGraphs/base.fxgraph" "Metadata/EngineGraphs/animateduvalpha_tex.fxgraph" "Metadata/Effects/Graphs/General/ForceMultiply.fxgraph" "Metadata/Effects/Graphs/General/BasicColour.fxgraph" "Metadata/Effects/Graphs/General/Ambient.fxgraph" "Metadata/Effects/Graphs/General/DarkenTex.fxgraph" )
2023/10/06 23:34:25 48957609 1d2ca080 [CRIT Client 240] [RENDER] Pipeline generation failed. (Signature: "Metadata/EngineGraphs/base.fxgraph" "Metadata/EngineGraphs/animateduvalpha_tex.fxgraph" "Metadata/Effects/Graphs/General/ForceMultiply.fxgraph" "Metadata/Effects/Graphs/General/BasicColour.fxgraph" "Metadata/Effects/Graphs/General/DarkenTex.fxgraph" "Metadata/Effects/Graphs/General/Ambient.fxgraph" )
2023/10/06 23:34:26 48958750 f22b6988 [INFO Client 240] Tile hash: 2545285986
2023/10/06 23:34:26 48958750 f22b6b6e [INFO Client 240] Doodad hash: 698097789
2023/10/06 23:34:26 48958828 a0b45e09 [CRIT Client 240] [STORAGE] Failed to decompress (corrupted data)
2023/10/06 23:34:26 48958828 a0b45e09 [CRIT Client 240] [STORAGE] Failed to decompress (corrupted data)
2023/10/06 23:34:26 48958953 a0b45e09 [CRIT Client 240] [STORAGE] Failed to decompress (corrupted data)
2023/10/06 23:34:26 48959187 2d1efd8d [CRIT Client 240] [D3D12] Pipeline compilation failed [VS: , PS: ].
2023/10/06 23:34:26 48959187 1d2ca080 [CRIT Client 240] [RENDER] Pipeline generation failed. (Signature: "Metadata/EngineGraphs/base.fxgraph" "Metadata/EngineGraphs/terrain.fxgraph" "Metadata/Materials/DielectricSpecGloss.fxgraph" "Metadata/Materials/SSS_FromAlbedo.fxgraph" )
2023/10/06 23:34:26 48959203 1187100e [DEBUG Client 240] Joined guild named RIP City with 14 members
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 2d1efd8d [CRIT Client 240] [D3D12] Pipeline compilation failed [VS: , PS: ].
2023/10/06 23:34:26 48959218 1d2ca080 [CRIT Client 240] [RENDER] Pipeline generation failed. (Signature: "Metadata/EngineGraphs/base.fxgraph" "Metadata/EngineGraphs/terrain.fxgraph" "Metadata/Materials/DielectricSpecGloss.fxgraph" "Metadata/Materials/SSS_FromAlbedo.fxgraph" )
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:26 48959218 6ad7b316 [DEBUG Client 240] ALTERNATE TREE JEWEL: Applying modifications for jewel with alternate tree version = 3, seed = 1438, and keystone selection = 1
2023/10/06 23:34:27 48959328 cffb0719 [INFO Client 240] : You have entered City Square.
Hi Guys,
i had the same problem. Game was absolutely unplayable. Meaning crashes when entering the game. I tried alot including reinstalling everything. It went so far that i started playing per GforceNow.
Then i tried Cyberpunk 2077 and the new Addon (great game btw) and got a similar Problem. That lead me to this solution:

"
Figured out how to fix it. Seems like issue is specific to Intel CPUs with P cores and E cores(Like my 13900k). Someone in another post mentioned they fixed it doing the same thing they had to do to fix Remnant 2, I tried it and it actually worked, and I was able to play for 4 hours straight without any issues with just about every setting maxed.

Fix for me was: install Intel's Extreme Tuning Utility, open it and go into Advanced tuning and set each P-Core in the Performance to Core Tuning to a slightly lower value. For me it was going from 55->54(some were even at 58->54) on all the P-Cores, hit apply, minimize the Intel Utility and play the game. Rinse repeat anytime you reboot/startup your computer.

Seems like some kind of compatibility issue with Cyberpunk and other games like the Remnant 2 just not liking Intel's P/E Core architecture(12000-13000 Series).

Way too many people just blowing off this issue assuming it has to do with mods or ♥♥♥♥♥♥ computers(Kinda wished I went AMD now lol). My last two rigs ran cyberpunk fine(amd and intel), so it was a little alarming having issues with a 4090/13900k. I keep my gaming rigs clean, up to date, and pretty much as stable as possible since I work in tech and have 0 desire to do any kind of tinkering/troubleshooting outside of work.

And if I find that post again here with the fix that worked for me, Ill put an award, thank you kind person!
*

It worked for me and will hepefully work for someone else too. So thanks Zev.



*https://steamcommunity.com/app/1091500/discussions/7/3878218563600108001/?ctp=2#c3878218563599823298
"
M4XS1N wrote:
Hi Guys,
i had the same problem. Game was absolutely unplayable. Meaning crashes when entering the game. I tried alot including reinstalling everything. It went so far that i started playing per GforceNow.
Then i tried Cyberpunk 2077 and the new Addon (great game btw) and got a similar Problem. That lead me to this solution:

"
Figured out how to fix it. Seems like issue is specific to Intel CPUs with P cores and E cores(Like my 13900k). Someone in another post mentioned they fixed it doing the same thing they had to do to fix Remnant 2, I tried it and it actually worked, and I was able to play for 4 hours straight without any issues with just about every setting maxed.

Fix for me was: install Intel's Extreme Tuning Utility, open it and go into Advanced tuning and set each P-Core in the Performance to Core Tuning to a slightly lower value. For me it was going from 55->54(some were even at 58->54) on all the P-Cores, hit apply, minimize the Intel Utility and play the game. Rinse repeat anytime you reboot/startup your computer.

Seems like some kind of compatibility issue with Cyberpunk and other games like the Remnant 2 just not liking Intel's P/E Core architecture(12000-13000 Series).

Way too many people just blowing off this issue assuming it has to do with mods or ♥♥♥♥♥♥ computers(Kinda wished I went AMD now lol). My last two rigs ran cyberpunk fine(amd and intel), so it was a little alarming having issues with a 4090/13900k. I keep my gaming rigs clean, up to date, and pretty much as stable as possible since I work in tech and have 0 desire to do any kind of tinkering/troubleshooting outside of work.

And if I find that post again here with the fix that worked for me, Ill put an award, thank you kind person!
*

It worked for me and will hepefully work for someone else too. So thanks Zev.



*https://steamcommunity.com/app/1091500/discussions/7/3878218563600108001/?ctp=2#c3878218563599823298


Oh shit... that might be the fix. I was changing the multipliers down from 55 to 54 and 58 > 54 (I have a 13900k), game is running stable so far. Changed it back to default -> immediatly getting the crashes again. I guess time will tell if that is actually the fix. Will give feedback in case it is not working
Hi,
i got the same problem, i dl xtu and down from 55 to 54 then 53 ... 50 !
still bugged and ccrashed when there is a bit of density mobs.

This league i'm not able to juice any map.

Can we have a fix somedays ???
Just writing into post that as the reply above suggested, using Intel XTU to set P-Cores to 54 has stopped my crashes completely (I have an i9-13900kf). Thank you for that suggestion! Hopefully this will help GGG figure out the root cause so we can avoid this work around in the future.
Last edited by johnhageman on Oct 8, 2023, 11:11:06 PM
Same problem and I find temporal solution - steam client. Game worked fine and stable. However regular client still can't launch properly and I tried several times with clean re-install.
had the same problem. I tried different solutions. Installing old video card drivers helped, currently installed nvidia 536.23
Ryzen 5800x + XFX 6800, same error

It's not an Intel/nVidia bug...
I get the same and have a RTX 4080
This just started for me. Been playing all league no problems, and run 100's of sanctums. Latest patch seems to have broken something though, I can't run any sanctums now. Hanging out in HO is no problem though

Report Forum Post

Report Account:

Report Type

Additional Info