Dangerous Beans
SOH-CM-2022
Just got a 1Gb update from the Xbox store.
I've had a look on the MSFS forum but nobody seems to know what it fixed.
I've had a look on the MSFS forum but nobody seems to know what it fixed.
Just got a 1Gb update from the Xbox store.
I've had a look on the MSFS forum but nobody seems to know what it fixed.
What are WASM and RTC ? I have the cinematic turned off anyway so I probably wasn't affected anyway.
I set all my controls through FSUIPC so I'm not affected by that either.
I'm surprised you guy got a 1 GB update to download.
On Steam, I got something that was maybe around 200 MB yesterday night ? Or is there anything additional to download from inside the sim ?
The Paderborn addon is the only other thing I had to download too.
I do have one odd thing that's happened since the update. All the files in my community folder are showing as not installed in the content manager.
I don't get an install button to click if I select them either.
They do work just fine though so I dont know whats up with that.
The " not installed" thing I noticed right away and reported here. Then there's the permissions issues associated with the Community Folder. I'm one of those MS Store users who can delete, but not copy anything from the Community folder (CF). I don't have "permission". Searching for a fix came up empty handed.
One thing I came across is a cool utility called MSFS Addons Linker. This utility basically allows me to create a folder outside of the CF to install addons into, and then I link to them leaving the CF empty for future updates. A cool feature is that I can create preset "scenarios" and load only what I want to use near my base which probably helps with processing.
It's very intuitive and I would recommend it for, avoiding the 'permission' issues, and staying organized. Here is the link if you're interested,
https://flightsim.to/file/1572/msfs-addons-linker
Fnerg, I'm going to take a guess that you installed MSFS to the default location which would put it in a protected system folder.
Thats been a long time bug from FSX and the old advice is to install to a custom location preferably on another drive.
Asobo probably originally programed it so that wouldn't be a problem but the latest update broke it.
My MSFS is on my D drive and I don't have any problem editing or moving file in it.