Actually you missed the nav designations off the runway records so the runway records actually point to NO NAVS which is a design shortcoming of the airport.
You don't need to include the navdataa file with the airport but you should always state the nav designations for the runways if they have them.
There's no requirement to copy ILS data into the runway of an addon AFCAD, just as there's no requirement for Navaids, FSX will use the ILS of the underlying stock scenery.
In fact, as the user confirmed "
The ILS is still there in sim, works fine and shows on the map within FSX" so, I repeat this is a design shortcoming of navigation products that don't replicate the FSX standard behavior exactly.
And, as I've said in my previous message, not ALL programs are being fooled by this method. Both AFX and ADE will show ALL default stock Navaids INCLUDING ILS, when opening the FSDT PHNL AFCAD. And this is a more correct representation of what would appear in FSX while flying.
So, the real question is not why there are no ILS at PHNL, because they clearly works in FSX but, why some addons programs behave like FSX and display ILS coming from the default scenery together with the custom AFCAD, and others don't.
I agree that working with data coming from multiple AFCADs at the same time is more complex. GSX, for example, has the same shortcoming, it works only with self-contained AFCAD, it doesn't really support overlays with (for example) parking informations coming from the stock scenery and taxiways coming from an addon AFCAD. But we recognize this being a GSX limitation, I wouldn't say developers using these methods are "wrong" or made something not correct.
