Again I am replying to an old topic, but after the last Hawaii scenery updates in December 2013 (thank you) and FSCommander again do not list these ILS's, I have to reply again.
We haven't changed anything in the AFCAD files, I've checked all of them, and none is newer than end of 2012.
I want to point out your AFCAD files DO duplicate data from the FSX default scenery, all add on scenery AFCADS I have, does. All the navaid data is in your AFCAD bgl file, just as it is in the default FSX one.
No, they don't.
You are mislead thinking that we might have duplicated FSX navaids, because ADE or AFX will SHOW you those navaids when you load our AFCAD. But they are NOT coming from our AFCAD, they come from the FSX default scenery, that's why the AFX, for example, will indicate those navaids as "Stock", because they DO NOT come from the AFCAD you just opened.
All your, and other scenery developers' AFCAD files have the applicable runway ILS Ident info and the navaid data in it and IS "duplicating" the FSX default scenery, as you put it. It is only some of your Hawaii scenery AFCAD files that don't have this ILS Ident data, causing a very nice flight planner not to show the ILS info.
Of all runways of all 5 Hawaii airports ( PHLI, PHKO, PHTO, PHOG and PHNL ), there are ONLY 2 ILS included in our AFCAD, ALL of them DO NOT have any ILS or any other navaid, they all come from FSX.
And of course, there's a sound reason for this, we haven't "duplicated" those two, they have been modified, sometimes slightly moved, sometimes because the heading wasn't entirely right or for any other reason where the default data didn't work.
If a navaid should change, there is no complex procedure, only update the one applicable addon AFCAD file, no "chasing for that navaid into each scenery that copied it from the default".
If updated navaids are duplicated, you must duplicate your update work for each scenery that duplicated them. That's why it's wrong to duplicate data.
As you know, FSX reads the addon scenery according to priority, so the file with highest priority will be displayed. So does FSCommander
No, there are EXCLUSION rules.
Something on a higher priority will hide something below it ONLY if the higher level AFCAD contains an Exclusion command with the bits active for certain object class (navaids, buildings, approaches, jetways, etc.), FSCommander is just *ignoring* the Exclusion commands altogether, and consider an higher priority to automatically exclude everything below it, but that's not how FSX works. FSX will display *everything* that hasn't been explicitly excluded, coming from many files at the same time.
It's not a "shortcoming of a flight planner" if it ignores the default, reads the addon AFCAD at higher priority, sees no ILS Identification linked to a runway and then don't display the ILS.
Yes, it's a shortcoming of that program, because it doesn't recognize something that is legal for FSX. As I've said, even GSX has that shortcoming: it only takes data for a single AFCAD at time, it doesn't work with "partial" AFCAD files. But I'm admitting that IS a GSX shortcoming, and we'll probably going to fix it, because partial AFCADs are a legit programming method.
However, this shortcoming is less severe for GSX, since for a ground operation program, it's enough an AFCAD contains parkings and taxiways, and GSX can work with it. It's far more serious for a Flight planning program, because NOT duplicating Navaids is FAR more common than using partial AFCAD that don't contain parking/taxiway data and rely on the default airport.
I thus fail to see it's "just wrong to start duplicating data" because you and all scenery/AFCAD developers already do it anyway
No, we don't. Except when they ARE different from default.
. All I ask is just for the AFCAD developer of this Hawaii scenery to add the runway ILS Ident info with a next update. I did it to the PHNL AFCAD on my side and just took me about a minute.
Then take 5 minutes and do it for the other 4. I firmly believe it's wrong duplicating identical data, just to work with a single 3rd party program that needs it.
