Navigraph 2503 missing airports in UNS-1
-
Hi there,
I have updated the AIRAC to 2503 via the Navigraph hub and seem to now be missing information in the UNS-1, For example YSSY, YPPH. They can not be entered in the FPL directly on the UNS-1 or if a FPL is loaded from simbrief then there are no airport details like runways, sids, stars available for them?
Hope you can assist with this.
Many thanks
Matt -
These airports and some other details have been missing for quite some time. Just Flight and Navigraph have each said they're in touch with the other about it, hopefully they find a fix soon so we can all do some Aus flying without outdated navdata!
-
Ok. Confused. If I try same thing in another aircraft, Flysimware Cessna 414 with the TDS GTNXi, which has the same AIRAC data from Navigraph the info is there. So it is not missing data in general but just missing in the F28? I can put in YSSY into the GTNXi and all the procedures etc are available.
So it seems that it is the UNS-1 that is the issue or not?
-
I don't think it's the UNS-1 per se, but something else to do with Just Flight planes (in 2024 at least) I guess, because the RJ has the same problem, in fact had it first, and that's a different FMS. If you delete the Navigraph navdata for the F28, you'll have those airports and maybe some of the missing approaches/STARs/SIDs. But since you'll then have out of date navdata, some waypoints and procedures may have changed.
There's also a (short) thread in the Navigraph forum about this, maybe if enough people add their voice we'll see a fix: https://forum.navigraph.com/t/missing-data-justflight-rj-and-f28/19008/3
-
Same issue here, no YSSY or YPPH (only ones I checked, after reading the above). Until there's a fix, I'm trying to go back to an earlier version of the NAV Data. I had to reload the aircraft to get the original, Justflight supplied navdata and now I have YSSY and will test others as time permits. One would think the navigraph data might be the issue, who knows.
-
I contacted Navigraph and they said " their nav data has these airports" and that it's an issue with the add-on, which in this case is the UNS-1 in the F28. They included limited technical information to back up their story. Something to do with the UNS-1 not reading data due to a file size issue. Basically the navigraph guy was saying, talk to Justflight.
-
Well that's less than ideal; Just Flight have said it's a Navigraph issue, and now Navigraph told you it's a Just Flight issue. When I posted on the Navigraph forums about it, their response was that they've already been in touch with Just Flight. Hopefully they get this sorted out soon, because eventually the default navdata that shipped with the F28 (and the RJ, which is a different FMS with the same issue) will start to become problematic especially on procedures. Right now I'm doing okay with the default, but when I can no longer fly current, valid approaches with charts to reference, it'll become annoying.
-
Hi all. We have been in touch with Navigraph throughout the development of our UNS-1 and GNLU custom FMS, including regarding this issue. The 2401 cycle that we include with the product, supplied by Navigraph, works fine, so we're not sure why the latest cycle is causing an issue. We're waiting for more information from their team and we'll update you on progress ASAP.
-
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-f28 (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
