Hi Guys,
Sorry I've missed this thread upto now, and thanks to Charl (Wing_Z) for pointing it out to me.
And Jamie, thanks for respecting my wishes about not re-distributing my beta to others !
About that: the reason I request this on beta's, is a very simple one: for pre-versions of any of my gauges, I just want to know exactly who has what; otherwise, upon a release, it's impossible for me to give proper support with all those pre-versions floating around. And I have learned that the hard way over the years :isadizzy:.
Now, about me not releasing this "refuel/auto-track/auto-follow" solution, which I advertised last year, sofar: I really couldn't have said it any better or more precise then Jamie did a few posts back.
To add to that: In general, I am very reluctant to release anything (freeware or not) to the public, if it doesn't adhere to my own standards for:
- Is it comprehensable ?
- Is it fool-proof ?
- Is it stable (within limitations specified), and without apperant bugs ?
If only because I want to avoid to be swamped with support questions.
And this "feature" clearly doesn't qualify.
For those who know my work in FS-design: I'm always looking to create addon stuff that:
A. I (me) am interrested in myself.
B. Is a kind of a "niche" in FS-design.
And to that, this "feature" DOES qualify (as Jamie can confirm
).
That said:
The two major technical problems that I'm facing in this addon, and which made me give up the idea:
1. The accuracy with which FS gives the exact location (in its variables) of an AI-aircraft or user-flown aircraft in any point in time.
In short: that s*cks. Normally, you wouldn't notice this at all, but in an application where you want to control a fixed distance (within a meter or so) between a user-aircraft and a AI-tanker, both flying at 200 Knots or so, the result IS influenced strongly.
Example: calculating aircraft speed based on the difference on read coördinates and elapsed time each 50 msec, can give fluctiations of up to 40% in calculated speed.There are enough tricks to "average" this, but still.....
2. I'm relying on Eric's (payware) Radar gauge, to get the position of a selected AI-tanker and it's heading/speed, in XML variables (this is an undocumented feature of Eric's gauge). However, on occasion and with short spikes, these variables contain erratic values (Eric couldn't pinpoint this problem). Probably system-dependant.
The result being, that the distance between a user-aircraft and AI-tanker, visibly might quite vary. To the extent that sometimes the user aircraft suddenly is even ahead of the Ai-tanker on occasion.
For me reasons enough to not release it, since I can think of no better working alternative implementation.
However, if there's still interrest in it (given the above), I'm willing to mail you an UNSUPPORTED version for you to try.
Just send me a PM with your Email adress, and I'll mail you a test package; I just need some time to bundle everything up again, since I haven't touched it for almost a year.
Needless to say, this package isn't for the "casual" flightsimmer, because it isn't a plug-and-play feature.
And you DO need to have Eric's Radar gauge (V2, the payware version) installed, otherwise it's pointless.
:ernae: Rob