-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] MCDU did not show/use actual Navigraph cycle 2101 #3233
Comments
The Airac cycle that is shown in the MCDU is currently a hardcoded string by Asobo. Afaik it cannot be fixed (until Asobo brings an update) as there's no possibility to get this information inside the sim. |
Out of curiosity, why do we have the Navigraph NavData Beta program update the sim every month if the sim isn't using the newest data? Where is it going then? Not doubting you...just curious if it's not actually updating the sim's navigation data. Is the sim taking in new data for planning but simply not coding the correct AIRAC number each update?? Maybe that's why there's a monthly "small nav update" where they catch it up later?? |
Navigraph updates the actual navdata of the sim, so all your routing etc will be navigraph. The issue is that there's no way to update the navdata date displayed on the data page of the MCDU, so while the navdata updates, the date doesn't. It's only updated when Asobo update the default data in the sim. |
You were right with the second assumption. Maybe I was not clear enough :D So the data is being used, it's just this string that is only updated when MS drops their navdata update. |
Affirmative |
The issue has been solved since the latest msfs update. Just update to rev 3 2101 and it should work |
Yes, confirm that it works. |
Mod Version
{
"built": "2021-01-28T03:45:39+00:00",
"ref": "",
"sha": "",
"actor": "ZigTag [email protected]",
"event_name": "manual"
}
Describe the bug
Loaded the actual Navigraph AIRAC cycle 2101 with "NAVIGRAPH" tool into the community folder. Starting a flight, checked in MCDU the version. Showed and used (wrong STAR approach VOVLU2A at SKBQ - unknown waypoints D210F and CF05) wrong cycle 2014.
To Reproduce
Expected behavior
Fresh loaded cycle should be shown and loaded
Actual behavior
see above
References
Additional context
Was this working before/when did the issue start occurring?
Yes
Is this a problem in the vanilla unmodded game?
Don't know, did not check
Discord username (if different from GitHub):
The text was updated successfully, but these errors were encountered: