MCDU: Misaligned / cut digits of VOR frequences

[mcnobody]

Dear iniBuilds Team,

when entering VOR / ILS names manually into the MCDU - i. e. the IKA VOR - certain frequencies are misaligned or cut on the duplicate names list. See the 1st, 3rd and 4th entry on the following screenshot:

The named stations are all ILS frequencies and I guess the last zero (0) is cut.

As usual: I don't have any real world documents. So I can say if this is actually a bug or a function of the MCDU.

Christian

[Crabby]

From what I can see, there are 6 different navigation items in the world called IKA

2 NDB stations

3 ILS

1 VOR/DME with FREQ 114.30

So, the VOR is shown correctly. 

As for the first entry, the GPS coordinates shown are for one of the ILS stations and the freq is 109.3.  The third entry is an ILS with freq 110.1.  The last is an ILS with freq 111.70.  Again, all based on given coordinates.

Now, the question is why.  

Are you using Navigraph in the simulator? (Replacing the simulator base data with the Navigraph data.) If you are, try it without that.  If you aren't, it could be an A300 glitch or a sim data glitch or some combination of both. 

Either way it is not the VOR stations that are cutoff.  

 

 

[mcnobody]

4 hours ago, Crabby said:

Are you using Navigraph in the simulator? (Replacing the simulator base data with the Navigraph data.) If you are, try it without that.  If you aren't, it could be an A300 glitch or a sim data glitch or some combination of both. 

I am using the current data by Navigraph. It might cause the trouble but the problem doesn't exist with the FBW A32N nor with the ATR72. Both of them using the MSFS navdatabase as far as I am aware.

 

4 hours ago, Crabby said:

Either way it is not the VOR stations that are cutoff.  

I have already pointed out that the ILS frequencies are the ones being cutoff. My topic title is a bit misleading.

[Crabby]

1 hour ago, mcnobody said:

I am using the current data by Navigraph. It might cause the trouble but the problem doesn't exist with the FBW A32N nor with the ATR72. Both of them using the MSFS navdatabase as far as I am aware.

I have already pointed out that the ILS frequencies are the ones being cutoff. My topic title is a bit misleading.

Neither the FBW 320N nor the ATR72 are the INI300.  This is important in any trouble shooting/support endeavor.  That start will always throw the process off.  Treat each plane/developer as individual cases.  It is just as bad as "well it worked yesterday".  

I question whether the ILS stations should even show there.  I will have to dig in the FCOM, but that page should be reserved for navigation aids (VOR, Fixes, ADF) only.  Maybe this is the way the 300 did it, as it is an old aircraft.  I will report back what I find on the FCOM.  

[Deleted Account]

Thanks, will take a look 🙂