Havena Posted March 20, 2017 Report Posted March 20, 2017 Hello SMP team, I am a really big fan of your addon and use it since v3. I recently occured a crash in which it was stated that SkyMaxx Pro caused it. To clarify some things, the crash occured on my final approach to KATL airport. Before the crash I noticed the frames went down a lot. I suspect my GPU could be an issue but possibly you can have a look at it and see what happened and possibly why. Any help is of course highly appreciated and I say thanks a lot for your efforts in advance. cheers Log.txt Quote
rcmarple Posted March 21, 2017 Report Posted March 21, 2017 I had a recent crash too with the log indicating SMP was the cause. Log is long gone but here's a section from the OSX crash report - hope this helps. XP Version: 11.00pb15 (398) OS Version: Mac OS X 10.12.3 ACF was the LES Saab 340 v1.3 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 mac.xpl 0x000000007ec54fe1 comp(SilverLining::CloudLayer*, SilverLining::CloudLayer*) + 33 1 mac.xpl 0x000000007ec581a5 void std::__final_insertion_sort<__gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, bool (*)(SilverLining::CloudLayer*, SilverLining::CloudLayer*)>(__gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, __gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, bool (*)(SilverLining::CloudLayer*, SilverLining::CloudLayer*)) + 293 2 mac.xpl 0x000000007ec53a41 SilverLining::Atmosphere::DrawObjects(bool, bool, bool, float, bool, void*, bool, bool, bool) + 2337 3 mac.xpl 0x000000007ec1439f silverliningDrawClouds(bool) + 377 4 mac.xpl 0x000000007ec151ce drawCloudsPreAircraft(int, int, void*) + 2220 5 XPLM 0x000000007e09c546 XPLMDispatchDrawingHook(int, int, int) + 158 6 com.laminar-research.X-Plane 0x0000000102c646e4 XPPDoDrawingHook(int) + 132 7 com.laminar-research.X-Plane 0x0000000102c6beb4 OGL_scenery_per_dome_3d_blend(xcam_class*, float, float, float, float, float, float, rendering_pass) + 5796 8 com.laminar-research.X-Plane 0x0000000102c572c3 WORLD_scene_per_render(rendering_pass, float, float, float, float) + 17763 9 com.laminar-research.X-Plane 0x0000000102c59d07 WORLD_scene_per_frame(xplane_window*, int, int) + 3623 10 com.laminar-research.X-Plane 0x0000000103238014 APP_update() + 3124 11 com.laminar-research.X-Plane 0x00000001030459ae MACIBM_post_event_proc() + 318 12 com.laminar-research.X-Plane 0x0000000102e7fc1b WIN_run_app + 43 13 com.laminar-research.X-Plane 0x0000000103264d3d main + 93 14 libdyld.dylib 0x00007fffd6913255 start + 1 Quote
sundog Posted March 21, 2017 Report Posted March 21, 2017 2 hours ago, rcmarple said: I had a recent crash too with the log indicating SMP was the cause. Log is long gone but here's a section from the OSX crash report - hope this helps. XP Version: 11.00pb15 (398) OS Version: Mac OS X 10.12.3 ACF was the LES Saab 340 v1.3 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 mac.xpl 0x000000007ec54fe1 comp(SilverLining::CloudLayer*, SilverLining::CloudLayer*) + 33 1 mac.xpl 0x000000007ec581a5 void std::__final_insertion_sort<__gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, bool (*)(SilverLining::CloudLayer*, SilverLining::CloudLayer*)>(__gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, __gnu_cxx::__normal_iterator<SilverLining::CloudLayer**, std::vector<SilverLining::CloudLayer*, SilverLiningAllocator<SilverLining::CloudLayer*> > >, bool (*)(SilverLining::CloudLayer*, SilverLining::CloudLayer*)) + 293 2 mac.xpl 0x000000007ec53a41 SilverLining::Atmosphere::DrawObjects(bool, bool, bool, float, bool, void*, bool, bool, bool) + 2337 3 mac.xpl 0x000000007ec1439f silverliningDrawClouds(bool) + 377 4 mac.xpl 0x000000007ec151ce drawCloudsPreAircraft(int, int, void*) + 2220 5 XPLM 0x000000007e09c546 XPLMDispatchDrawingHook(int, int, int) + 158 6 com.laminar-research.X-Plane 0x0000000102c646e4 XPPDoDrawingHook(int) + 132 7 com.laminar-research.X-Plane 0x0000000102c6beb4 OGL_scenery_per_dome_3d_blend(xcam_class*, float, float, float, float, float, float, rendering_pass) + 5796 8 com.laminar-research.X-Plane 0x0000000102c572c3 WORLD_scene_per_render(rendering_pass, float, float, float, float) + 17763 9 com.laminar-research.X-Plane 0x0000000102c59d07 WORLD_scene_per_frame(xplane_window*, int, int) + 3623 10 com.laminar-research.X-Plane 0x0000000103238014 APP_update() + 3124 11 com.laminar-research.X-Plane 0x00000001030459ae MACIBM_post_event_proc() + 318 12 com.laminar-research.X-Plane 0x0000000102e7fc1b WIN_run_app + 43 13 com.laminar-research.X-Plane 0x0000000103264d3d main + 93 14 libdyld.dylib 0x00007fffd6913255 start + 1 What version of SkyMaxx Pro are you using (it should be in the upper-left corner of your SMP configuration screen)? This looks like a bug I thought we fixed awhile ago. Quote
sundog Posted March 21, 2017 Report Posted March 21, 2017 14 hours ago, Havena said: Hello SMP team, I am a really big fan of your addon and use it since v3. I recently occured a crash in which it was stated that SkyMaxx Pro caused it. To clarify some things, the crash occured on my final approach to KATL airport. Before the crash I noticed the frames went down a lot. I suspect my GPU could be an issue but possibly you can have a look at it and see what happened and possibly why. Any help is of course highly appreciated and I say thanks a lot for your efforts in advance. cheers Log.txt Not a lot to go on there, but if I'm reading your log right it looks like you're running with HD Mesh installed. That could be causing you to run out of memory on your GPU, which in turn could cause SMP to crash when trying to allocate new clouds. You've also got a somewhat out of date SASL plugin installed which can cause trouble - if you can update to a newer version of your MD-80, it certainly couldn't hurt. Quote
Havena Posted March 21, 2017 Author Report Posted March 21, 2017 oh, it is the recently updated 1.3 of the Rotate MD-80, so this is what I have. The HD Mesh thing, yeah well, that was a temporary solution I already should have fixed with the new tiles LR brought out with PB14. Forgot to get rid of them. But it was on a flight from KMEM to KATL so there was no HD Mesh active for that area, not even close (lots of distance to 60°N and beyond) - but I am going to take care of it, as well with the 2K textures for the MD80, which have been released a couple of hrs ago. So it is most likely a memory issue which can be fixed on various ways. Thanks a lot for your help. Quote
rcmarple Posted March 21, 2017 Report Posted March 21, 2017 Thanks for the response @sundog - version I have is 4.0.1 (although the version.txt file says 4.0). Created date on the actual plugin is 18 Dec 2016. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.