• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Not in database

Scheduled Pinned Locked Moved RJ Professional
18 Posts 11 Posters 994 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    VIZIX
    wrote on last edited by VIZIX
    #9

    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

    RhinozherousR 1 Reply Last reply
    1
  • RhinozherousR Offline
    RhinozherousR Offline
    Rhinozherous
    replied to VIZIX on last edited by
    #10

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

    1 Reply Last reply
    1
  • NorthlandAirN Offline
    NorthlandAirN Offline
    NorthlandAir
    wrote on last edited by NorthlandAir
    #11

    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.

    1 Reply Last reply
    0
  • B Offline
    B Offline
    bj777
    wrote on last edited by
    #12

    Ongoing issue! Numerous airports missing when updating Navdata to current Airac date.
    Default 2401 Airac works but it’s getting old.

    1 Reply Last reply
    0
  • MarkM Online
    MarkM Online
    Mark JF Staff
    wrote on last edited by
    #13

    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

    Just Flight Development Assistant

    1 Reply Last reply
    0
  • B bj777 referenced this topic on
  • N Offline
    N Offline
    Nodak
    wrote on last edited by
    #14

    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!

    MarkM 1 Reply Last reply
    0
  • MarkM Online
    MarkM Online
    Mark JF Staff
    replied to Nodak on last edited by
    #15

    @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

    Just Flight Development Assistant

    1 Reply Last reply
    0
  • N Offline
    N Offline
    Nodak
    wrote on last edited by
    #16

    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

    1 Reply Last reply
    1
  • MarkM Online
    MarkM Online
    Mark JF Staff
    wrote on last edited by Mark
    #17

    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:

    1. Update the navdata for the respective aircraft in the Navigraph Hub.
    2. Download the free, community created MSFSLayoutGenerator tool via the following link: https://github.com/HughesMDflyer4/MSFSLayoutGenerator
    3. Navigate to the following file directory: ...\Community\justflight-aircraft-rj (the aircraft name will vary for each product).
    4. 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.
    5. The changes will take effect the next time the simulator is launched.

    Mark - Just Flight

    Just Flight Development Assistant

    1 Reply Last reply
    -1
  • O Offline
    O Offline
    okletsgo
    wrote last edited by okletsgo
    #18

    Glad I found this post. I have been banging my head on the table trying to understand what I am doing wrong. Please fix this ASAP, it's a really awful bug.

    It has been 6 months since it was reported.....

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users