Possible to disable MSFS custom airports without disabling their libraries?

[MSFS 2024] Questions & Community Discussions Airports & Sceneries
,
1

Is there a workaround to disable MSFS custom airports without disabling their libraries? I ask this, because I’ve already run across users who happen to run freeware for one airport alongside payware for another airport that happens to disable a set of needed custom MSFS libraries, thus disabling libraries that are referenced and needed for the freeware to display properly.

I’ve read that if you rename the folder of the 3rd party software to the same name as the MSFS default, it should override the default airport without disabling its libraries, but I wanted to make sure that actually was the best solution…if it works at all.

The issue came up in my own KMTJ scenery (KMTJ Montrose Regional (Colorado) - Airports for MSFS | Flightsim.to) that referenced a building from KSEA, but a user is using MK Studios KSEA, which is disabling the building at KMTJ.

Thanks

2

Yes, it IS possible to disable MSFS custom airports without disabling their libraries. Using KSEA as an example, here is the “trick” to reenable the KSEA libraries without disturbing a 3rd party KSEA addon.

  1. In MSFS 2024, go to the Marketplace, My Library, search for KSEA, and download and install the “Base” Asobo KSEA.
  2. Close MSFS 2024.
  3. Go to the folder (your path may be slightly different): Official2024\OneStore\Asobo-airport-ksea-seattle-tacoma
  4. Go to the path “Asobo-airport-ksea-seattle-tacoma\scenery\Asobo\Tacoma” and delete the single “ksea.bgl” file.

This will deactivate the “airport scenery part” but will leave the model libraries intact.