Hi there! I have notice that the LOC/ILS 110.30 LB ILS-cat-II is missing in MSFS 2020. It is only a RNAV for RNW 09, witch does not exist at ENSB airport. In Fenix Navcycle, is present thought the correct ILS for RNW 09.
Could you please update?
The correct runway designators are 09/27, changed SEP 23.
MSFS runway numbering is outdated and needs correcting by ASONO.
Steve
1 Like
I don t think is an Asobo issue, because with navdata fenix, Iit gives me the correct ILS frequency in MCDU. The issue is present only when using an aircraft that has the MSFS 2020 navdata, like inibuilds A320, or FBW A320. If will be an Asonbo isuue, as you say, it will be present also with custom navdata for other aircraft. But I repeat: with Fenix, airac cycle, everithing is ok.
FYI, here are the official charts from the Norway AIP showing the new designators:
EN_AD_2_ENSB_2-1_en.pdf (414.8 KB)
EN_AD_2_ENSB_5-1_en.pdf (464.9 KB)
Are you saying the Fenix MCDU lets you select approaches for runway 10 (old designator)? This would mean the data in the Fenix is outdated.
Updating data for the Fenix is done in a separate tab in the Navigraph Hub application:
Regards,
Tim
1 Like
Hi,
Steve and Tim are absolutely right. The stock scenery in the MSFS2020 is outdated; therefore, the sim can’t assign the approach (included in the data) to the correct runway. When this happens, and the runway idents are outdated (as in this case), the MSFS turns off such terminal procedures.
That is nothing we have because we may not change runway idents on stock airports.
You can try to find a 3rd party scenery or wait until ASOBO releases a WU, which possibly corrects the runway idents.
I hope that helps
Richard
Yes, I understand, but again: why with Fenix navdata the ILS it show me correct? You say that you cannot change rnw ident, but , the scenery is the same, am I right? My question is: how with Fenix Airac cycle I get ILS rnw 9, but with Inibuilds Airac MSFS, I get only RNAV rnw 9 ? I mean: the scenery is the same, and if I have an ILS in one aircraft, then it should appear in all aircrafts . If someone that does not have Fenix, and fly the default aircraft Inibuilds A320, and pay for same Airac cycle, then you tell me that cannot have the same Cycle? The issue is from Navigraph, not MSFS. If it will be from MSFS, then all aircrafts Fenix, PMDG, Inibuids, doesn t has to have the ILS for 09. If you tell me : ok, you pay for the same Airac Navdata, but are difference from payware aircraft with the default, then I understand. But IMAO, guys, the Airac Navdata, must be the same, payware aircraft, or default. Otherwise, there is a glitch somewere in youre system. Her is Fenix approach in MCDU
The Fenix add-on uses its own database, completely independent of the MSFS logic. Therefore, you see the correct runway idents, the correct frequencies, and the correct loc idents - because we offer all this correct information. Fenix, PMDG, Maddog, Justflight, and all major add-ons use their own databases to be independent of any MSFS logic, update changes, etc.
I hope that helps and makes it clearer now.
Cheers
Richard
Ok, so Navigraph does not offer the same product for the poors guys that does not have money to buy payware aircraft, and on top of that , there are difference in the Airac cycle for MSFS. All clear now, thank you. You should warming before someone make a subscription: Be aware that are difference from payware Airac airplane and the default one. Don t try to make an ILS lapproach on certain airports with default aircrafts, because you will succseed only with an 80$ one! This is … incredible !
I was not convinced with Aviaplanner, but now guys, you make my day. Thank you again!
There is no difference.
We offer the same data in the same quality for all datasets and for MSFS, but this is an MSFS and legal limitation.
You still have the data on your system, but the MSFS doesn’t use it due to this internal limitation. Again, try to install a 3rd party scenery where the runway idents are correct, and you will immediately see the “missing” approach.
We offer it, and you still have it on your system, but the MSFS can’t handle it because the logic in the MSFS doesn’t allow it - that is nothing we have in our hands. This is an ASOBO/MS limitation/issue.
We think this “issue” is solved and explained in detail. Therefore, I close this topic.
Cheers
Richard