captainamerican Posted November 26, 2015 Report Share Posted November 26, 2015 (edited) While it is too early to decide whether the new update is already bugged, because every system and setup varies, this warning goes out only to Mac OS X users. However, I would recommend Windows users to take a look at this as well and comment if you have noticed anything. Dear fellow Mac Users, I highly recommend holding off on the current update because there are issues between X-Plane and 3rd party plugins. One of these is SASL; causes the system to crash every time. This is straight from my Log.txt: --=={This application has crashed because of the plugin: SASL}==-- Guys, if you are the type to frequently install betas, please skip this one. I hope this whole post wasn't redundant, because perhaps I'm the only one who had done this to myself so far Happy Flying and Happy Thanksgiving. EDIT: PROBLEM SOLVED:Dear Mac Users who are running OS X EL CAPITAN. Please make sure your aircraft are using the Newest Version of SASL to avoid any compatibility issues. (Read Ben's Post at the bottom of the page) Edited December 4, 2015 by captainamerican 1 Quote Link to comment Share on other sites More sharing options...
niebieski Posted November 26, 2015 Report Share Posted November 26, 2015 Are you referring to 10.42rc1 -> 10.42 (final) patch?I'm on Windows 8.1 and everything's fine here. Any chance your problem is related to this? Quote Link to comment Share on other sites More sharing options...
otto Posted November 26, 2015 Report Share Posted November 26, 2015 Runs fine on my old Mac Pro in El Cap and Snow Leopard. Quote Link to comment Share on other sites More sharing options...
mmerelles Posted November 26, 2015 Report Share Posted November 26, 2015 no problem here, imac + el capitan Quote Link to comment Share on other sites More sharing options...
captainamerican Posted November 26, 2015 Author Report Share Posted November 26, 2015 Ive just noticed some problems running B777 ever since the update. Seems like an issue: Notice in the screenshot, the altitude is increasing even though Im on the ground with the engines off. I also hear sounds like flap movements and fire warnings randomly, and finally as I click the aircraft menu, the program crashes. This has happened to me countless times.. Quote Link to comment Share on other sites More sharing options...
captainamerican Posted November 26, 2015 Author Report Share Posted November 26, 2015 Are you referring to 10.42rc1 -> 10.42 (final) patch?I'm on Windows 8.1 and everything's fine here. Any chance your problem is related to this? Yes, it is related to that. Now I am unsure of what to do. Quote Link to comment Share on other sites More sharing options...
captainamerican Posted November 26, 2015 Author Report Share Posted November 26, 2015 Okay Guys, Problem is Solved. I was running the FF777 and 757 older versions, So i updated and reactivated all my aircraft to newest versions which run the newest and most compatible SASL. However, since I like the B777 v1.7 because of Pumpers Cockpit, I downloaded the patch here and installed it on v1.7 without any problems so far. Quote Link to comment Share on other sites More sharing options...
bsupnik Posted December 2, 2015 Report Share Posted December 2, 2015 Hi,I highly recommend holding off on the current update because there are issues between X-Plane and 3rd party plugins. One of these is SASL; causes the system to crash every time. This is straight from my Log.txt: --=={This application has crashed because of the plugin: SASL}==-- This is definitely wrong. There is no compatibility problem between X-Plane and SASL. What has been happening is SASL has been crashing X-Plane on El Capitan for --months-- now. This is just the first time we reported this crash for what it is: a plugin crashing the sim. In 10.41 the exact same crash happens, except you get an Apple crash report. If you speak Apple crash dump, you'll see a plugin (that is in fact SASL) on the stack causing OpenAL to abort. The problem is that Yosemite broke X-Plane's automatic crash reporting (via break pad) and with that we lost the code that annotates whether a plugin or the sim was running at crash time. The annotation is now restored (unfortunately without auto-crash reporting for X-plane..that's a much harder thing to solve). For the last few months I have just received a huge number of "bug reports" from users, sending in Mac crash reports that were attributable to SASL. I put the annotator back into 10.42 to stop the torrent. The fix for SASL is already available for freeware aircraft - for payware, the vendor has to roll a patch. Here's the details. http://developer.x-plane.com/2015/11/sasl-crash-fixed-youll-need-a-new-sasl/ 3 Quote Link to comment Share on other sites More sharing options...
captainamerican Posted December 4, 2015 Author Report Share Posted December 4, 2015 (edited) Hi, This is definitely wrong. There is no compatibility problem between X-Plane and SASL.. http://developer.x-plane.com/2015/11/sasl-crash-fixed-youll-need-a-new-sasl/ This is the same exact conclusion that I have drawn based on all these experiences. So far, JAR and FF have done their part and updated their aircraft. EDIT: This is exactly why the warning goes out to Mac Users haha. Thanks for clearing it up sir! Edited December 4, 2015 by captainamerican Quote Link to comment Share on other sites More sharing options...
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.