|
From: Florent R. <f.r...@fr...> - 2023-07-01 16:25:10
|
Hi, David Megginson <dav...@gm...> wrote: > That sounds like the right plan, Florent. If scenery has overridden an > airport in a custom apt.dat, then only supporting files (thresolds, etc) > from the same place should apply. AFAIK, the supported types of XML files in this context are: groundnet, ils, procedures, runway_rename, threshold, twr I'm wondering whether to apply the rule to all of them or if, say, “procedures” would be better with an exception. I assume a few people have $FG_SCENERY like so: some_custom_sceneries:procedures:terrascenery with the “procedures” folder containing a gazillion *.procedures.xml files (possibly obtained from Navigraph). If we strictly apply the proposed rule, said procedure files wouldn't be used for airports that have an apt.dat snippet in some_custom_sceneries. Of course, some_custom_sceneries could ship appropriate procedure files, though. Would it make sense to let XMLLoader::findAirportData() work as it does now for the special case of procedure files? That would be a bit more complicated, of course... Regards -- Florent |