UNABLE TU LAUNCH GAME [SHADE] OODLE: FAILED TO DECOMPRESS
I went to Compatibility options and turned on change high DPI setting all on.
That seemed to work for me.... Before that tried everything posted on this forum page. So good luck P.S I also already had run as admin for both .exe for POE. | |
I have the Same issue and i am running not the Steam version.
It is not a Steam-only Problem Pls fix this! |
![]() |
" Thats worked for me. Thanks a lot man. |
![]() |
Tried everything on this thread and the other one as well to no avail. I have redownloaded the game twice as standalone and twice through steam. Still getting the same error. What else could be the issue?
|
![]() |
I just installed the game by firts time, and give me that error, I tried everything posted, There are any solution?
|
![]() |
Quoting a solution from another thread that worked for me and others:
" |
![]() |
" This worked for me. Managed to log in and invite someone to my guild. win 7 sp2 32-bit client running PoE as admin |
![]() |
I can't use the solution of the file production_Config.ini, because the document is empty I never played before. I don't know if I reinstall the game could fixed that or just was a wasted of time
|
![]() |
" I attempted this from the other thread with the same error. Unfortunately, my production_Config.ini file didn't contain that string of text/value. But just for giggles, I removed the folder and did a fresh install for the 3rd time. The same production_Config.ini file is now empty. Copied the command in manually, nothing. Also attempted re-added the original production_Config.ini file to see if I could manually add the value. Also no good. Installed PoE on my Laptop, running the exact same software/antivirus I run on my Desktop. PoE Running fine on an old GTX 860m laptop, but the error continues on my GTX 1080 equipped desktop. In fact, my laptop seems to not have the crashing issue I started getting with Synthesis league. Last edited by VozVal#2994 on May 5, 2019, 2:27:57 PM
|
![]() |
Tried fixes, none have worked. Still getting error.
|
![]() |