Note that on Xbox, you can choose not to install about 60 GB of “offline world data”, and let it stream on demand. On PC IIRC you can manually remove the files I believe, but have to install them first, then delete them to free the room back up or something? No user interface is provided for it, in any case.
(The Xbox interface for this is in the system’s app/game installer UI, not part of MSFS itself; they packaged it such that the offline data is an optional component included by default.)
I think a good summary of MSFS is this article here:
With the key words being “a work in progress” - a lot of this AI stuff is dripping off the bleeding edge and is doing the kinds of stuff that “boldly goes where no game has gone before” - and yes, there are going to be bumps in the road or places where the rendering absolutely stinks, (like Canada’s update), but as they used to say, it comes with the meal.
Could they jump on massive screw-ups like Canada more quickly? Of course they should. However, I don’t know how they have things set up and since I’m not there, I’m not really competent to judge them from the comfort of my armchair.
And to be clear: this applies to long-term work, because hiring people takes a lot of time. When we’re talking about “they introduced regressions in the latest version and they should fix them immediately” then there isn’t time to hire and onboard new software developers and get them productive on your huge code-base in a few days.
Did you miss the dozen world updates dedicated to scenery, all for free? Many folks actually criticize the Devs for spending too much time on the scenery, so this opposite take is funny.
If one reads the forums regularly, bridge fixes are a small minority of requests from users compared to many other issues, including weather, ATC, flight modeling, performance issues, live traffic, SDK capability, water physics, broader photogrammetry issues…shall I go on?. That’s just how it is.
ArchBlizzard, Thank you for your reply and concern. Oh, no need to go on and on… I, like most MSFS owners are very well aware of all the new and old “Bugs and Flaws” being addressed or in someone’s’ please fix wishes.
…
I have not missed a single update. I am the proud owner of every single update bit provided to the MSFS owners, however, I was hoping that one day, along with all the eye candy being added and all the continuous fixes being addressed, a few missing bridges and span errors might be corrected.
…
Only about 8 years left so they have plenty of time, there is no rush.
Regarding the idea that this topic is just mindless whining, my two kopeks:
As has been said before, these topics come and go, but has anyone thought about the “why” and “wherefore” about this phenomenon?
As I see it, there are two aspects to this:
Asobo/Blackshark are dealing with the dripping edge of the bleeding edge in commercial AI for building and terrain modeling. This isn’t easy and the models can, should and likely will improve over time.
A lot of the whining is caused by the apparent lack of concern that the game function properly at the most basic levels - graphics, aircraft dynamic modelling, gross scenery as opposed to picky details, and other issues that represent fundamental flaws. Note that I’m not worrying about smaller issues - even things like sunken bridges, (which are a disgrace IMHO), I am talking about fundamental optimization and cleaning up Sev-1 bugs that destroy the ability of many users to even play the game.
Many commentators have mentioned the way bugs appear to get swept under the rug - either not accepted since they existed from day-1 (and are not “regressions”), or are consigned to the bit-bucket and marked “won’t fix”.
All of this causes frustration and a bad taste in many users mouths, including myself. I would love to see these people make a concerted effort to clean up their bug lists and reconsider fixing bugs that were “swept under the rug”.
This isn’t impossible to do, all it takes is for The Powers That Be to say “Hold on - we need to stop and regroup and look at where we are now.” If they decided to spend this next year doing nothing but bug busting - and not releasing any new content - I’d be a happy bunny and so would many others.
Be able to save a flight and load it without having half the sim excluded like the entire toolbar plus flight plan still wont load into a saved flight.
Fix world map, it constantly after setting a origin and destination wont let you add any way points without going back to main menu then back into the map.
They are, there’s proof in the VR bugs section whereby a new regression bug was closed and listed as “won’t fix” and another that was pushed way way down the pecking order (I forget the actual words used).
Whilst they’ve finally at least acknowledged it, the right mouse button blocking controls is still my number one issue that exists, and it has since SU5!
Aircraft registration and airline should be saved per livery.
If you’re not on XBOX, you can permanently change these in the livery’s aircraft.cfg file. I’m surprised to hear you’re finding that they haven’t been by the livery developer.
If your in game registration and airline are left blank (They will override any livery’s setting), then the livery’s values will display correctly.
Ground staff and services can also be disabled in the aircraft.cfg file for each aircraft/livery.
I think we do have different definitions of “sweeping stuff under the rug”. While it isn’t cool it won’t get fixed, it’s imo not sweeping under the rug, but giving a transparant explanation that this is not going to be fixed soon.
(Personally I never had any problem with this, because I close all windows always immediately if after I’m done with them)
For me it’s the pop-up menu icons constantly rearranging themselves. There are more serious bugs and issues, but for some reason that’s one of the ones that annoys me the most.
I think it was nearly a year ago when Jörg mentioned that they will be hunting bugs right after the “Game of the year” update. When the next SU went live, what have we gotten:
A few bugs fixed, some new bugs introduced and a ton of new half baked features.
So, yes!
MSobo should tidy up the code, ASAP.
Errors occur, no question. But when you know about an error that was introduced a week ago with a major update, you should fix it with a hotfix. And not (eventually) 3 months or 2 years later!