When you first call GSX, it's entirely normal you'll see a pause, because the sim is creating all the GSX vehicles, so it will stop until they all appear. There's nothing you or we can do about this, because that's how the sim works when objects are created.
However, it's not normal that, after all the GSX objects are already visible, that every subsequent command would result in pauses, especially those that do not belong to GSX.
I cannot reproduce this, but I can make some guesses:
- You changed the sim affinity mask somehow, maybe because you read some suggestions on forums but, there's no "right" value, because it depends on the other running programs. Usually, the best value is using no value at all, which is the default, which means that Windows will handle itself the task of assigning different processor cores to different task.
- You have other 3rd party products that send a lot of commands in a very short amount of time using Simconnect, clobbering the communication channel with the sim, so we don't have enough time to send our own commands in time, which get queued, so when we finally get the chance to talk with the sim, the queued commands might cause the sim to pause by not being able to process everything in time. Weather engines are known to cause this issue, but not all of them, some are less resource-hungry than others.
