deleff

Hi, original poster here. Is there any update on this from the programmers? I'm still getting the same behavior, after the update to PoE version 2.

I'm curious if any news, cuase, or suggestions to address this problem are as yet identified. Thanks.

I'm verified the integrity and am still experiencing the same issue. I'm running 1.0.6.0617. The most relevant parts of the crash log to my eye are: Crashed Thread: 4 UnityGfxDeviceWorker Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called Application Specific Signatures: Graphics hardware encountered an error and was reset: 0x00000003 And then the specifics of that thread: Thread 4 Crashed:: UnityGfxDeviceWorker 0 libsystem_kernel.dylib 0x00007fff8d209286 __pthread_kill + 10 1 libsystem_c.dylib 0x00007fff95370b53 abort + 129 2 libmono.0.dylib 0x00000001016dc44a mono_handle_native_sigsegv + 732 3 libmono.0.dylib 0x0000000101723e3b sigabrt_signal_handler + 100 4 libsystem_platform.dylib 0x00007fff953f1f1a _sigtramp + 26 5 libsystem_kernel.dylib 0x00007fff8d209286 __pthread_kill + 10 6 libsystem_c.dylib 0x00007fff95370b53 abort + 129 7 libGPUSupportMercury.dylib 0x00007fff9298eb81 gpusGenerateCrashLog + 173 8 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340044249f gpusKillClient + 9 9 libGPUSupportMercury.dylib 0x00007fff92990068 gpusSubmitDataBuffers + 500 10 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400003c98 IntelCommandBuffer::getNew(GLDContextRec*) + 48 11 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340010939d intelSubmitCommands + 191 12 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340005dd23 Gen7Context::CheckOOM(USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, USC::IM_Shader*, unsigned long long, bool&) + 1665 13 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400105973 Gen7Context::CheckOOM(unsigned long long, bool&) + 103 14 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x0000123400100843 Gen7Context::ProgramPipeline() + 91 15 com.apple.driver.AppleIntelHD5000GraphicsGLDriver 0x000012340044dbe8 glrIntelRenderVertexArray + 328 16 GLEngine 0x00007fff8df17f46 glDrawElements_ACC_Exec + 526 17 unity.Obsidian Entertainment.Pillars of Eternity 0x000000010072eb14 ARBVBO::DrawInternal(ChannelAssigns const&, void const*, unsigned int, GfxPrimitiveType, unsigned int) + 436 18 unity.Obsidian Entertainment.Pillars of Eternity 0x000000010074e4e5 GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&) + 12421 19 unity.Obsidian Entertainment.Pillars of Eternity 0x000000010074b33c GfxDeviceWorker::RunGfxDeviceWorker(void*) + 76 20 unity.Obsidian Entertainment.Pillars of Eternity 0x000000010047620a Thread::RunThreadWrapper(void*) + 58 21 libsystem_pthread.dylib 0x00007fff94df4268 _pthread_body + 131 22 libsystem_pthread.dylib 0x00007fff94df41e5 _pthread_start + 176 23 libsystem_pthread.dylib 0x00007fff94df241d thread_start + 13

I will add that I have not always had this difficulty. It's only recently that this crashing behavior began to manifest.

Thanks for the response, celliot. I'm running OS X 10.10.4 if that factors into this. On the OS, what was the power options I think are now known as "Energy Saver" settings. Regardless, I see no option to modify GPU related activity under that section or the Display properties. Also note that this MacBook Pro has the Intel Iris chipset, and does not have the capability of switching between the integrated and a dedicated GPU. I looked in the game options as well, in case you meant an setting there. I did not find this as a game setting, either. (I did not expect to, but thought to check just to be certain.)

Thanks for the response, bartlebooth. I unchecked the "Enable Steam Cloud synchronization for Pillars of Eternity" and am still experiencing the same behavior.

Are you running on OS X (perhaps on a laptop?) I have started to observe the same behavior. A crash upon transitioning areas, but the autosave is created and may be loaded after restarting the game, upon which my party is placed in the new area and all works fine until the next area transition. I've posted an issue and linked support data.

Description =========== Game will consistently crash upon entering a new area. The transistion screen with tips will show, then the cursor will switch to the Mac OS X "beachball" and then the game will exit, dropping to the desktop and producing the OS X Problem Reporter with the crash data. The autosave will occur during the transition, and the game load the save game in the new area upon restarting. Steps to Reproduce ================== Leave the current area and enter any new area. Link to support data ==================== https://dl.dropboxusercontent.com/u/7529996/deleff-PoE_crash_data.zip