rcmarple

I had to buy a new joystick after upgrading OS a few years back - apparently some Saiteks don't use Apple's USB protocols and Mac OS got fussier about it.

YAY - huge improvement and thanks for making this change . I can't deny it was always a worry if troubleshooting a glitch that I'd run out of downloads so great to see that the limits are gone! I can also now delete my stash of XA installers

Thanks for sharing the update - quick question, which ACF should I use for XP11.01r1 (current version as I write): I'm guessing it's either the first one or the fourth one?

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.

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

I think NOAA Weather overrides all other settings and will always load real weather. Try removing this, then you should be able to set the weather manually. Hope this helps.

Try unzipping the archive with a different app - this one works for me with problem files: https://itunes.apple.com/us/app/decompressor/id1033480833?mt=12

Ta very much.

Quick question - if I was able to install v1.1 with the original installer, do I need to re-install with the new "Sierra" version I got an email about? i.e. Has the actual plugin changed or just the way it is packed?

Taking the archive out of the bin after download, then unzipping with StuffitExpander (v15.0.7) worked for me. Mac OS 10.12.2

I think I caught the effect quite well here -

Looking forwards to the update - thanks for all the hard work!

Worked fine for me this week - all up to date and patched. Here's the list of my third party plugins... AutoGate/ ChaseViewDeluxe/ CustomSBDatarefs004/ FJCC_FMC/ FJCC_x737FMC_mac.xpl FSWidgetsGMap/ Gizmo64.plugin/ GndHandling/ HSAIRXPL-Mac-64.xpl planecommand/ QPACTerrainData/ RealWeatherConnector/ SilverLining/ XHSI2_plugin/ xreloaded/

Post your log and someone may be able to take a look...

I'd try it without the HD meshes. As Jan says, memory may be the issue and the HD mesh might just push things over the edge?