I wonder if your issue is related to a significantly larger number of flights than me.
The whole ceasing to record flights was tied to a limit on the log’s capacity, right?
Perhaps, you’ve hit the new capacity or there is an issue with what that capacity is even with the new compression mechanism?
I was wondering about this aspect. Maybe constantly in/out of decompression and hogging CPU while mousing over entries. Will see if it persists. But in SU13 where my logbook took 2+ minutes to decompress and display I didn’t have this problem. Maybe it’s their new workaround for faster viewing of the slow decompression of logfile that I’m running into. It’s quite useless/unusable like this though. Anyhow I don’t want to clog up this thread with this issue.
1 Like
My performance baseline is to fly my Bonanza G36 Improvement Project over the Sahara. I have quite a few addons loaded as well.
5800X3D, 3090 Ti/ 24GB, 64GB DDR4-3600/CL14, MSI B550
4K, DX11, HDR10, DLSS Performance, no rescaling.
TOD = 175, LOD = 130, ultra clouds, water waves high, trees, grass medium, other misc. settings medium/high.
Pre-SU14
90 FPS limited by Riva / 11.11ms latency.
GPU: 62°C / 310W / 60% Uitlization
Post-SU14
85 FPS / 12.25ms latency.
GPU: 65°C / 340W / 80% Uitlization
So it apperas that SU14 shifted some things over to the GPU in an effort to relieve CPU single-core task saturation.
That’s just a WAG, though, as the differences could be due to other things I’ve changed since I tested my baseline model.
Bottom line - SU14 doesn’t seem to have degraded my performance in a simple environment, flying a low-stress model.
One thing I have noticed is that my cockpit camera movement is much smoother.
1 Like
So, like in the conversation above somewhere mentioned, i had the hefty impact on photogrammetry.
Now ive made the exact same flight again, to test something for the 747, this time i turned PG off for the arrival at EDDK and this time is was perfectly fluid again.
So its indeed photogrammetry again, like some patches before. At least in my case, we all know, many ppl have many different things ^^
But the impact from the SU14 patch is for me for sure based on PG. (or PG in combination with airports. Tbh i havent tested with only PG but no EDDK.
Btw, im using Aerosoft EDDK and i have deleted the Asobo one in content manager. And anyway this also was happening either over Paris or over Brussels already, not 100% sure.)
Everyone testing this, please make sure you first delete rolling cache and recreate and maybe also scenery indexes dont hurt, here and there.
And also make sure that you dont have double airports now. Like EDDK for example. If yo have AS, delete Asobo (or opposite) etc.
2 Likes
There is a landing challenge with the King Air 350 in Quito.
Try that and you get a stutter when you make the turn in to final, regardless of settings, done it with low vs ultra settings , makes no difference. At some point the CPU gets bogged down, this did not happen with SU 13
1 Like
I need your help here. It would be really kind if others would test something on their end.
I have found out, that at my end, using Stock or Addon Planes, which rely on Asobo/MSFS Avionics displays (TBM, CIRRUS, 787-10) create significant stutters when you are in the insight view (Cockpit). When you are flying, and turning the knobs on any ND display, so the display is changing and gathering loading data (like ICAO, Weather, Terrain, WPT, etc.) the higher you turn the range, the more the “CoherentGTUIThread” is creating spikes and this is resulting in FPS spikes as well. My MSFS FPS counter in DEVMODE is showing yellow peaks and sometimes, when turning the ND range knob quickly to high ranges (like in 787-10 to 160NM, 320NM and 640NM) these spikes get RED, so the stutters get heavy. Also the FPS drains at that moment and recovers after this.
I would really appreciate it, when you would test this as well.
What I have done to eliminate this without any positive result is:
- Im on the latsest Release 1.35.21.0
- I have reinstalled the XBOX MSFS APP
- I have swapped the DLSS file as well, and reinstalled the origin also
- I have reduced TLOD and OLOD to even 10NM
- I have used TAA, DLAA, DLSS, FrameGen ON and OFF
- Have reduced so many settings to test and nothing helped
- Stock MSFS (so in Safemode) and even then the issue occurs
- 2D and VR it iss an issue, and in VR I get HMD Stutters when panning, BECAUSE of the yellow and red spikes
I think, and assume, that there is an issue with those WASM-Displays?, or CoherentGTUIThread renderer
I am on a AMD 7900X3D
RTX 4090
32GB RAM
NON OC
Emtpy Community Folder and Filled, no difference
Please reply if you have the same issues or even have no issue at all.
I would like to know, if you see spikes in the MSFS Dev FPS counter like me, regardless if your view is stuttering or not. The spikes weren´t there with the latest MSFS SU14 BETA. I head butter smooth experience there.
2 Likes
Not sure this is an answer to your question….I do have random CPU spikes that makes the screen “jump” or stutter about every 30 seconds.
Dev mode shows all green, and den all of a sudden 6 fps, CPU spike and then back to 87 fps. This happens regardless of settings. 87 fps on Ultra with DLSS on a 4070 OC.
Same thing happens on low, no DLSS, or just everything turned down to absolute minimum.
Started with SU14
1 Like
Thanks for your reply! Yes, these spikes drain fps significantly. IN my case from 75 in Cockpitview down to 38 and directly up again. So I´m having good FPS, around 70-80 in flight and between 15 and 30 seconds later drop again to 38-48FPS for just 2 seconds maximum, and then up again.
But that happens without turning the knobs in my avionics display. I´m asking myself, if the avionics do some “draw” calls…? Which spikes GTUIRenderThread and drops FPS for short seconds.
1 Like
I don’t know. Perhaps. Maybe only the coders know for sure.
I do wonder if it was rushed out (before fit for purpose) to meet a deadline though. Pure speculation on my part but I do wonder.
1 Like
So here is a fresh example, just random flying, yes I know I hit the concrete , just goofing around, low scenary area.
And all of a sudden…comes the spike…rinse and repeat every 30 or so seconds…the spike manifests as a sudden “freeze/stutter”…
2 Likes
Can you try the same with the new Cirrus or 787 stock (or something with complexer displays )? And then in the cockpit view and look at the CoherentGTUIThrear of this has small shorts spikes as well please?
Yep this is basically what I’m seeing on the CPU graph
So would it be possible that the biggest impact on MSFS is photogrammetry? I tend to believe so. I thought about it now and in fact the system’s work in downloading the data and being processed by the AI and traveling through the SIM I think, I don’t think so… it is very likely that the data flow on the servers is the limiting factor. Is this what causes so much stuttering? I have a modest 5800x3d equipment and a 4070ti with 32G DDR and whoever has their 7950x3d and a 4090 +64G DDR and still encounters occasional stutters, I imagine they feel uncomfortable with such an investment in hardware…
Hello
Just to make sure we are all on the same boat. Did you regenerate your rolling cache already?
And made sure you dont fly to airports you have bought + are in the sim.
I know, we shouldnt have to do this all the time but there is an update guide from Asobo somewhere and a few of tmportant. At least if someone has problems.
I mean the part with rename community folder before update, or regenerate rolling cache, delete scenery indexes etc etc.
Just so we sure we didnt run in the more or less typical issues that can happen after updates.
Here is a part of this, the point with DELETE DIRECTX SHADER CACHE could also be tried (also on Win10). The rest i wouldnt do blindly.
And the other steps are
- regenerate rolling cache
- close sim and rename community folder to XCommunity
- delete your scenery indexes (the files, not the folder)
- start Sim
- try in a PG city where you know you had issues
- close it
- delete the empty Community folder and rename the XCommunity back to Community
- Start sim and hope its better
Of course first you could also simply turn off PG and see if it improves dramatically.
2 Likes
Hmm, i think my EDDK got installed again… I know i had deleted it already, not sure how it ended in there again.
In this case i have to sadly say i have to retry this… because i had EDDK from Asobo and EDDK from AS installed at the same time. Maybe that caused the issues.
I will retry… this time with really only 1.
Sorry for posting many times.
I think for me at least its back to normal…i did the whole thing again (i had done it after update, nt sure why i needed to do it twice) and now it seems okish. It could be that its a little bit lower, not sure. But at least i dont see that 14 fps anymore, im back to 30 fps (locked) now in EDDK. With PG active.
- regenerate rolling cache
- close sim and rename community folder to XCommunity
- delete your scenery indexes (the files, not the folder)
- start Sim
- close it
- delete the empty Community folder and rename the XCommunity back to Community
Thats what i did again and for now it seems to work.
2 Likes
Thanks for sharing the link! I too began experiencing stutters on dedicated MSFS i9-13900K w/64GB DDR5, 4090, & Samsung 990Pro NVME drives system. I wasn’t optimistic, but the “fix” outlined in the linked article worked for me!
I am in complete agreement that this step by step helped to improve my performance. Just the simple fact of having cleaned the Scenery Index folder freed me from some crashes. I think there was a lot of dirt there from the various scenes that we installed and uninstalled and the task you described helped to clean it up. Now I have MSFS back as it was. Clean, Fast and Fluid. Apparently we will have to do this whenever a new update occurs. Thank soo much!
1 Like
Yes, i think rolling cache and those things are more important than the cache thing from the link. It shouldnt hurt to do that here and there but personally i ony do that if nothing else helps.
The cache etc have already caused me much more issues in past, i would start with that. THere is s link too to the zendesk, where those steps are detailed. But cant find it atm.
Ill do when i found it.
No problem, glad it worked for you.