Goonie...
Long time, buddy. Yeah, I may do that when I get a chance and enough passes to warrant sending the logbook file.
My suspicion is that the meatball, the visual model, and/or the glideslope reference point are not matching up or have some type of flaw that we are missing. I know that the carrier visual model is not correct. A while back, was flying with Molly (SYM;ShutYoMouth) Badger and she pointed out something that Sandpro and his gang found out... the carrier dimensions are not correct. If I remember, I think the FSX version is smaller and its compounded by the fact that the overlap of Javier's carrier makes things a little disoriented.
The reason I have my suspicions is that what we see in FSX (carrier meatball and wires) dont represent well and the fixes I've done with the Sludge (wire caught pee-pee dance) using this knowledge that the carrier physical model and activity (wire catch zones) areas dont match up. IMO, a possible vLSO fix would be to move the g/s datum points backward, so that they correspond with the visual model, to make the whole process transparent to the vLSO user. Essentially, the cause of the pee-pee dance was that we were doing a midair engagement on every pass. The wire engagement zones are above and behind of the physical model depictions.
In my opinion, this might be another FSX vs. real-world go-between fix because of FSX carrier's physical model overlay and incorrect scale size difference.
Later
Sludge