You probably remember when I explained this on the forum - many users (you and myself included ) were pointing to the wrong folder. They selected the Community folder directly, instead of the parent folder that contains Community. Thatâs a user mistake, sure - but honestly, Asobo shouldâve anticipated this behavior.
Right after installation, itâs completely reasonable for users to try to move their packages and the sim should clearly warn when the selected folder is incorrect. A simple message saying âYouâve selected the wrong folderâ would save a lot of frustration.
Btw - for well over a year now Iâve been changing the default C: drive to another drive in the Xbox app and never had an issue. I donât ever mess with any sim folders or files other than using MS Addons Linker with the community folder. I use this method only because itâs a Microsoft approved way of changing the install location. Iâve done close to a hundred installs this way between my 2 sim PCâs as I always do a deinstall/reinstall of the sim on every update.
So after skipping a few beta versions I completely reinstalled the latest one yesterday. I must say that performance is way way better than before, almost no stutters, however some still occur every now and then. Not as severe as before but still noticable. I wonder if that will get better once SU3 is officially released and every addon is officially supported
Short hop in the Fenix tonight, no bad, still some FPS drops during landing (at Pyreegueâs new EGBB). Not too bad though. Will need to try a denser airport. Using BATC+AI injection.
Still some audio skips/glitches especially when switching to external camera. Overall though not bad.
You manually chose that folder on your E: drive - the Xbox app didnât automatically pick it for you. You set it as âthe defaultâ, not the Xbox app itself.
At this point, I think continuing this discussion is pointless, so Iâll leave it here.
That was when only the Community folder was being moved. And I learned a long time ago not to type community in the path. Now we have the option to move the packages folder which does include the community folder.
Since then I have always selected D:\MSFS 2024 for my install location when moving packages. We went through that too and agreed the infinite loading time is a bug. And figured out the workaround was to put the correct path at the bottom of the UserCfg.opt file.
Did you customize your library by disabling items? Did you customize the graphics settings or just use presets? That stuff is not stored in the cloud.
The 3rd party options for aircraft are not stored in the community folder â they are in the Limitless folder structure. So when that gets removed a bunch of 3rd party stuff does as well.
Iâve reinstalled a couple of times since the initial release of 2024 and wasted a bunch of time before learning to back up certain files and take screen shots of some settings. Just think folks should be careful before reinstalling or they could have some unwanted surprises.
Yes, I remember that I wrote somewhere on the forum that editing the UserCfg.opt file is a workaround for the folder-moving loop bug in MSFS 2024. I think I or someone else also mentioned that besides editing the line, one of the lines needs to be deleted as well.
Right. It was you who suggested removing the line that included âon next rebootâ or something like that. Once I removed that line the infinite loading stopped, and the path was displayed correctly in the sim.
Itâs still a bug and I have to edit the UserCfg.opt file every time I do a complete reinstall.
I donât have that bug anymore, but after reinstalling MSFS 2024 SU3 beta, my graphic settings werenât downloaded from the cloud. Itâs not a big deal, just another bug.
The sim runs great. Had good FPS since yesterday, no fps dips anymore. Now iâm starting the sim. In the menu I have 60 FPS my monitor refreshrate. When I load a flight, it drops to 30⊠I have no cap or something active.
I did the uninstall/reinstall thing, and all my graphics settings got reset. Not a huge issue, but I did have to tweak mine to half monitor refresh, capped at 60fps, as I did before the upgrade.
I tried EGPF, and it took about 20 seconds to go from the main menu after clicking fly to spawning on runway 23. But the textures were already at their highest resolution when I got there.
Did clean instal, cleaned everything, newest nvidia driver. In general performs better than previous SU3 build, but after long flight with airliner performance degradation and stutters when fast panning camera still present. Maybye memory leak or so? But i have decent setup 13900kf/4090/64GB DDR5 so memory leak need to be huge. Only developers know, or donât know whatâs the case. In general this build is step forward.
Assuming these were both stored locally and not in cache, my equivalent load time was around 2 minutes for EGPF and 1 minute for EGBB. I am really confused why there is a difference for non streamed assets unless these airports are using in sim satellite data and runway textures. I mean I have slow broadband but for locally stored airports itâs a bit of a head scratcher for me. They work fine when loaded into data cache though.
first run of .23 loaded to the runway and CTD. Second start was ok.
Overall performance is good, landing at bigger handcrafted airport VHHH was âdo-ableâ, looking to the tower still halves the fps on my system in VR. If this bug is fixed i like the sim!
Did clean instal, cleaned everything, newest nvidia driver.
In general performs better than previous SU3 build, but after long flight with airliner performance degradation and stutters when fast panning camera still present.
Maybye memory leak or so? But i have decent setup 13900kf/4090/64GB DDR5 so memory leak need to be huge. Only developers know, or donât know whatâs the case. In general this build is step forward.
) were pointing to the wrong folder. They selected the Community folder directly, instead of the parent folder that contains Community. Thatâs a user mistake, sure - but honestly, Asobo shouldâve anticipated this behavior.
Once I removed that line the infinite loading stopped, and the path was displayed correctly in the sim.
