Now that 2024 has been announced and all these updates of juicy details start to filter down to the masses i cant help but wonder, Where does 2020 stand now in the eyes of MS/Asobo?
Devs are still updating products but are MS/Asobo looking at fixing the bugs/ issues that are still being reported?
There are many issuse occuring across both platforns but do any of them actually get fixed now or do they get top drawed til the servers are switched off?
What are your opinions?
How long will you wait for the experience you had before SUxx played havoc with your hobby?
As we have previously announced in our Microsoft Flight Simulator 2024 FAQ, support for Microsoft Flight Simulator (2020) remains ongoing. We released three updates just last week (Bullseye Landing, World Update 14, and Local Legend 11), and next on the roadmap is Sim Update 13 in September (with a beta test starting soon). SU13 will include many bug fixes and improvements to MSFS.
Additionally, support for the current 2020 version of Microsoft Flight Simulator will continue after MSFS 2024 launches.
What kind of support can Microsoft Flight Simulator (2020) players expect to see once Flight Simulator 2024 has been released?
We will continue to deliver our Microsoft Flight Simulator (2020) Roadmap which has content ranging from Aircraft and Avionics Updates, Sim Updates, City and World Updates, and also the free Dune DLC. We will continue to support Microsoft Flight Simulator (2020) post the Microsoft Flight Simulator 2024 launch.
Does âsupportâ after the end of the 2023 âroadmapâ timeline mean âcontinued bug fixes and compatibility with new plane and scenery releasesâ or âthe online services will remain onlineâ?
But does any of that mean any attention to the issues still being reported and them actually being fixed. For example console multiplayer stuttering and vanishing players?
Unclickable nav point data on the planning map?
Overly loud exterior wind noises inside the cockpit?
Missing ATC voices at major airports?
The list grows everyday but no one seems to see any remedial work taking place. Only 2024 will be better than sliced bread statements.
I don´t know what they think and how they would define support but AAU2 is causing a CTDs nightmare everyday to many users and next SU is planned for september. Instead of hotfixing the CTDs we had fireworks, more new content and they went on holidays afterwards.
Now I can´t play game as everyday I get several CTDs either while flying or simply when moving around at world map to create a flight plan. Should I wait until september just to have a game than can run without crashing or should I wait for next year? It´s really hard to think on FS2024 as the silver bullet solution to most of the existing problems when we can´t even have a game that runs without CTDs for more than a few months now and the fixes take ages to go live.
I was glad to see this topic because Iâve been wondering if the worsening ATC/Co-pilot voice problems and what seems to be an increase of CTDs reported on the forum (Iâve had two in the last two weeks after not having any for months) is because of Asoboâs (I assume Asobo is the developer of FS2024?) attention and effort is now focused primarily on FS2024. Updates and new content are always welcome but not at the expense of fixing current problems. Unless more programmers have been hired I have to assume there are not as many focused on FS2020 as before.
I think you missed an item on the âroadmapâ which was said to be released alongside WU14, the so called âworld hubâ (aka scenery gateway). I really appreciate every update delivered for the current 2020 version, but is this still in development or âpostponedâ for the future 2024 version?
When MSFS 2024 releases, MS2020 will be a legacy product. More than likely, this means that nothing further will be added to the roadmap and active development work will cease. Legacy support generally means doing the bare minimum (which is hopefully nothing) to keep the product running and secure.
As far as forward compatibility with new add-ons goes, that is going to depend on the capabilities of the SDK and the Independent Software Vendors (ISVs) themselves. It sounds like the new SDK features for MSFS 2024 will be a superset of the MSFS 2020 features. If that is the case, it may be possible for ISVs to create add-ons that degrade to legacy functionality if they are being run on MSFS 2020. Whether that happens will largely depend on how much work it is to do so and whether the ISVs can justify doing that work.
This of course, is all just an educated guess on my part. The bottom line is that with most âoff-the-shelfâ software from Microsoft, if you are satisfied with it on the day that it becomes legacy, then there is no reason for you to upgrade. If you want new features and fixes, then you should upgrade. That said, existing bugs that make it into the new version are less likely to be fixed as they would need to represent serious pain-points affecting vast swaths of customers in order to get enough visibility to supplant work on the new stuff.
Iâm not sure why people are upset about MSFS 2024. Versioning happens to âoff-the-shelfâ software and this is what it looks like. Anybody who wants to keep using MSFS 2020 will be able to do so until it reaches end of life in 2030. It may even be possible to use MSFS beyond thatâall end of life means is that absolutely nothing will be fixed, but if the product continues to run, nobody is going to stop you from using it.
The same system that didn´t have any CTDs with SU12 nor during the whole 2023 but started to reproduce them just after updating to AAU2? The same one that had CTDs during a part of 2022 only and not during the other? I highly doubt the users systems are the problem here.
Indeed I also had no CTDs while other users were having them in the past. But this doesn´t mean there was no problem at that time just because I was not reproducing it. How many times have we seen CTDs and stability fixes in patch notes after the last 3 years? This is a never ending history. Source code generates them and patches solve them afterwards.
did you tried with empty community folder ? sfc /scannow command or this ?
try to delete the content of these 2 folders (before starting the simulator)
C:\Users\YourUser\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes
C:\Users\YourUser\AppData\Local\FlightSimulator (Donât worry, they will create themselves when you start the simulator)
This is not solving the CTDs. The problem is not related to content nor any local config files you have. App crashes now do to wrong memory allocation. It´s therefore a memory management problem and that´s caused by game client. Until exe file is updated this won´t be fixed.
MS said FS2020 would be supported for ten years, and I am sure they will honor that promise, just like they honored the promise that Windows 10 would be the âlastâ version of Window with perpetual updatesâŚ
Iâll stay with both 2020 and 2024 until I feel like yknow maybe Iâll only fly on this,
I started with P3D,FS2020,XP12,then 2020 again and no matter what P3D makes me feel bored and Tired of not having amazing sceneryâŚâŚâŚIâll stay with fs2020 only if 2024 fails but if itâs good,2024
And therein lies the problem. The community gave FS the 2020 moniker, Asobo and MS have always officially called it âFlight Simulatorâ. The way I saw it, it was essentially a reboot of the franchise, though some may not. Now you can blame this on bad marketing and during recent events, this has changed, with Jorg now even officially recognising the FS2020 moniker. The bottom line is, it was never about FS2020, FS11 or FS itself, as in the August 2020 version being supported for 10 years but the platform as a title.
The fact is, FS2020, the version, will be supported going forward. What this means, who knows but if MS/Asobo have officially said it will be, then Iâm inclined to believe them. Will it eventually have support cut, yes, probably, but I canât see them just shuttering it. Much like console gens, car models, everything, things move on, technology changes.
I think a number of folks are a bit miffed that so many core bugs have been ignored (or added) in the last 3 years, and the only hope we seem to have of ever getting them fixed is to buy the product again, still with no guarantee of any specific fixes.
Itâs perfectly fair to give me new features and new content in a new version with a new dollar cost, but itâs easy to feel like youâve been taken for a ride when basic stuff doesnât work (numerous bugs as reported all over the forum). Iâm grateful for the improvements from them hiring Working Title to start redoing the autopilot and Garmins! But thatâs honestly the main thing that Iâve been happy about as a customer.
Shrug it is what it is; most of us will either pay in by buying the new version explicitly or paying in via Game Pass. Will our bugs get fixed? Maybe, maybe we have this same conversation in 2027 about FS28.