|
From: Emilian H. <emi...@gm...> - 2018-05-08 08:29:08
|
On Tuesday, 8 May 2018 11:05:03 EEST James Turner wrote: > > On 8 May 2018, at 08:47, Gijs de Rooy <gij...@ho...> wrote: > > > I only see taxiways in the launcher and the in-sim Location > Select > > > Airport map for the default PHNL.> > > Just found another one that works: PHOG, which is also on Hawaii. The > > other Hawaiian airports don't show any taxiways though. Maybe they just > > don't have any.> > > As far as I know taxiways come from apt.dat, since groundet.xml only contains the AI network, not the actual pavement. PHOG.groundet.xml for example has no absolutely no taxiways defined. I think this doesn't fit your idea: > > > James wrote: > > > gets parking / taxiway information from the groundnet.xml files > > > > Maybe there's the problem? > > Sorry, I was getting mixed up: parking and ground-net data comes from > ground-network.xml, used by AI for taxi-paths. ‘Visible’ taxiways / aprons > comes from apt.dat as you point out, and only exists from some subset of > airports. We have a long-standing issue to get the taxiway data out of > apt.dat (since it bloats it) and into the ground-net files, since that > would also make editing easier. > > But, the flip side then is airport BTG generation needs the ground-net > files, which currently it does not. > > This is all my recollection anyway - does that with the observed behaviour > and other people’s understanding? Corrections are welcome, as are bug-fixes > :) > > Kind regards, > James Nowadays WED has ai/groundnet support (in the apt.dat format of course, not sure if it supports as many features as the groundnet.xml yet), maybe that policy should be revised for the next world build? it would reduce much of the confusion/disorientation regarding the airport/ground-ops/ai and the relation with the X-plane airport gateway. Regards, Emilian |