I’ve set my rolling cache to 100GB just to see if it would improve performance (which it didn’t) but now I want to change it back to a smaller size but that’s not possible (see attachment). Cache can only set bigger and never smaller? Please fix this
Can you delete your current rolling cache …maybe that’s the answer?
how do you do that? There is no option and I cannot put the value 0 in as it gives the same message
No idea …maybe somebody knows where the folder is located and can assist!
this is on xbox so no acces to folders that’s why I created the issue here
Ah, ok …sorry …not able to help then!
Go to xbox home and msfs2024 options (not ingame options). There you can delete reserved space. It resets cache to default value.
well i followed your suggestion to delete reserved space and indeed my rolling cache is now back to 16GB. Unfortunately, all my saved camera views are now gone. I had setup views in different planes and now all of them are not working anymore.. ![]()
Hi @Trinity8968 ,
Thank you for this report. We’ve moved your topic into the User Support Hub.
The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.
If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.
If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.
All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.
See related topic: No ability to reduce rolling cache size
I did comment on the same question in a different topic. I hope this is useful for you.
Just delete the ROLLINGCACHE.ccc file, this causes no harm and it resets back to 16GB. You just need to wait a little longer on the first loading screen again for the initial download.
Guys, this is for xbox so please don’t give answer for pc. Also why is this topic moved to a pc topic?
I had exactly the same problem and on Xbox as well. Here is how I set the cache back to 16 without losing all my other data like control bindings and carrer progress:
Exit the game back to Xbox menu.
With the game highlighted press the hamburger button.
Select Quit to stop the game completely.
Press hamburger button again and select Manage game and add-ons.
I see 3 boxes, one for the game (about 32GB), one for updates (0MB) and finally one for saved data (about 130GB in my case with a very large cache).
Select Saved Data.
Now I see 2 boxes under DELETE ALL, do Not click delete all unless you want to lose all your saved settings! Instead select the large one called Reserved space (approximately the size of your current cache).
Then select CLEAR RESERVED SPACE.
In my case that seemed to only delete the cache without impacting anything else ![]()
Restart the game and confirm your default cache is now back to 16GB but nothing else was harmed.
I think I recall that MSFS 2020 had a delete cache option right in the game where you would expect it. Why they made it more obtuse is another mystery of 2024.
Good luck!
I think it’s some king of bug. Once again who would suppose
Seriously speaking I did it this way and all my settings were unaffected.
I put mines to 16GB and it worked fine. Just ok the message and type in 16.0 again
Upps … you are right @Trinity8968 … and I am sorry that I missed that important aspect.
On Xbox the problem of a missing simple “official” UI button to get that work done is a way more pressing problem.
I think in the Xbox context I would kindly ask the moderators to classify this issue as a real “bug” … and not a trivial “user support” issue.
