Confirmed - mine are gone too after reinstall.
Sort of unrelated, but I just re-installed the latest nvidia game-ready using DDU. Will deleting GLCache and DXCache files actually make a difference in performance?
They are already deleted when you reinstalled the driver, you donât need to do anything.
Weird.
I do not have that issue, and Iâve not altered any permissions, either.
Not sure what to suggest.
Backup your user.cfg.
Ages ago - even before MSFS 2024 - I used to recommend this exact thing in such cases: just zip the folder first, then move the zipped file wherever you want. That way, you avoid messing with permissions.
It was very widely reported and very common. See this long thread that ran from November through January (among many others):
Last night prior to uninstalling and reinstalling the sim, I tried to drag and drop my Community folder and received the âYour organization ⊠blah blah blahâ nonsense.
Anyway, after reinstalling the sim for the .23 beta build, I tried to manually set a custom Community folder location to avoid this in the future and then ran into the separate infinite moving packages bug. I had resort to manually editing the UserOpt.cfg file, something I always advise people to avoid monkeying with unless absolutely necessary.
Yeah, we know that. He was replying to the moderator who suggested settings would be saved in the cloud - which just isnât the case. Not with the SU3 beta.
Yea I did and checked bindings.. Idk.. button wonât return view to cockpit. Not that big of deal.
Thanks for pointing me there, but I do not think that this is documented sufficiently well here:
It would be in everybodyâs interest to improve the UX instead of repeatedly suggesting to clean folders manually, even for testers. Until then, the suggested steps could be easily automated and a tool provided with MSFS. Less support required, yay.
Bonus points if time could be saved by only partially cleaning files: Looking at my MSFS 2024 folder, itâs 625 GB and would probably take half a day to download again (mostly limited by server speed).
Pointing to random pages with specifications is not helpful. Itâs like pointing to Asoboâs recommended spec of GPUs with 8 GB VRAM.
Iâve had no issues with settings saving in the cloud on any of the SU3 beta builds, so issues beyond that seem to be anomalies which can occur in/out of the beta program.
I have had instances of graphics settings being reset (as they did after yesterdayâs uninstall/reinstall cycle) as well as occasionally some Assistance options being reset (which did not occur yesterday). Fortunately, none of my custom controller profiles have been wiped since the very early days of the sim, though occasionally they do seem to reset to defaults and I have to manually select the ones I want again before flying. But the profiles themselves were not changed.
Bug âŠ
You mentioned the WpSystem folder and symbolic links too - which suggests you had (and probably still have) the MSFS launcher installed in a non-default location. Thatâs most likely why youâre facing permission issues.
This is the smoothest beta build ive seen for SU3 so far, Took off out of SFO in the PMDG 777 and was smooth as could be.
I donât know what youâre trying to prove here - MSFS 2024 is (and has been) installed on my E: drive in a folder called âXBox Gamesâ, as suggested by the XBox App on my PC, along with a rotating case of other GamePass or MS Store titles I play from time to time. The sim launcher/installer gets installed and on first run sets up locations for the various packages folders, including Community. The early bug I linked to showed you the problem of being unable to set a custom location for the Community folder was long-standing so I gave up and left things as MSFS 2024 wanted to set them up. And clearly, despite leaving things as default, I ran into permission problems for some items, directly contradicting your claims above.
It would really help these forums if people stopped posting authoritatively in absolutist terms.
Finally, I bought 2024 for my VR rig (9800x3d oc and 4090). The sim looks very promising but it still lacks of the right performance. Although I use quadviews and DFR with my pimax crystal super the performance is quite poor (even at a 0,85% rendering). Without those âtricksâ it would be unflyable.
I hope Asobo and Microsoft improve the performance a lot. At the moment, I think it is a nice beta.
Edit: using beta 3
Today, trying to fly a mission I was sent to the desktop. Ups!
Infinite loading when attempting to move packages is still a bug unfortunately. I too have had to manually edit the UserOpt.cfg file and then itâs fine.
I also had my graphics settings reset to Ultra but all other settings were fine too.
This is not actually correct⊠Some of your settings are kept in the cloudâfortunately control bindings are in the cloud. But, graphics settings are not maintained. Library settings â like disabled packages are not maintained. And, configuration settings for 3rd party aircraft like Ini/PMDG/FSS not maintained.
Best to backup the aircraft WASM work folders, exe.xml, and content.xml or you may be doing a bunch of reconfiguring.
Iâm not trying to prove anything.
The default installation folder for the MSFS launcher is XboxGames
on the C: drive, not E:, D:, or any other location.
As we can see in the screenshot above the default installation folder is XboxGames
on the C: drive.
You have to click and change the folder manually - the Xbox app by default suggests installing to C:\XboxGames
If you manually choose a different location, like on drive E: or D:, thatâs a conscious decision and thatâs exactly why Iâm pointing it out again.
Changing the folder like this can lead to permission issues with certain files and folders, depending on how the system handles access rights for that location.
You had a different experience than I.
My graphic settings were kept, my library settings were kept, but obviously no third party items were.