Re: [Flightgear-devel] Helipad thresholds

[James T. <ja...@fl...>]

> On 23 Jun 2023, at 17:01, David Megginson <dav...@gm...> wrote:
> 
> That's great news! Last fall, supplying a custom apt.dat didn't put my aircraft in the right starting location (it was still using the default apt.dat), which is why I explored custom threshold.xml files in the first place.
> 

This code hasn’t changed in a few years, so I suspect there is something not working right in the code. Can you detail a bit more, what you tried and what is going wrong?

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 don’t *think* theshold.xml files add any new information to the mix, they were merely a way to override the base apt.data when we didn’t have support for custom apt.dat files in scenery.

> 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.

Kind regards,
James