Not in database

Sneaky13

Hello! Congratulations on the release! Been loving the plane. Issue iv been having is when I click a waypoint to go direct it says not in database but I can do it on the FO side. Maybe I'm doing something wrong. Thank you!

Rhinozherous

I had a similar experience when I entered OEW (the ILS for rwy 11 in LOWW vienna) into the FIX page. It said also "Not in database".
But I did not trie it on the FO side.

TimVS

Yes this also happened to me. Entering it on the FOs side solved the problem so I imagine it is a bug

Mark

Thank you for reporting this. It's not something we have experienced during testing, so this may be specific to certain navaids and/or the navdata being used.

If the "Not In Database" message appears on the scratchpad on any future flights, could you please let us know the complete flight plan of the flight, what waypoint the message appeared with, and which navdata AIRAC cycle is being used (either the default 2301 cycle or updated via the Navigraph Hub). We'll log the "OEW" VOR as an example to investigate further.

Mark - Just Flight

Rhinozherous

@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

Sneaky13

@Mark
Flight was KMSP to KDTW

Route 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.

p919h_lm

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.

ShermheadRyder

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.

VIZIX

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

Rhinozherous

@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.