Search the Community
Showing results for tags 'not responding'.
Found 3 results
Hi, I purchased this game on a sale last year and only started playing this now. It keeps hanging then eventually gives a "Pillars of Eternity is not responding" message. Here are the screenshots for the hanging and the error message: https://imgur.com/a/MCxZMKK It seems to happen every time a new "area" or "event" is triggered while exploring the local map. Things i tried before posting: 1. Verified Game Files 2. Set Power plan to high performance 3. lowered graphics 4. gave admin permissions to .exe What's happening? Attached are the output and the dxdiag log output_log.txt DxDiag.txt
Hello there, I've just bought PoE and was full of anticipation. But after creating my character, the game keeps crashing.. It crashes to desktop a few seconds after loading a savegame - I couldn't play further than to the first wolf. This happens with the "game is not responding" message. I already verified the game files via steam and observed the takes manager while "playing": CPU won't go higher than 50%, memory won't go higher than ~1,2 GB. The video card driver is up to date. I attached my system specs and the output log (should be playable with windows 10 64bit). Does anyone know a way to solve this? What I've seen so far lets me really wanna play this game.. output_log.txt DxDiag.txt
When this game launched I reported many bugs. Among them was the black screen at the kick starter logo lock up. The black screen launch lock up STILL persists in v2. The game will only launch to menu 1 out of 5 to 6 launches. From there my saves are constantly corrupted and loading them results in looping back to the menu (if you can get to the menu in the first place) When I originally reported this a dev eventually "fixed" my saves then sent them back to me WITHOUT fixing the game problem that caused it. Which is to say my "fixed" saves were corrupted as soon as they were used. Starting a brand new game with v2 my new game I started a day ago is now also corrupted causing the same loop back to menu.