Exeption [Shader] Oodle: failed to decompress

I still crash on every map/zana, great experience.

day 2 since the patch and almost unable to play the game.

I altered the file that was mentioned earlier. Like a few others it had a slightly different name but I searched for effects and found and changed it to a "2".

That helped and I was able to run the Twilight Strand all day.

I tried the compatability mode and I dont see a difference.

Logging onto my main, a trickster soulrend, I can stand in town, in hideout, and thats about it. I crash as soon as any monster comes onto my screen with any kind of effects. An aura or a splashy blood effect anything. Ive made it maybe 20 seconds in any map.

Logged into the flashback leagues and have the same issue. Casting with no monsters on the screen does not seem to crash me. Somehow the issue is when monsters show up. This is so frustrating for me since Im at 33/36 challenges done and I was really hoping to use this time to finish my wings!!!

Until this last little update I ran the game more or less flawlessly.

Have same problem. Nothing mentioned in thread helped me. Sad that this happened durning such unique and short experiance like flashback. Hope guys from GGG fix that fast

I can't play it after patch, so sad...

delete this on main folder
(ShaderCacheD3D1,CachedHLSLShaders)

Any change after last patch?

I'm currently playing in my laptop with Win10 using the 64 bits app from Steam, it runs normally.

On the other hand, in my PC with Win7 32 bits (can't run the 64 bits version) it had a little improvement; now, it doesn't crash before logging, at least I can reach to log with any character, appear in a zone that looks like Silent Hill (full of fog) and then crashes with the same oodle failed to decompress, so, an improvement overall, I guess.

The only recommendation that I can give is, if you can, play in a 64 bits system.

I got this issue aswell. So sad when wanting to join the last few hours of the league to get the free mtx at level 35...

after the new patch yesterday my game work but if I log my previous char the oodle will com up again. Then I tried to create a new char and i can play it but at the time I reach Hillock the same error will appear again.

what's happening here GGG we hope you will find other solution for this.

Same here.
When I reach Hillock the error comes again.

Maybe I got something for you, if you are running PoE on Steam:
Steam now has an additional option in "Settings" (Steam --> Settings), which is called "Shader Pre-Caching". It was on by default, so i deactivated it and deleted all shader caches from the game directory.

No crashes so far...will update if it is changing.

i am running PoE on 64 bit with admin permissions, without other compatibility modes.