Tim/Rodeo314 Posted December 10, 2018 Share Posted December 10, 2018 (edited) First, just a note that https://forum.aerosoft.com/index.php?/files/file/5007-sam-scenery-animation-manager/ lists "X-Plane 10 Version 10.00+"; I gather the Aerosoft forum doesn't allow for specifying an XP11 version, but may I suggest setting the "X-Plane 10 version" to either 11.10+ (11.10 required since you use new SDK 3.0 packaging rules) or at least "Not applicable"? Then, perhaps more importantly, your macOS plugin appears to be built against macOS 10.13: Load command 8 cmd LC_VERSION_MIN_MACOSX cmdsize 16 version 10.13 sdk 10.13 …whereas X-Plane 11 itself can run all the way back to macOS 10.10: https://www.x-plane.com/kb/x-plane-11-system-requirements/ Since you're most likely not using any macOS 10.13+ only APIs, specifying -mmacosx-version-min=10.10 should be enough to ensure compatibility with 10.10 or later, regardless of the SDK used. Regards, Tim Edited December 10, 2018 by Tim/Rodeo314 Link to comment Share on other sites More sharing options...
Marten@Stairport Posted December 10, 2018 Share Posted December 10, 2018 Hi Tim thanks for your feedback. The Aerosoft File Details are changed. Can you confirm that the plugin is not working/loading in macOS 10.10? Greets Marten Link to comment Share on other sites More sharing options...
Tim/Rodeo314 Posted December 11, 2018 Author Share Posted December 11, 2018 I can only confirm it does not load under 10.12 Log.txt Link to comment Share on other sites More sharing options...
Marten@Stairport Posted December 11, 2018 Share Posted December 11, 2018 And is there a specific reason why you don't use 10.13? Link to comment Share on other sites More sharing options...
Tim/Rodeo314 Posted December 11, 2018 Author Share Posted December 11, 2018 I just haven't really bothered upgrading. You should probably indicate the minimum macOS version somewhere, especially since it doesn't match the X-Plane 11 system requirements for macOS. BTW, we can turn that question around: is there a specific reason why you plugin requires macOS 10.13 or later? Link to comment Share on other sites More sharing options...
Folko Posted December 11, 2018 Share Posted December 11, 2018 (edited) According to the log, X-Plane loaded the plugin successfully, but it had an error during the initialization phase. Did it create a sam.log file in the plugin directory? Since it even put the version correctly into the log, the version of your OS seems to be supported, otherwise it would have failed sooner. Edited December 11, 2018 by Folko Link to comment Share on other sites More sharing options...
Tim/Rodeo314 Posted December 11, 2018 Author Share Posted December 11, 2018 Good point; issue is: 18:33:35 e: Exception in XPluginStart: Couldn't open file: /Volumes/Z4ALL/XP_DEMO_V_11/Custom Scenery/scenery_packs.ini I had just deleted preferences and scenery and run the updater to make sure I had clean demo, this was the initial X-Plane launch without a scenery_packs.ini file. I do tend to sometimes delete the scenery_packs.ini so that X-Plane regenerates it (if you keep the Custom Scenery folder organized by name, deleting and letting X-Plane make a new one is easier than hand-editing said file; Mac users can't use xOrganizer). Plugin should be able to handle this gracefully? Whatever it needs to look for, if there is no scenery_packs.ini SAM should be able to safely (and correctly) assume all airport-type or overlay-type packages (which I what I gather SAM only really cares about) will get loaded by X-Plane? I guess X-Plane does actually skip packages where it finds an apt.dat with a version number newer than the version of X-Plane (e.g. sceneries with 1100 apt.dat files do get skipped by XP10), but that's about it. Link to comment Share on other sites More sharing options...
Folko Posted December 11, 2018 Share Posted December 11, 2018 (edited) Thanks, the empty scenery issues is already known and will be fixed in the next version. Apart from that, did it work on the next start (i.e. after X-Plane generated the ini)? Edited December 11, 2018 by Folko Link to comment Share on other sites More sharing options...
Tim/Rodeo314 Posted December 12, 2018 Author Share Posted December 12, 2018 It does indeed appear to work, thanks! 1 Link to comment Share on other sites More sharing options...
OKernel Posted January 9, 2020 Share Posted January 9, 2020 I am a bit confused about minimum MacOS requirement. All documentation says MacOS 10.14+, yet this thread indicates to me that it may run on 10.13 (?). Regrettably, my hardware will not go beyond 10.13. Link to comment Share on other sites More sharing options...
Marten@Stairport Posted January 9, 2020 Share Posted January 9, 2020 You're referring to a 1+ year old thread. The current version of SAM requires 10.14+. Link to comment Share on other sites More sharing options...
OKernel Posted January 12, 2020 Share Posted January 12, 2020 (edited) Thanks Marten. Before you responded my over-zealous self laid down the shekels for WorldJetways from Aerosoft, which was the reason I was after your wonderful SAM in the first place. I am pleased to advise that it works a treat on my mid-2011 iMac running MacOS 10.13. I understand that SAM may not work with other programs for me, but that is OK. Just sayin' Edited January 12, 2020 by OKernel Link to comment Share on other sites More sharing options...
Marten@Stairport Posted January 12, 2020 Share Posted January 12, 2020 Sounds great! Link to comment Share on other sites More sharing options...
Recommended Posts