I am confused about what I am seeing in reference to SABA airport and I do not know how to fix this issue.

In Little NavMap it shows the airport as if it does not exist runways 12 & 30 have an X through them, but in Plan-G all is OK. Both programs are using the same Scenery.cfg - C:\ProgramData\Microsoft\FSX\Scenery.CFG.

Can you offer any suggestions regarding this issue - see attached two print screens, one from Plan-G the other from Little NavMap.

Thank you, Dane.

 

https://photos.app.goo.gl/UbHYJWNQLPjiovti2

https://photos.app.goo.gl/Knk9cFcXWwMIU8343

Hi Dane,

the runway numbers are x-ed out when the scenery indicates that the runway end is closed. See here in the SDK documentation. If all runways of an airport are closed I mark the whole airport as closed.

There should be a yellow X on the ends if the scenery is correct. http://www.airliners.net/photo/-/-/723905/L

I doubt that Plan-G uses and displays this information at all. 

Alex

 

 

5 hours ago, albar965 said:

Hi Dane,

the runway numbers are x-ed out when the scenery indicates that the runway end is closed. See here in the SDK documentation. If all runways of an airport are closed I mark the whole airport as closed.

There should be a yellow X on the ends if the scenery is correct. http://www.airliners.net/photo/-/-/723905/L

I doubt that Plan-G uses and displays this information at all. 

Alex

 

 

Thank you Alex, yesterday after several frustrating hours I learned so much about airports and runways. All is now good as I spent another several hours learning about ADE and used it for the first time. I opened the airport back up. I had to do that because AivlaSoft EFB simply did not even show an airport at all, at least LittleNav Map displayed the airport but marked it closed. I have now opened the airport for my flights.

 

Thanks again, Dane.

Hi Dane,

I also fixed some of my preferred local airports. Sometimes you have no choice if there is no pay or freeware.

Alex