I'm not sure that's the best permanent fix, because I feel like the sim has gotten a little laggy since I did that. Maybe it's something else, I dunno,
Compatibility mode on the Couatl program, which is a separate .EXE, cannot affect the simulator itself, because they run on completely separate threads so, even if for some reason our code would run slower, it won't have any effect on how the sim performs.
As an example, if GSX needs to calculate some pathfinding, to have a remote vehicle like Catering or Deicing coming to your airplane, if that calculation normally takes (this is just a made-up figure) 100msec (1/10th of a second) to make and, for some reason, the code became twice as slow, requiring 200msec, the only effect on the sim, would be the vehicle will appear and arrive 100msec later than normal, which of course nobody would be able to notice.
This is because the code itself is not running on the same process, so it's automatically running on a different thread, which in most cases means an unused core of a multi-core cpu the OS will assign it to, that without any special coding on our side. Even if we purposely slowed down our code, for example adding intentional pauses, even several seconds long, between each task, you won't see any effect on the sim, just our things will proceed with pauses in between.
In brief, we are UNABLE to "slow down the sim" with code. The only way we could slow down the sim is by populating it with too many objects at the same time and/or spamming it with so much Simconnect traffic, unti it breaks, which is something we are always careful not to.
In case, yes, the Windows 8 Compatibility mode is not a permanent fix, which I don't trust, both because there's no reason why it should work better but, most importantly, it's not very clear what it does, and in many cases, enabling it caused crashes in worse places than during a flight (where you don't even need GSX to begin with).
We are testing a completely different solution, quite like what Fenix does, of using a small and extremely simple "bootstrapper", which doesn't do anything other than starting the Couatl engine itself (instead of relying on MSFS), and it would just monitor it, and auto-restart it in case it crashes, all automatically. And will exit as soon MSFS quits, so it won't be resident in Windows.
