Mine were too.
Also, my 16 GB Rolling Cache was changed to 8 GB.
I thought that I had my UserCfg.opt file set ■■■ “Read Only”.
But, it is changed to Not Read Only.
I had to change them back.
Ultra then, UserCfg.opt to:
Preset = Custom
Terrain LoD = 4
Object LoD = 9
Set file to Read Only.
Did you have a custom install path or the default folder.
Everything was default. Nothing changed or altered as no instructions told me to.
I am afraid that I have to tell you that those instructions were certainly available. I can look it up for you. I made the same mistake twice before I learned to install in a custom folder. I really advise you to do the same now. Otherwise you’ll be in the same boat the next time.
So frustration now, but lesson learned for the next time.
Same here, left beta program, small update, and then the big 115G update. It has nothing to do with custom folder or standard folder. You had no choice and need to install the 115GB. Ridiculous!!!
More usefull changes to make !! - if you understand what they do, and they are appropriate for you
Thanks
I followed the instructions that were given on the pinned post for those of us that were part of the preview build. Nothing about custom installation path. So with respect I suggest that although you have read it somewhere before it is clearly not been communicated sufficiently in regards to this specific update.
You are absolutely right and I was just posting an excuse to you. This was pointed out for a previous beta and I really don’t know why the cm’s did not repeat this important information this time.
EDIT: See below. I knew it was posted but doubted myself because I could not find it anymore. I was corrected by @SeedyL3205 So my excuse should actually go that way!
Yes I was in the Beta
Crashes everytime during the update phase in Content Manager. I have the Premium Deluxe version, no mods, all stock from the Windows Store - some 3rd party aircraft through marketplace. Can not update the sim - as soon as I click update, CTD. Can’t experience the sim, at the moment.
I wasn’t in the pre release/preview.
We advised all players participating in the Pre-Release Test about the risk that a full re-install might be necessary later and how this risk could be mitigated by using a custom installation path in two separate threads announcing the availability of the test on MS Store/Xbox and Steam, respectively:
We also explicitly mentioned this risk in the December 2nd Development Update Blog post when the Pre-Release test was first announced:
CTD after pressing the download button in content manager!!
See above. We absolutely shared this information at least three different times.
Thanks @SeedyL3205 that was the post I was looking for!
Widespread issue. Massive problem, at the moment. Update should be pulled.
Oh well thats unfortunate😓
This. Spot on.
If you are not in the habit of creating a spare folder somewhere to drag and drop community files into before an update then more fool you.
But didn’t put it in pinned instructions. Surely you should expect that is where most people will look when they want instructions on how to swap over, not remembering a post from weeks ago or checking old threads on a forum.
Why didn’t you?
What pinned instructions are you referring to?
When I joined the Beta, I did, with the full knowledge and intentions (even if not necessary), that I would do a complete CLEAN re-install of MSFS when the next SU was released.
While it may be totally unnecessary, at least with a Clean Install, one is starting again with a “Clean Slate” (To use a highly Technical IT term !! )
I have also found, that a Total re-install is not so painful, if you resist the urge to sit there for hours, , watching it download & Install, but instead, go and do something more constructive .. 