Yeah I suspect the same although I mostly notice the area specific kind since my target fps is low anyway (20). I got through 3 areas again last night with periods of bad stuttering/low fps. In my case 5 fps or lower until it recovers again. Those can last over 10 minutes.
It does seem Asobo did something with memory management as memory doesn’t seem to run away aymore is it previously did when performance degraded. I’ve not seen situations anymore where allocated (commit) memory went over 30 GB, it generally stays below 20 GB with my settings. But that can also be because I have halved my draw distance (200->100) to not go down to 1 fps while terrain fails to draw in. (Did not have that issue at 200 before SU3)
Anyway now with only 65 ‘items’ installed, did not notice any improvement overall. It’s playable in the sense I can land at 5fps and it doesn’t CTD, enjoyable not really. Plus the trees now stop really close with terrain detail at 100.
I hope there will be a fix soon. I also noticed that the live time falls behind when this bad stuttering crops up. After 6 hours of flying with a couple bad areas in between I noticed that the live time was now almost half an hour behind the actual time.
I found an old FPS test (Februari 13th) I did before SU3 testing the impact of glass cockpit refresh rate on my system
High/medium/low
Shock Ultra 41 fps / 42 fps / 42 fps
Bonanza G36 33 fps / 34 fps / 35fps
Boeing 747-8i 19 fps / 24 fps / 26 fps
Dreamliner 15 fps / 21 fps / 24 fps
Today, same spot, same clear skies and other settings
Shock Ultra 22 fps / 22 fps / 22 fps
Bonanza G36 19 fps / 19 fps / 19 fps
I don’t have the airliners installed anymore since they are unplayable now. It also looks less stable now, fps frequently dips down while I’m not moving at all.
Depressing to see how much worse it got, from 42 fps down to 22 fps.
Turning v-sync off, trees to high, and terrain down to 100 the shock ultra gets 25 to 27 fps now. Still a huge drop compared to terrain 200, trees ultra, v-sync, before SU3.