MSFS 2024 update 1.2.7.0 includes the ability to enable/disable content but is it necessary to disable default airports to prevent conflicts with 3rd party counterparts?
I raise this question because I have started to disable a few of my default airports and can see no difference in terms of appearance or performance. (Win 10 PC).
I don’t recall ever disabling anything in MSFS 2020 after being informed the sim automatically prioritises add-on scenery and more recently I think I may have read somewhere that 2024 has similar logic?
The only default airport I uninstalled from FS20 was when I purchased the Swedish three airport (direct from Orbx). They recommended uninstalling the default ESNQ (Kiruna), perhaps because it was an Asobo handcrafted one.
I’ve not heard of any similar advice to uninstall default airports from FS24 if you have a third party airport.
However, why not just install the third party airport without disabling the default to see if they clash. If they do disable the default.
If, as you say, you have not noticed any difference without disabling the default then I think you’ve answered your own question.
Yes, fair comment but whilst there may not be any noticeable difference visually, there is a suggestion (from another source) that if both versions are enabled, the sim utilises valuable resources to process the default which, of course, is not desirable.
I’m hoping a dev or similar will confirm either way … own quite a bit of payware airports and don’t want to start trawling through all default airports to disable duplicates if it isn’t really necessary.
On the other hand, not a problem, well into ‘sim housekeeping’ will see this as good maintenance if this is what we need to do
@slicker55 Good question! Some add-on developer recommend disabling the MSFS defualt airports when their equivalents are in use.
My guess is that the most critical issue among 3rd Party airport add-ons would wether they were complet replacements for the MSFS defaults or just extensions, fixes or other mods.
In the latter case, they might rely on parts of the MSFS defaults. In that scenario, removing the MSFS defualt would “break” the airport.
Thank you for taking an interest in my post … the plot thickens … so, it could be a mistake to simply go through all duplicates and disable them … possibly, no way of knowing without physically checking each airport one-by-one … time consuming exercise for folks with a lot of payware, like myself, might be best to leave well alone?
@slicker55 If you are talking about payware, most I have seen are complete replacements MSFS defaults. Freeware runs the gamut from complete airport replacements to minor default scenery modifications like windsock animations.
But check the following before doing anything drastic or time consuming:
The product description at the developer’s website. If there is somesort of conflict with the MSFS default scenery, this is where you are most likely to find a recomendation to disable something.
Any FAQs or product support pages at the developer’s website.
Product discription pages on other websites that retail the product (e.g., FlightSim.to, SimMarket, iniBuilds, OrbX, etc.).
Product reviews on websites like FSElite, FSNews, etc. and on YouTube.
I don’t know about FS2024 because I haven’t been able to test it yet, but in 2020, sometimes third-party scenery and any included “handcrafted” scenery would overlap and generally result in a mess. For instance, I have the Orbx Catalina Island scenery, KAVX. When Asobo added a Gaya-made handcrafted version of KAVX as one of the US World Udpates, it made a complete mess of melded buildings and scenery elements, and a disasterous terrain morphing issue along the taxiway. After that, I made it a habit to uninstall any included airports in the sim when I bought better 3rd party versions: KJFK, KLAX, KSFO, EGLL, etc.
If I can disable the duplicate Asobo airport, I will. While most third party devs will create an exclusion area to hide default airports, this isn’t always the case, there have been a few occasions where duplicate airports have loaded together, causing performance issues, or even CTDs.
With 2020 I always disabled any default airports when replacing with 3rd party airports. Haven’t had the time to update and test with 2024 yet, but will be doing the same.
