Please stop saying there's a bug in GSX, in Couatl, or something like that.
TWO users already reported the problem was fixed for them by refreshing the shader cache and the scenery indexes.
We don't modify any of them so, clearly, they were already messed up with something else, and installing GSX might just have made the problem (which they already had), just more obvious, but it wasn't the cause.
If GSX was the cause (it's not), it couldn't explain that:
1) I cannot replicate any blurries and any higher than normal CPU utilization, as seen in the various videos I posted, including one from another user on Avsim, arriving at destination after a 2 hour flight with no blurries at all.
AND
2) Some users reported the blurries were gone by refreshing the shader cache and the scenery indexes. If GSX were the cause, this wouldn't be possible.
The *simulator*, of course, will generate such files automatically, when new kind of objects are used for the first time, and when a new scenery is installed. The only scenery we install with GSX 2, is the empty Exclude folder, THAT'S why I suggested trying to use a different add-on.xml, but I don't really think this is the problem.
The simulator might have also added new shaders, when it found materials added by our newly installed Jetways. That's nothing we have any control over it, it's all done automatically but, sometimes the shader cache folder might end up corrupted, so it needs refreshing.
AND, if you have 3rd party shader utilities, like PTA or Tomato Shader, this will result in DIFFERENT shaders being created, because they modified the original shaders. The shaders in the ProgramData folder are binary representation of the source files under the Prepar3d\ShaderHLSL folder, and there might be MANY of them, since for each source, the simulator can create different variations depending how it's used in the various objects found in the sim.
I have 1703 shaders in my shader cache, but every use will have a different number, because it depends how many object you have seen in the simulator. Yes, when creating shaders, it's understandable the CPU utilization might be higher, and the scenery might look bad.
Maybe your shaders folder has grown up too large ? Maybe your hard drive is a bit slow in writing for some reason ? Maybe your ANTIVIRUS is slowing down reading/writing the shader cache ?
We had users reporting the GSX airport cache regeneration took "minutes" on their system, while it shouldn't take more than 10-20 seconds for a full regeneration, and 1-2 for a refresh after installing a single scenery. This WAS caused by Windows Defender, that tried to scan every single .BGL, just in case it might contain a virus, and excluding all the simulator folder from scanning resulted in a 10x decrease in time for these users. And of course, while doing this, the CPU utilization gets higher.
Could be the same is happening to your shader cache ? The simulator is doing its usual work of creating new shaders (because there are new objects installed by GSX), but is taking much longer than normal because of the antivirus (or because your shader folder has become too large), so you see high CPU utilization and blurries, and put the blame on GSX, when there's clearly nothing wrong with it ?
