Technical Support - Exeption [Shader] Oodle: failed to decompress - Forum

Have the thing since exactly now, currently only when I want to do a Fortification Betrayal on a Shaper influenced Shore Map :( Running PoE standard no Steam, what to do :(	Posted by mastapetz#2737 on May 26, 2019, 7:30:49 AM Quote this Post
I can't even load the game. Every time I am about to load into the game I get this error. It's strange, it won't run PoE in 64 bit anymore and is always running the 32 bit client now. Been fighting this shit all morning, I give up. GGG fix your shit.	Posted by darkjoy#6975 on May 26, 2019, 8:17:04 AM Quote this Post
" ammo109 wrote: To the people who are having this issue and other graphics errors referencing things such as "f:\buildslave\build\production\source\windows\visual\device\d3d11\textured3d11.cpp", Error 2005270523: Open Task Manager on Windows and check to see if the game is running the 32-bit client or the 64-bit version. For whatever reason, Steam is defaulting to the 32-bit version - this started happening to me when 3.6 launched but when I was troubleshooting back then I noticed the same errors I was getting have been occurring for at least 3 years. I couldn't find a way on Steam to force the launch of the 64 bit version, but the following workaround works (replacing the default file path with the 64-bit executable): Spoiler WARNING: DO IT AT YOUR OWN RISK. I'm not responsible for anything that happens if you choose to follow my instructions. Spoiler 1. Open Windows Explorer and go to where you installed Path of Exile (by defalt that will be "C:\Program Files (x86)\SteamLibrary\steamapps\common\Path of Exile") 2. Make a copy of "PathOfExileSteam.exe" (ctrl+c, ctrl+v) for backup. 3. Make a copy of "PathOfExile_x64Steam.exe" (ctrl+c, ctrl+v) . 4. Delete "PathOfExileSteam.exe". 5. Rename the copy you made in Step 3 ("PathOfExile_x64Steam - Copy.exe") to "PathOfExileSteam.exe" by either hitting F2 or right clicking on the file and selecting Rename. This has fixed all the issues I've had with crashes and freezes since 3.6 launched. I don't know if the 32/64 bit issue is present in the standalone version of the game as well as I've never used it. This fixed it for me. Just tricking Steam into running the 64 bit client.	Posted by darkjoy#6975 on May 26, 2019, 8:26:46 AM Quote this Post
" darkjoy wrote: " ammo109 wrote: To the people who are having this issue and other graphics errors referencing things such as "f:\buildslave\build\production\source\windows\visual\device\d3d11\textured3d11.cpp", Error 2005270523: Open Task Manager on Windows and check to see if the game is running the 32-bit client or the 64-bit version. For whatever reason, Steam is defaulting to the 32-bit version - this started happening to me when 3.6 launched but when I was troubleshooting back then I noticed the same errors I was getting have been occurring for at least 3 years. I couldn't find a way on Steam to force the launch of the 64 bit version, but the following workaround works (replacing the default file path with the 64-bit executable): Spoiler WARNING: DO IT AT YOUR OWN RISK. I'm not responsible for anything that happens if you choose to follow my instructions. Spoiler 1. Open Windows Explorer and go to where you installed Path of Exile (by defalt that will be "C:\Program Files (x86)\SteamLibrary\steamapps\common\Path of Exile") 2. Make a copy of "PathOfExileSteam.exe" (ctrl+c, ctrl+v) for backup. 3. Make a copy of "PathOfExile_x64Steam.exe" (ctrl+c, ctrl+v) . 4. Delete "PathOfExileSteam.exe". 5. Rename the copy you made in Step 3 ("PathOfExile_x64Steam - Copy.exe") to "PathOfExileSteam.exe" by either hitting F2 or right clicking on the file and selecting Rename. This has fixed all the issues I've had with crashes and freezes since 3.6 launched. I don't know if the 32/64 bit issue is present in the standalone version of the game as well as I've never used it. This fixed it for me. Just tricking Steam into running the 64 bit client. This also has worked for me. I've tried the following method before proceeding with this method 1) I tried deleting "ShaderCache, ShaderCacheD3D11, and ShaderCacheD3D11_GI", and it still giving me the error. 2) I tried changing screenspace_effect=2 and screenspace_effect_resolution=2, and it still giving me the error. 3) Re-downloading the game client about 3 times, and it still giving me the error, and I also have to delete "Path of Exile" in "My game" folder before hand to make sure everything is gone before re-download. So just like the post said above, for some reason the client is intended to run 32-bit instead of 64 bits, which is kinda... weird. Anyway, cheers.	Posted by Aseki2013#4832 on May 26, 2019, 10:23:08 AM Quote this Post
Only one week until "Legion" and still this odd "OODLE" bug... I (and I think many others) can't play POE (OK in the meantime I play Grim Dawn but I really want to try the new melee skills).	Posted by Th69#3281 on May 30, 2019, 8:37:36 AM Quote this Post
Change the name of the poe client in steam folder for run x64 version work for me!	Posted by m3dyz4#5967 on May 30, 2019, 9:57:43 PM Quote this Post
I only have 32bit Windows...	Posted by Th69#3281 on May 31, 2019, 3:58:33 AM Quote this Post
I too was suffering from this the only way I got poe to run was upgrade my ram and upgrade to windows 64, tried all the fixes mentioned none worked but the upgrade has done the trick.	Posted by Macrozz#5286 on Jun 1, 2019, 11:38:32 AM Quote this Post
Only 12 hours left until 3.7, but no news about the "High Priority Known Issues"... When can I play POE again? Or will I never be able to play it again? I know that "Oodle" is an external SDK and not direct POE code, but couldn't you ignore this error and instead use a default shader (so the game continues)? Last edited by Th69#3281 on Jun 7, 2019, 3:36:02 AM	Posted by Th69#3281 on Jun 7, 2019, 3:20:55 AM Quote this Post
" Th69 wrote: Only 12 hours left until 3.7, but no news about the "High Priority Known Issues"... When can I play POE again? Or will I never be able to play it again? I know that "Oodle" is an external SDK and not direct POE code, but couldn't you ignore this error and instead use a default shader (so the game continues)?	Posted by Igronawtik_Pro#3136 on Jun 7, 2019, 2:31:29 PM Quote this Post