my questions are:
- how should i create the necessary .dat file for fgfs to know where these airports are?
- is a minimal apt.dat type file all that's needed? by minimal i mean one that has just the bare necessities...
- Code: Select all
A
1000 generated by hand by some person
1 ### # # ICAO common name
99
in the above maybe a 100 line if needed... - noting, again, that the ones i've checked already have runways in fgfs, is this something that has to be done in WED?
since the runways already exist in the scenery, i'm guessing that the airport does not have to be created... only the definition is missing for some reason... i have checked a few at the x-plane gateway and they don't have anything for them...
the list i have is of about 200 ICAOs... i don't know if this is all of them or not... they are the ones i see generated while sitting at KATL but i plan on sitting at other airports and gathering any others that the traffic manager complains about... i can share this list if someone wants a copy of it... my script simply grabs them all from my log file, sorts them and keeps only the the unique ones... while it does look for both "arrival" and "departure" airports, it doesn't care which it is and drops that word so all we see is something like
- Code: Select all
Traffic manager could not find airport : EGDG
Traffic manager could not find airport : FAOR
Traffic manager could not find airport : FCOD
Traffic manager could not find airport : FLKK
Traffic manager could not find airport : FYWV
the above are the first five in my list... all of them have runways except for FCOD...
the main thing i want to do is to get the traffic manager to stop crying about missing airports and then we can get on with what else needs to be done to fix them up...