Products Support > Honolulu FSX/P3D

No ILS in FSCommander

(1/2) > >>

peacedivision:
Noticed a small issue today after updating the FSC database, PHNL now shows no ILS for any runways.  The ILS is still there in sim, works fine and shows on the map within FSX, only seems to be a problem with FSC.  All other FSDT airports display correctly.

No approaches at PHNL
http://img683.imageshack.us/img683/171/noils.jpg

KFLL as correct example, all other FSDT airports display as such.
http://img190.imageshack.us/img190/1808/kfllils.jpg

Thanks!
-Sam

virtuali:
That's obviously a mistake by FSC, since FS9/X doesn't require to duplicate Navaids and Approaches inside an airport AFCAD. And in fact, you confirmed yourself that they work in the sim.

There's no point to copy that data from the default scenery, if it hasn't changed so, PHNL AFCAD doesn't contain any Navaids and Approaches.

Other utilities, like AFCAD, are smart enough to know this and, they always show the Navaids for the area around the airport, coming from the default scenery files. If FSC doesn't do this, it's a design shortcoming.

peacedivision:
Thanks! I will report the issue on the FSC forum as well.

-Sam

Steve Waite:

--- Quote from: virtuali on February 03, 2010, 08:12:02 am ---it's a design shortcoming.

--- End quote ---

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.

http://www.codelegend.com/forums/viewtopic.php?f=4&t=231

Thanks
Steve

virtuali:

--- Quote from: Steve Waite on September 26, 2012, 07:02:35 pm ---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.
--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page