![fspassengers x plane 11 fspassengers x plane 11](http://www.dansteph.com/screenshots/180315-144523_FsPassengersP3dv4.jpg)
A crash is a plugin crash (and you see the “we crashed because of a plugin: XSquawkBox” or whatever) if the sim crashed while executing code on behalf of a plugin or inside the plugin on the main thread. We categorize crashes into plugin and non-plugin crashes starting with 11.32 we actually get a statistical picture of this. This is a deployment problem that really needs to be solved, but it’s orthogonal to true app crashes.) (There is an in-between area where an add-on is mis-installed because it has a library dependency that the user hasn’t met. That is, they are caused by an add-on that should not have shipped. While I would like to make this code less hostile to users, it’s also worth noting that these cases are ones where the author of the scenery pack would have been able to fix this if they had loaded their own work even just once. This failure mode is user hostile in that you can’t fly, but it’s not a crash – the refusal to load is the code working according to design. ter file, the sim will refuse to proceed and quit.
![fspassengers x plane 11 fspassengers x plane 11](http://www.fspassengers.com/design/trydemo1.jpg)
For example, if you load a DSF with a missing. The sim quitting on purpose because of bad content is not considered a crash. This number has been remarkably stable – it’s not a ton different between 11.26, 11.30, 11.31 or the 11.32 beta. X-Plane’s overall crash rate (all causes is approximately 14% – which is to say, for all of our users using analytics, for every 100 times they launch X-Plane, the sim quits in a way we did not expect or want 14 times. The more gathered data we get about crashes, the better shot we have at addressing the issues. The rest of this post gets into the weeds if you tune out (and I won’t fault you if you do) the TL DR is: please turn on our anonymous analytics, and click “send” if you get the crash report form. We have learned some things about X-Plane’s performance and stability though.
#Fspassengers x plane 11 series#
We really haven’t found a series of smoking guns we could fix to improve stability. Over the last few weeks we have spent a tremendous amount of developer time investigating reports of instability, crashes and performance problems, and the results have been quite unsatisfying.
![fspassengers x plane 11 fspassengers x plane 11](https://i.ytimg.com/vi/XytHYSjG8_c/maxresdefault.jpg)
Our own server should serve the latest weather we have, whatever that is. NOAA weather was plagued by 404s when the server posted METARs didn’t meet the date/time scheme X-Plane expected. The big item for RC2 is that X-Plane now uses our own replicating METAR servers. If you think RC2 changed your framerate from RC1 (for better or worse), it is imaginary. While yes, I know I can go edit the aircraft.cfg to make my custom dreams happen, it's a little disappointing when other studios like Milviz have the cockpit tablet that will configure the interior in-sim, on the fly.We’ve posted X-Plane 11.32 release candidate two – it contains very few changes from release candidate one. While you get use to it, sometimes the color you want doesn't have an interior to match. Looking at liveries assaults your eyes with a wall of colors and text. The other is interior and livery management. One is that when you rotate your head in the cockpit to look backwards, the turbine SFX gets eerily quiet. Sounds are great and the number of cockpit clickables will keep you entertained. The exterior is absolutely gorgeous and is a screenshot machine from any angle. The plane moves and behaves as it should, and all of the control systems look to work relatively bug free. If you have any familiarity with Simworks Studios last plane, the CH701, you'll know they make a solid product.