Not sure if this is the right place to put this or not. I've been playing with the file, trying to make it better, and I seem to have hit a wall. No matter what goal range I set, target speed, etc. I will almost always eventually overshoot. So, I did some testing and found that it works absolutely wonderfully at low altitudes. I match the target's speed once I'm about 3 nm away, and ever so slowly inch my way towards it as it turns and stuff, but never get within 1 nm of it. I know the original idea was to make the AP maintain formation, and I think that is still possible with my settings, since it will match the target's speed once it's within 3 nm of the target.
The problem sets in when I climb to altitudes above 10,000 ft. The target speed is ALWAYS too high, no matter where I am in relation to the target. Anyway, after a recent flight, I concluded that the speeds that the script is plugging into the AP must be in KTAS. This explains why it will work perfect at low altitudes, but leave me to play with the throttle manually at higher altitudes. So, I was wondering if there is anyway to get the script to recognize speed in KIAS, and use that instead?
You may be wondering, why would I want to take the fun out of maintaining formation with someone? Well, I like making videos, and I doubt a pilot would actually hold a camcorder and aim it at another plane, while trying to fly very close to it without crashing. Sure, s/he'd mount the thing somewhere in the cockpit, but that's about it, UNLESS a passenger takes the camera, and acts as cameraman. Basically, the idea is to give all planes with good APs functionality that is similar to the mibs. No, I wouldn't be satisfied just using the mibs, even if mine worked.
So yeah.... I will be very happy to receive any suggestions on how to modify this script, then I will apply them, test them to make sure it works as planned, and then release it right here! You'll just have to copy and paste the text and overwrite your copy of target_track.nas.