Good grief....read this thread, tried to backup my MSFS Community folder - system somehow decided to begin "updating" MSFS 2024 without even launching via the XBOX app and POOF! my Community folder disappeared mid-way through backing up.

Perhaps a sign that the "all default" life is the best MSFS life for me (though I will re-install that wonderful F28 by Just Flight right away!)

Sigh......this is why I love XP12 (though I'm also trying to keep that mostly default).

 

I participated to the beta via the Xbox insider hub, after the official release I didn't do anything about to leave the beta. At this moment it's resulting that I'm not in beta anymore on the Xbox insider hub. My question is: it's better at the moment not to start FS24 ?

12 minutes ago, Republic DC9 said:

 

Sigh......this is why I love XP12 (though I'm also trying to keep that mostly default).

 

Makes 2 of us !!! XP12 Rulezzzzz !!! at least management wise.... It's so simple to maintain, backup, update, and even "betate"...

Dodged a bullet, luckily i also visited here looking for details of SU2, to see the warnings. Quickly left the Beta for SU1, and moved the Community folder to another drive. 

37 minutes ago, Republic DC9 said:

and POOF! my Community folder disappeared mid-way through backing up.

I don't really understand all the complaints when Microsoft has said over and over, 3 years ago. sorry to say this but that POOF! comes from not following the beta checklist:

"There is always a risk that you may have to re-install the sim when joining/leaving a flight, so please keep this in mind before participating. If you have MSFS content installed completely on a custom path, you will have a much lower chance that a full re-install will be necessary when the update is officially released. However, if your sim content is installed in the default path selected by the in-game content manager, you may have to reinstall the whole sim when moving from the test build to the public build. We recommend that those who wish to test with us ensure your sim content is located in a custom path before joining the flight to avoid full reinstallations in the future (Details on how to do this can be found here). The best set up would be for your store app to live on the default drive and sim content on a custom drive.

Please remember if you decide to join the Beta and install the build, you will likely have to re-install your sim if you wish to leave the Beta before it ends."

https://forums.flightsimulator.com/t/beta-testers-new-information-on-joining-leaving-the-beta/543728

 

to avoid full reinstallations in the future (Details on how to do this can be found here:

https://forums.flightsimulator.com/t/how-to-change-the-installation-path-of-installed-packages-inc-community-folder/471682

Edited March 22, 20251 yr by turbomax

Cool glad I went with steam, because I didn’t have to reinstall anything was as easy as unchecking beta and it was done.  The less control you give to Asobo and Microsoft the better. 

So I am still enrolled in the beta but understand this update is not the SU2 beta (yet)?

also, with both 2024 and Community folder in dedicated non-default locations, I understand that this update should do no harm (though I always check the installs/update folder when being ask, just to be safe)?

after all, when not SU2 beta what is this 8gb all about? Bit big for just an AIRAC update, isn’t it?

6 minutes ago, turbomax said:

I don't really understand all the complaints when Microsoft has said over and over, 3 years ago. sorry to say this but that POOF! comes from not following the beta checklist:

"There is always a risk that you may have to re-install the sim when joining/leaving a flight, so please keep this in mind before participating. If you have MSFS content installed completely on a custom path, you will have a much lower chance that a full re-install will be necessary when the update is officially released. However, if your sim content is installed in the default path selected by the in-game content manager, you may have to reinstall the whole sim when moving from the test build to the public build. We recommend that those who wish to test with us ensure your sim content is located in a custom path before joining the flight to avoid full reinstallations in the future (Details on how to do this can be found here). The best set up would be for your store app to live on the default drive and sim content on a custom drive.

Please remember if you decide to join the Beta and install the build, you will likely have to re-install your sim if you wish to leave the Beta before it ends."

https://forums.flightsimulator.com/t/beta-testers-new-information-on-joining-leaving-the-beta/543728

 

to avoid full reinstallations in the future (Details on how to do this can be found here:

https://forums.flightsimulator.com/t/how-to-change-the-installation-path-of-installed-packages-inc-community-folder/471682

I think you're missing that the problem you are talking about is about the ufficial final version release after the Beta, now it's a different business: a fantomatic mandatory update is destroying our FS24 installations, and this is a real problem, not directly linked if a user has left the previous Beta or not, because now we are all in the same final ufficial version of FS24. Am I wrong?

14 minutes ago, turbomax said:

I don't really understand all the complaints when Microsoft has said over and over, 3 years ago. sorry to say this but that POOF! comes from not following the beta checklist:

"There is always a risk that you may have to re-install the sim when joining/leaving a flight, so please keep this in mind before participating. If you have MSFS content installed completely on a custom path, you will have a much lower chance that a full re-install will be necessary when the update is officially released. However, if your sim content is installed in the default path selected by the in-game content manager, you may have to reinstall the whole sim when moving from the test build to the public build.

Let me rephrase that: "We are so incompetent that there is a chance - meaning that we are not entirely sure of that... we cannot reproduce it but it can happen... we say it in that way simply because we have no idea what's the cause after 4 years of programming and tweaking this 5h175h0w - I was saying, we are so incompetent that there is a chance that if you leave the installation path that WE choose by default, your entire installation go bust because of an update.

And guess what... again it's YOUR fault for not having changed the default installation path that WE selected.

LMAO

P.S. And also... if you use a custom path, there is "a much lower chance" of this happening. They are not entirely sure of that either, they are clueless.

Edited March 22, 20251 yr by MrFuzzy

3 hours ago, MarcG said:

Another day another monumental mess from this lot, I rue the day I chose the cheaper MS Store version 🙄 that's on me, the rest of it is yet again pure amateurism on MS/Asobos part.

It's amazing. The amateurism and frankly the complacent contempt they hold their customers, users and commercial partners in.

After punting out a not so obvious announcement on the official forum twelve hours ago "oops, we've made another balls-up" they go radio silent again.

Bring on Elon for some backside kicking...

Can anyone get back in the sim after this?  Basically, it ended up doing a complete re-install and now I can't load into an airport.

54 minutes ago, turbomax said:

I don't really understand all the complaints when Microsoft has said over and over, 3 years ago. sorry to say this but that POOF! comes from not following the beta checklist:

"There is always a risk that you may have to re-install the sim when joining/leaving a flight, so please keep this in mind before participating. If you have MSFS content installed completely on a custom path, you will have a much lower chance that a full re-install will be necessary when the update is officially released. However, if your sim content is installed in the default path selected by the in-game content manager, you may have to reinstall the whole sim when moving from the test build to the public build. We recommend that those who wish to test with us ensure your sim content is located in a custom path before joining the flight to avoid full reinstallations in the future (Details on how to do this can be found here). The best set up would be for your store app to live on the default drive and sim content on a custom drive.

Please remember if you decide to join the Beta and install the build, you will likely have to re-install your sim if you wish to leave the Beta before it ends."

https://forums.flightsimulator.com/t/beta-testers-new-information-on-joining-leaving-the-beta/543728

 

to avoid full reinstallations in the future (Details on how to do this can be found here:

https://forums.flightsimulator.com/t/how-to-change-the-installation-path-of-installed-packages-inc-community-folder/471682

Good advice, Turbomax....I shall follow it in the future.

In any case, whatever they did in terms of changes to this beta, it runs absolutely smooth as silk on my PC - hard to quantify, but far fewer stutters, smoother panning, etc. after several flights in heavy (Seattle and LA) areas.

47 minutes ago, MrFuzzy said:

if you use a custom path, there is "a much lower chance" of this happening. They are not entirely sure of that either, they are clueless.

that's the nature of beta.

1 hour ago, Simselli said:

and moved the Community folder to another drive. 

renaming would also suffice should you run out of HD space. as long as your COMMUNITY is not in the MSFS default location. the install program creates a clean slate environment including an empty COMMUNITY to avoid any ambiguity in users configurations, of which there exist already more than enough. a non-empty COMMUNITY has stopped the sim from even starting due to incompatible addons, happened more than once. there are obviously good reasons for this clean slate MSFS design strategy to minimise conflicts before the game has even finished loading. 🤣

 

2 minutes ago, turbomax said:

renaming would also suffice should you run out of HD space. as long as your COMMUNITY is not in the MSFS default location. the install program creates a clean slate environment including an empty COMMUNITY to avoid any ambiguity in users configurations, of which there exist already more than enough. a non-empty COMMUNITY has stopped the sim from even starting due to incompatible addons, happened more than once. there are obviously good reasons for this clean slate MSFS design strategy to minimise conflicts before the game has even finished loading. 🤣

Yeah I am still enrolled in beta so I plan to start up my PC and rename my community folder straight away and copy my usercfg before the update runs. Then just rename it back afterwards