|
From: Florent R. <f.r...@fr...> - 2023-06-28 15:18:45
|
Hi, James Turner <ja...@fl...> wrote: > In *principle* (modulo any bugs) custom apt.dat can add or replace runway data > from the base apt.dat; I can’t recall if removing runways is possible. I think it is, because for a given airport, the first apt.dat snippet found in $FG_SCENERY order that has data for this airport provides *all* the data for said airport: https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Airports/apt_loader.cxx#l163 IOW, if data for the same airport is found in later apt.dat snippets, it is ignored (skipAirport is true in these cases). >> That said, if there is a default threshold.xml for the airport, will that >> supercede my custom apt.dat? > > > Yes, I think right now the scenery overlay XML files are always processed, so > this might cause some troubles. Unless we have a way to suppress loading the > XML files when using a custom apt.dat, and I would need to dig into the code > further, to answer that. I believe there is no such way: I probably didn't know about *.threshold.xml files yet (and *.twr.xml, *.ils.xml...) when I added the possibility of gathering apt.dat data from scenery folders. Regards -- Florent |