4 ms·
The Connect API for X-plane is a great toy. I wrote a "recover from upset" script some years ago after having a discussion on the best methods for upset recover
by t0mas88 3y ago
The Connect API for X-plane is a great toy. I wrote a "recover from upset" script some years ago after having a discussion on the best methods for upset recovery by human pilots. You can easily implement something that does what a human would do and then compare other options that may be possible.
The one thing that does make it a bit "easy mode" is that all data is clean and exactly as you would expect mathematically. While real input data for avionics is more noisy and has several types of sensor errors.
- sokoloff 3y agoIt also seems like the chance of having had sensor failure or disagreements is higher in cases where a human pilot (or autopilot) has lost control of the airplane or exceeded autopilot limits. (It’s by no means all cases, but some LoC incidents are initiated/contributed to by a sensor or avionics failure.)
- t0mas88 3y agoAbsolutely. I've had an instrument failure (invalid attitude indication) cause an autopilot issue that put the aircraft in an upset state in seconds. From there you're manually recovering based on limited data. Fortunately this is a key part of training and unlike the autopilot a human pilot knows to look at the backup instruments and make a judgement on what data is correct. But that judgement is very hard to code into an automated system. Because there is also a bit of trial and error involved. If indications don't follow your inputs, you're going to assume those indications are wrong and put more weight on the others.
- auspiv 3y agoThe numbers coming from X-Plane are indeed super "clean" and very mathematically expected. No lag on VSI, etc
- stavros 3y agoIt should be easy to inject some lag and noise on the plugin end if you want to simulate that, no?