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?
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…
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”.
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.
I try to fly to ENOV Hovden (Norwegian Town) and I have installed Navigraph last cycle. The ATR don’t find any STAR or Approach. The Asobo Vision Jet with G1000 find it. What is wrong ???
Generally I just don’t recommend using the Navigraph navdata overwrite - seems to cause more issues than it solves. Virtually every problem in this thread related to navdata is nonexistent if you’re using default navdata.
Found the Problem: Not Navigraph is the Problem. I have an FS2000 Addon Airport from Aerosoft. If I disable this Addon, STAR/Approach was found. I wonder, that it works with the Vision Jet ? It also uses the MS Database. ???
The gold standard seems to cause more issues than it fixes when it’s applied to aircraft that already use the default navdata which even Navdata themselves have said is functionally identical to their own.
