One thing I'm curious about is which logical processors are getting maxxed out when these blurries present themselves.
A user on AVSIM presented a situation where if you load an FSDT scenery, then move to another FSDT scenery, then do it once again, the sim hangs during loading and the CPU load goes sky high for as much as 10 minutes during the loading of the third or subsequent FSDT scenery. It's consistently reproducible--I start with the PMDG 737 at KLAS gate A12, then move to KMEM gate B12, then move to KJFK gate 803. What I saw when I reproduced that sequence was relatively normal load times for the first two, then at KJFK, a stall at about 36% during the terrain loading phase and 100% load on all of the logical CPUs that handle terrain and texture loading (in my case logical CPUs 4-7 on an HT-enabled quad-core i7). Changing the order of the airports didn't seem to make a difference, either. This, BTW, is with GSX v1 without ever having upgraded to v2. Killing the couatl, UTLive, and SimobjectDisplayEngine processes had no effect once the hang occured. RAM usage was normal (~7.4GB) and VRAM usage was also not problematic (~3.8GB on a pair of 11GB 1080Ti GPUs).
I'm not certain if it's relevant to the blurry issue, but the apparent similarities between the two--the presence of a large, long-duration and unexplained load on the logical CPUs that handle terrain and texture loading is suspicious. It may be demonstrative that GSX and/or FSDT sceneries are coming up against some kind of internal limitation not previously encountered in P3Dv4.
Regards
Bob Scott