[msfs2024] atr 42-600 / 72-600

I am experiencing navigation issues with the ATR 72-600 in MSFS 2024.

On the MCDU NAV DATA page, the aircraft shows:

STD DATA: MSFSNAVDB – CURRENT
MSFSNAVDB – PREVIOUS

However, some SID/STAR/RNAV procedures and/or waypoints appear to be outdated or incorrect. The aircraft also sometimes has problems sequencing legs and making turns correctly in LNAV/NAV mode.

I would like to clarify whether the ATR 72-600 is actually using the latest MSFS 2024 navigation database, and whether the ATR currently supports the latest Navigraph AIRAC data.

Is MSFSNAVDB – CURRENT expected to contain the latest AIRAC available in MSFS 2024?

Could this be a problem with the ATR’s FMS/navdata implementation rather than the MSFS navigation database itself?

It uses the latest internal MSFS nav database, the info about cycle in FMS is fake/hardcoded.

1 Like

Can you provide some specific examples where the navdata seems incorrect or incomplete?

In today’s Dev Update, it was stated that Hans is working on updates. So there will be further updates. Timing is unknown.

5 Likes

Sorry for delay. I just waited for another moment to get that situation. So it happend in LGTS airport when arriving from LGAV.

Are you using 3rd party LGTS? If so try to reproduce with stock one - it should work fine. 3rd party scenery devs seem to break msfs built in nav data in some of their products, Greece area is very good example of at least a few I am aware of that publish airports that have completely broken approaches whereas the stock airports work fine. Go figure… or stop buying broken products…

1 Like

Totally agree to pwnek, had this for Mykonos for example! For me it always helps moving the scenery itself up in the ordering within the package reorder tool which you can access in the Developer Mode. Search Google for “package reorder tool MSFS24”.

1 Like

I used airport version from 2020, but play in 2024. I used free version from flightsim. Dev wrote: “There are no SIDs/STARs for RWY 10/28 as the SDK is still very limiting in terms of NavData.” Yes, that version conflict could be the reason. Thanks!

FYI: I managed to get the FTSim soundpack working with the native 2024 ATR:

  • Move the files into: <addon-folder>\simobjects\Airplanes\microsoft_atr\common\sound\ (or \common\config\ for aircraft.cfg overrides) — path matters, root-level did NOT work.
  • Update layout.json accordingly.

Some sounds don’t get triggered correctly (likely due to node name differences between the 2020 and 2024 models) — the one I’ve noticed so far is the stab trim horn. Works well otherwise, engine sound is clearly updated.

Its just for me or the nose wheel dont turn in the external view?

I really like to put external view to admire the plane during taxi, but the noose whell almost not turning with full rudder or tiller, is really anoying, maybe not so dificult to fix this for the next update.

A post was split to a new topic: [ATR 72-600] How to read FMS Transition Altitude externally with SPAD.neXt?