See this post here, starting from JFK2, in the most autogen-heavy area of the world, with the most autogen-unfriendly airplane possible, under the worse possible situation for blurries (flying at high speed)
No blurries, and no autogen loss.
http://www.fsdreamteam.com/forum/index.php/topic,18432.msg128490.html#msg128490About CPU utilization, I just made another test here:
Showing first with the Addon Manager enabled and lots of replaced SODE jetways in view, CPU utilization averages around 27% and GPU around 63%. Then, I disabled the Addon Manager, which disables *all* our software at once, and restored the default jetways.
Yes, they are a *bit* better in fps, so much uglier to look at, and the CPU and GPU utilization are
exactly the same as with GSX enabled! I couldn't be more proud of this result: being able to replace 12-years old jetways with much better looking model, without affecting the CPU/GPU consumption AT ALL, and with only a minimal impact on fps, it's really good.
Now, having proved the problem is not caused by GSX, by it's clearly related to system settings, it's likely that something that affect CPU utilization might have something to do with having played with the AffinityMask setting.
Have you changed this value ? I'm using default, which means no AffinityMask at all in the Prepar3D.cfg file, which is the setting that make more sense to me. I tried with other values, reading users report of "miracle" changes, but the only thing I could achieve, was a huge slowdown in loading textures so, I went back to default immediately.
And, of course, the usual common sense antivirus settings:
- Exclude the Addon Manager folder from the antivirus.
- Exclude the whole Prepar3D folder from the antivurs.
