Not only do you not have to clear your rolling cache, increasing it to 64GB or 128GB is completely unnecessary. Seb covered the rolling cache during one of the dev streams, and explained why it’s not needed to have huge rolling caches, and why it can even be detrimental.
1 Like
Not sure I agree with that… Check out:
His original writings from 2020 suggest mostly the same.. He is certainly not Asobo but seems to have a pretty methodological approach.
With this post, I’m sure the moderators may rightly chime in that we are off topic.. 
2 Likes
Inibuilds A350. Battery Errors and Engines don’t start cold and dark start up. Both work fine from end of runway starts. Possibly an Ini issue more than Sim. Thought I’d post it though.
You need to go into the EFB and replace the batteries and service the engines (no oil). Not sure if it does it every time or not
1 Like
MS/Asobo have recommended this as an official troubleshooting step whenever issues arise, and also have recommended it and/or full reinstallations (which would include a refreshed rolling cache) after major updates.
Yep, you can - go into the game management menu from your home screen and delete “Reserved Space.” That will clear your rolling cache, streamed packages, and a few other things that can cause issues. This does not wipe your cloud save file or affect the sim in any other way other than causing a bit longer initial load as it’s basically a soft-reinstall.
But doing so will also delete any camera pre-sets you might have which is annoying so I don’t do this
3 Likes
Wasn’t that in one of the earlier streams and at a later stream they said they would recommend/or used (themselfes) around 64gb+?
1 Like
Thank you i will look into it. I played around with process lasso last night and i could get every core to work but tbh the result was the same as with only using one ccd in overall cpu usage (between 40 and 55 ish %)
Can’t you go in to MSFS Settings and set the Rolling Cache to Zero (which deletes it)? Then set it back to the amount you want. That used to work on Xbox in MSFS 2020
That’s effectively what they’ve already recommended doing (just a different low value, not 0) - though MSFS 2020 had a distinct “delete rolling cache” button (or maybe “reset” but either way).
1 Like
Yep, SU4 currently stops Just Flight, A2A and PMDG modules working.
I have a similar or even worse experience so far.
I opted out of SU4beta for this build. While it is generally similiar in performance to SU3 for me, it introduces a lot of nasty bugs and regressions. Quite a few of those with 3rd party add-ons which I use exclusively.
Just to name a few most annoying ones for me:
- Camera switching reloads textured every time
- General loading of textures is way slower
- Strange highlighting of options in all menu lists
- Some of my favorite 3rd party planes and airports are bugged
- no restart of flight possible
- ground textures are randomly broken on airports
- strange temporary hammering of main thread which leads to a stutterfest when airborne
Will be back for the next build.
4 Likes
For those affected, REX just announced they will be releasing a Beta of CORE for SU4 “in the next few weeks”.
1 Like
I use an RX7600 8GB with a 5600G processor, and the main thread improvement was significant in my case.
I was already running the simulator in TAA at 2560x1440p with most settings set to high (except for texture resolution, which I’m forced to set to medium due to VRAM limitations).
But before SU4, I reduced the resolution via resolution scaling to 95% because my processor was starting to feel limited in third-party scenarios and photogrammetry at the same time.
My processor now works more smoothly, and thanks to the VRAM improvements, I can achieve 100% scaling at 2560x1440p when flying online in IVAO in demanding scenarios. That’s what I was able to achieve in FS2020. Asobo is on the right track. With each SU, I saw gradual improvement.
I remember that before SU2 when Asobo started working the VRAM, I was forced to use the simulator at 1080p and low resolution to avoid VRAM overflow. I even went months without flying because on final approach, the VRAM would always be exceeded and it would turn into a slideshow.
I have a lot of criticism for Asobo regarding how they handle the simulator’s problems, but I have to praise how efficient they’ve been with optimization so far.
1 Like
All my temps are okay. It only fixes if I restart my PC for a few flights then starts doing this again. Cache is fine since ive just reinstalled the sim yesterday. Reinstalling a driver will temporarily fix it until i start decending
On my AMD system 5800X3D 7900XTX the beta also performs much better. Much more reliable 100% GPU usage, much less stutters (not perfect yet though)
4 Likes
This would not affect planes who are not using the new inertia tensor parameter in the flight model. Since it did not exist before SU4 beta, only the two aircraft listed in the release notes are using the parameter.
1 Like
I am one of the fortunate ones that have generally and consistently had very good experiences with both 2020 and 2024. This beta has proven to be a bit of an exception and I must admit to being puzzled.
With this beta I have been experiencing awful AP swings around the GS and LOC (i.e. both laterally and vertically) on ILS approaches, as described here. This after approaches have always been pretty much perfect before and returned to being perfect when I went back to SU3. The lack of comments on this topic makes me wonder if there is just a small handful of us experiencing this or if the release of the beta is still sufficiently recent that just hasn’t been widely noticed. For information, this screenshot of the flight path in LNM is what I have been seeing:
Hoping for some feedback on this.
1 Like
This was a confirmed sim-side bug with ILS L-Vars and has been reported to Asobo.
This info from the Working Title Discord.
2 Likes