I’ve finally worked out what is causing it and how to fix it. GSX is the culprit. Sorry Umberto.
GSX is not the "culprit". The "culprit" is, of course, is the fact the simulator doesn't create Simobjects in the background so, obviously, GSX MUST create its objects at some time, and that's not any different than, for example, UT Live pausing for 15-20 seconds AND stalling the whole simulator, while it creates its own traffic.
There are several reasons why GSX objects are not created more in advance, for example when you select the gate in flight:
- To know were the gates are, GSX must loads the scenery .BGL and it loads only one file, the one for the airport closest to your position. But if you select the gate in flight, the closest to your position might not be the one you are going to land on. Another .BGL might be the closest one and GSX might have already loaded its jetways for it so, in that situation it would have to first make a PAUSE to *destroy* the jetway of the closest airport and, when you decided the gate for the remote airport, eventually re-create them again if you still in range of an airport that used GSX L2 jetways.
- When you are far from an airport, the terrain mesh is completed only very close to your airplane, but it's uses a way lower resolution further away, so if we tried to place objects on ground from a distance, they would end up placed on the "wrong" mesh, so you see floating objects.
So, if that pauses concerns you, just don't pre-select a gate in flight. I was never a fan of that feature, because I knew it would come with complications, but users were so vocal about it, that we added it anyway.