Not in database
-
@Mark said in Not in database:
either
- It is also OEZ (ILS for rwy 16 in LOWW).
- "Not in Database"
- AIRAC 2411 via Navigraph Hub.
- Flightplan:
EDDK/13L PODIP4X PODIP Y867 BADGO Z850 ARPEG Z52 MASEK L604 LAMSI DCT ADLET DCT VENEN VENEN3W LOWW/16
-
@Mark
Flight was KMSP to KDTWRoute COULT7 DLL DCT PORZL RKCTY2
Navdata was 2411 through NAVHUB
Not a single waypoint would work it always would say Not in Database, but I could click each one on the FO side with no issue. Doing KDTW to KIND as we speak and so far no issues with the routing or the plane.
-
Happened with me too. KMRY to KLAS, I tried populating the fix info page with KLAS, and boom, not in database, I tried to bridge a discontinuity in legs page, tried to select first point of star by pressing the line select let, boom, not in database, tried manually typing the waypoint name and pressing in the discontinuity, same error. But after doing some random things in other pages, and came back to same page and tried again, both fix info and legs page problem went away. All of this in cpt mcdu, might have touched FO mcdu for other pages though.
Not trying to do just flight's job here, but as a software dev myself, I have a hunch that the scratch pad is sometimes not getting cleared properly and there are some invisible characters left from time to time. And when we try to use the line select keys where waypoints are involved, this issue is appearing.
-
I'd like to echo the above, this feels particularly prevalent with the fix info page. Waypoints in the route itself I've been fine with but the fix info page feels like a 50/50 chance of NOT IN DATABASE - will try to get a specific example this week.
-
Yep, same problem here. Watch the video clip below to watch me being unsuccessful at trying to go direct to a waypoint. Using the latest Navigraph nav data as of yesterday (no, I don't remember AIRAC numbers).
https://youtube.com/clip/Ugkxx1RwxriUvET1tOCoQvSsIjOkQPRQTZoE?si=pzrOAnWCP-74cg3F
-
@VIZIX said in Not in database:
Yep, same problem here. Watch the video clip below to watch me being unsuccessful at trying to go direct to a waypoint. Using the latest Navigraph nav data as of yesterday (no, I don't remember AIRAC numbers).
https://youtube.com/clip/Ugkxx1RwxriUvET1tOCoQvSsIjOkQPRQTZoE?si=pzrOAnWCP-74cg3F
Weird that it says that a waypoint - which is already in the flightplan - is "Not in Database".
Hope this gets fixed soon. -
Just got this this error morning, first time for me on the RJ85 in 2024. Using the latest Navigraph database 2502 valid from 20 Feb to 20 Mar, updated for the aircraft via the Navigraph Hub. It cannot find Sydney YSSY, so the plan is in the box up to the arrival RIVIT4, but I could not select a runway or approach into Sydney. It cannot find it from the captain's or FO's box.
My flightplan was: YMHB/30 N0414F310 LATUM2 LATUM H111 LT J22 NUNPA J163 CB W423 CULIN Y59 TARAL DCT RIVET RIVET4 YSSY/16R
Love the RJ very much, but I am very pumped up for the F28 coming soon.
Cheers.
-
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 on
-
Hi Mark, thanks for your help in other posts. I’m on Xbox, so would the same request to Navigraph for an update also be sent by them to Microsoft to include as an update in the marketplace-or is that a separate issue which needs to be addressed for Xbox users? BTW on Xbox this aircraft performs great!
-
@Nodak The navdata used in the Xbox version is the AIRAC 2401 cycle which is the default navdata that is shipped with the RJ Professional on all stores. The default AIRAC 2401 cycle shouldn't suffer from the "NOT IN DATABASE" errors discussed in this thread, as they seem to only be caused when using updated navdata installed via the Navigraph Hub.
As it's not possible for Xbox users to update the navdata in the RJ Professional, the same "NOT IN DATABASE" errors should not be present in the Xbox version.
Please let us know if you are seeing any in the Xbox version though, and we can investigate that.
Mark - Just Flight
-
HI Mark. I do have some issues regarding the database. Not many, mind you and certainly can usually do a work around. The most recent was a flight from MMMY in Mexico (Mariano Escobedo) to KCRP (Corpus Christi). The runway numbers were 1 degree off from the MS Flight Planner. I also had one waypoint which didn’t register. Using the Xbox and its limitations, I really commend all of you for a fine AC. I hope the updates will keep coming. - Gary
-
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
