From the above, it appears you have been in contact with Mr Carlson. I would be interested to know how extensive or fruitful your correspondence with Mr Carlson has been
Only very recently, so it doesn't imply in the slightest that we *tried* some coordination a while ago, and it failed for some reason. If this were the case, I would have clearly said so.
Earlier, you yourself hinted that GSX could be responsible for the appalling pushback animations we see on Vatsim:
I don't know how you could understand that, by saying "maybe vPilot would need to account for that", that would mean GSX is "responsible" for causing this problem, as if you never read or understood all my previous repeated explanations about GSX **ONLY** setting some variables that clearly works correctly in local and standard multiplayer.
Yes, of course this happens when GSX is pushing, but "happening" doesn't mean "causing", considering it doesn't happen unless you use vPilot, that what it meant "vPilot would need to account for that", it means using the variables that signal the freeze, to KNOW GSX is pushing and do something about it.
That's because the normal documented LVariables GSX publish for developers to know GSX is pushing are not transmitted through Simconnect over a network, they are only valid for the user airplane (LVariable really means "Local"), so the only way to know when GSX is pushing is checking the freeze variables themselves, which should be transmitted via Simconnect, although I must say I never tested this.
Your use of the word 'maybe' concerns me in that it suggests you have not undertaken any testing whatsoever with vPilot. Please correct me if I am wrong.
I never said I made any test with vPilot myself, and why should I? Since vPilot is not Open Source, the only thing I could do would be *confirm* what users are reporting, and I have no doubts about this happening, also because I saw it in some videos of online sessions. It's not as if I could check the code and have some ideas about how to make vPilot aware of GSX.
To me this is critical to understand since any other method I have tested (Toolbar Pushback, PMDG and FBW inbuilt push back, and even simply slewing) does not result in the gymnastics we see from online users of GSX Pro. What, precisely, is 'frozen' during the pushback?
Freezing means temporarily disabling the plane's own ground physic, to prevent visual stuttering due to both the simulator's own physic simulation and GSX trying to do the same thing at the same time, which is moving the airplane in certain axes, this because it's a completely custom method with its own custom physics, which is why it does what other methods can't do, like supporting the very different Towbar kinematics, for example, since they still use in some form the default pushback method, which likely solves the in-fighting of two physic simulations automatically because it's part of the sim.
Umberto, in closing, I refuse to believe that this cannot be readily resolved by a short collaborative effort between yourself and Mr Carlson.
That's what I've been saying for a long time: it can only be fixed from vPilot's side so, clearly, it should be easier with some coordination which, again, has just started.
