Latest Navigraph Update for RJ - no YSSY??
-
Thanks for reporting this. Looking into this, it appears to be an issue affecting several airports specifically with the 2412 navdata. The same airports can be entered into the FMS with no issues using the default 2401 navdata.
We will raise this with our contacts at Navigraph to investigate further. In the meantime, the default 2401 navdata will allow you to enter airports such as YSSY into the FMS without issues. To revert to the default 2401 navdata, this will require a reinstall the RJ Professional.
Mark - Just Flight
-
As far as I know Navigraph fixed this some releases ago. I do not experience it with the RJ currently.
-
I had accidentally reinstalled the Navigraph data to the RJ a couple weeks ago, and I forgot to go double check. So just now I loaded in at YPPH Perth, which is where I first noted the issue, and ascertained that neither YPPH nor YSSY are in the database. It's a shame, because the RJ is the only fully-functional, non-bug-infested airliner I have in the sim, so I'd love to have all the navigation data loaded into it!
Edit: Thankfully, the 2020 version of the RJ doesn't have this navdata problem, so I can do all the Australia flying I want in that sim.
-
Hi all,
Just to let you know that we haven't forgotten about this, and we have contacted Navigraph several times about this. Unfortunately, as we aren't the supplier of the navdata there isn't much we can do apart from recommending that you switch back to the default AIRAC 2401 navdata if you run into this issue.
Mark - Just Flight
-
B bj777 referenced this topic
-
Hi all,
To provide an update on this, Navigraph have kindly been looking into this and they have found that the root cause of the navdata issue is due to differences in how MSFS 2024 handles aircraft packages compared to MSFS 2020. Essentially, whenever a file in an MSFS 2024 aircraft package is updated, that change must also be reflected in the package's layout.json file. This is very strictly enforced in MSFS 2024, so much so that even a small change in file size caused by a change in navdata is preventing the WASM gauge from reading data past a certain point in the file. MSFS 2020 aircraft packages are much more lenient in this regard, with small changes to file sizes being possible without updating the layout.json, hence why this has never been raised as an issue prior to the product(s) becoming MSFS 2024 compatible.
There are some changes we can make on our side that will permanently work around this issue, and those will be included in the next update to the affected aircraft.
In the mean time, for users who would like to use updated navdata in our MSFS 2024 compatible products we recommend the following steps:
- Update the navdata for the respective aircraft in the Navigraph Hub.
- Download the free, community created MSFSLayoutGenerator tool via the following link: https://github.com/HughesMDflyer4/MSFSLayoutGenerator
- Navigate to the following file directory: ...\Community\justflight-aircraft-rj (the aircraft name will vary for each product).
- Drag and drop the "layout.json" file into the MSFSLayoutGenerator.exe. The Date Modified filed of the layout.json will update once the file has updated successfully.
- The changes will take effect the next time the simulator is launched.
Mark - Just Flight
-
Thanks, Mark - appreciate the workaround.
