If not already done, i challenge Umberto and the team to reach out to the vPilot developer(s) and start an initial discussion on the matter to find a common solution.
If you followed my replies, you would have known this already happened, and mr. Carlson has been informed with my latest post, which confirmed the underlying issue is inherent in the way the sim works, and a solution.
However, I don't think it is correct from my side, continuing to update users about any progress, or the eventual lack of it: if mr. Carlson decides to act on this or not, it's his own prerogative, in his own time, and it's not up to me to constantly report this publicly, or even soliciting him in any way.
I guess there MIGHT be a possible solution on our side, in case vPilot won't be updated for some reason, but the solution would be very cumbersome, bad for performance (Simconnect traffic) and unnecessarily complex, worse for everybody compared to a much cleaner solution from vPilot because it would require the following:
- A separate Simconnect app, that we would have to write from scratch, that must be run in parallel to vPilot. We couldn't done it from GSX, since it would force to install GSX even for those that don't use it, so it must be a separate app.
- This separate app, will need to *constantly* monitor ALL AI planes created by vPilot, check when they become frozen by GSX, and Disable their simulation, so it won't interfere with GSX movement.
This MIGHT work (in theory at least), but it's so much worse than a vPilot solution, because we would need to constantly scan all created airplanes, increasing traffic over Simconnect and putting extra strain on the sim, with the added annoyance of another app to start.
Clearly, vPilot could make it much better, since it already has a list of airplane it has created, so it can do it way more efficiently and reliably, without any need for a separate app to start.