Yes, we just reverted while we check to see what’s causing this. Thanks for your patience.
Preliminary investigation seem to indicate that this is not related to the recently released MSFS version 184.108.40.206.
More info to follow…
Thanks for the rollback.
Hope you can get it fixed without too much troubles …
In the small text MSFS is giving together with the update, it refers to the FMS Data of Navigraph:
A small update is available today - This corresponds to the AIRAC cycle being updated with new navdata (Cycle 13)
More information here: https://navigraph.com/products/fmsdata
So did Navigraph now deliver the airac data directly to MSFS?
No we don’t deliver data directly to MSFS, so not sure what he means unless it is just a loose reference to our AIRAC cycle release table on that link.
In addition, it doesn’t seem like the MSFS default navdata was updated with the most recent patch today.
No, we are still delivering navdata to FS2020 separately via our Microsoft Flight Simulator Navdata Update Service which you can find here: Navigraph Navdata Beta
Thanks, I thought so… I think they just refer indeed to the table on your site with release data of the cycles. But good that they give a little but extra attention to Navigraph
Interesting, could you elaborate more? Asobo devs specifically state that it is the navdata update, and people on the official forums checked the diffs and deduced that there was a navdata update even before the official announcements.
Thanks for your work on getting the CTD problem fixed, btw!
The date/time stamps on the BGL files in fs-base and fs-base-nav all changed after applying the 1GB patch that was downloaded on launch of MSFS today. That doesn’t necessarily mean that the data in the files are new of course.
I am still seeing 8-year-old obsolete approach data for ILS 06 at my home airport KELM using NavBlue default nav data. It has been that way since MSFS launch in August despite several updates of the core nav data since then. The other 5 existing approaches at the airport don’t even show at all in MSFS default, which has also been the case since launch.
Navigraph is 100 accurate for the same airport. All approaches are present, and all are current.
I haven’t made any extensive tests, but when planning a flight out of LZTT this morning I noticed that the world map still showed e.g. MARK4C and EPED4B departures which have been replaced by MARK5C and EPED5B respectively in 2013. Again, no extensive testing and could be a local data issue on my system, but it was my initial reflection.
Yeah, either Navblue or Asobo aren’t interpreting the data correctly, it seems.
Should we uninstall for the time being not to cause conflicts with Asobo’s update they pushed today?
Should we stick to 2012 accross the board for now for MSF2020?
Probably depends on what you mean by “across the board”. AFAIK, using Navigraph Charts it doesn’t let you select a cycle. If you mean things like Simbrief, then probably a good idea to wait, yeah.
Gotcha yes it’s what I meant thank you!
I reverted simbrief to 2012 to match my ingame AIRAC.
navigraph charts is 2013 but I’m only using it to double check.
I don’t think it’s a case of incorrect interpretation. The simple fact is that the data supplied to Asobo by NavBlue is, in many cases, woefully out-of-date. I reported the obsolete approach data for my home airport KELM directly to NavBlue themselves back in September. They verified the problem, and said that the database would be updated with the AIRAC release in early September. But, it has not been updated in MSFS, despite several sim nav data updates since then.
I have to wonder if NavBlue is actually updating anything. It almost appears that they just give Asobo the same database over and over again with each cycle. The outdated LZTT SIDS are a good example.
If so, then Asobo should definitely stop using them. I’m not sure what they are paying them, but if it’s over $1000, then that’s too much for outdated data. (Apologies if being unkind to companies isn’t allowed…)
I think you are talking about things that you have absolutely no information about
This is not the topic of this thread. please stop posting to discuss this kind of things. there is numerous discord/facebook groups/reddit feeds where you can spread your conspiracy.
I’m just interested by this issue resolution.
WTF??? Unkind words right back at you, buddy. Buh bye.
Alright @TransPacificMediator stay on topic. @ticktouktack has a point - this thread is about resolving the issue. Let’s stick to what we know. I am sure Asobo has good judgement and the intention of the best possible customer satisfaction behind their decisions. Let’s take a 10 min breather and start fresh, ok? Give everyone the benefit of a doubt and that we all mean well.