Many of the 3rd party developers like Fenix, IniBuilds, FSDreamTeam, FSHud, Axis & Ohs, FSIPanel, etc. have quickly mobilized and produced viable Fs2024 versions of their products. Not perfect but good enough. Some have charged us and some have made their upgrades available for free. They have scrambled and made sure FS2024 had their support.
Others (we know who they are) have sat back, explained/complained about how much work MS/Asobo has created for them, provided dramatic hand waving excuses about product roadmap decisions, and said things like “It will take time and we will be ready when we are ready” or “This is hard, please be patient”. One VERY popular/high-end airport developer has still not made a statement about their 2024 compatibility plans. Seriously?
This scenario may permanently compromise the adoption/engagement of FS2024 and negatively impact the future revenues of the developers dependent on FS2020/2024 for their livelihoods. Folks are running from FS2024 because of the bugs AND because of the compatibility issues. They are turning to other games and other hobbies. They are getting frustrated, angry, and losing interest in Flight Simulator. This could be temporary but could also permanently diminish interest in MSFS 202X.
Waiting for Asobe to magically fix compatibility is not the answer. The 3rd party developers must seize the moment and get some of their key products working–we know this is possible from the work some have done. In the same way the FlyByWire A320 helped save FS2020 early on, FS2024 needs major investment and support from the developer community to take root. Charge us if you must but please move ahead with great speed. Time is not your friend.
Let’s all support the developers (yes, financially) who quickly embrace FS2024. And, perhaps more importantly, let the others know we need them to lean in now. MS/Asobo may have made this mess but the community of developers and their customer’s support need to help fix it.
