Well with all the software mods I’ve made to the sim in the past few weeks something was bound to go wrong….   Somewhere in amongst the UFC/DED stuff I have implemented must have been some sort of auto-throttle code…..  Part way through tonight’s mission I discovered that I had lost throttle control, yet the engine RPM was increasing and decreasing on it’s own!    Aborted the mission, and tried to figure out what was going on…   One of the functions I have implemented from the SimScape F-16C panel was the “Autopilot” display on the HUD.  It appears that somehow there is an Autothrottle/speed function tied into that display, and during the flight got activated.  Since the A-4 flight model wasn’t designed to have autothrottle (yet it was still enabled in the config) the accel/decel gains were set at some really low figures meaning a really slow responding autothrottle.  With a bit of work I managed to get it working well enough to *survive* the approach and landing back at Ohakea.

First half of the mission was great, cross country NAV to Ohope, then out across the Bay to “attack” White Island:

 

And that’s about where it all came unravelled 🙁   The trip back to Ohakea was boring just trundling along on autopilot (and autothrottle as it turns out) then slide down the groove to land…..

Only glimmer of happiness;  Got to see an Andover taxi in after I landed.  I love “bumping in to” my RNZAF AI aircraft as I fly around 🙂

NZ6258 rolled into maintenance, and had the Autothrottle disabled in the config….  *should* be good now!

[osm_map_v3 map_center=”-38.862,176.165″ zoom=”7″ width=”100%” height=”450″ file_list=”http://ta4ksim.com/tA4K%20Log/2017/201707082104_Default.kml” file_color_list=”#ff0000″ file_title=”201707092019_Default.kml”]

By SeanG

Leave a Reply

Your email address will not be published. Required fields are marked *