Good Job Asobo

The latest update has corrected a bad stuttering problem that I would consistently experience. I would get bad stuttering between FUELR and BASET intersections east of Los Angeles. The simulator would literally stop for one to two seconds. CPU load would show 99% for one core and the other 23 cores would show 0%, GPU load would show 0%, and FPS would drop to 0. I flew test flights through this area dozens and dozens of times trying to determine the cause and it always stuttered severely. I was able to make it stutter less by reducing Terrain and Object LOD, and Terrain Vector Data settings - but there would still be stuttering. The higher Terrain and Object LOD, and Terrain Vector Data settings I was using worked well everywhere else I flew, just not in this area. With the latest update this has been corrected. I have turned Terrain and Object LOD up to 200, and Terrain Vector Data back to Ultra. Four test flights through the area and no stutters - a smooth 35 to 40 FPS. Good job and thanks.

I have noticed one strange issue. The frame rate is sometimes low - I only see 25 to 30 FPS - but I do not see a reason for it. The max load I see on the CPU is 80% on any one core, and the GPU load is only 75% to 80%.

Photogrammetry loading used to cause a lot of pauses and stutters for me as well. LA was probably the worst offender there, turning my experience into a stuttering slideshow at times. Last night around LA I was experiencing slightly lower than usual fps, likely due to the increased detail of that area after the patch, but the overall experience was a lot smoother. The PG optimization in this patch helped a lot. It could be better, but at least it wasn’t a regression like we’ve seen in prior patches.

I agree that overall performance is smoother - almost stutter free for me. But, I do not think that the problem I experienced was due to photogrammetry. I came to believe that it was bad terrain data in that area.