Airac updates
Airac updates
One last one …would like to see regular Nav aid/ILS updates to match real world Airacs
-
Christian007
- Posts: 1
- Joined: Fri Feb 04, 2022 12:08 pm
Re: Airac updates
+1
Just failed to get airport issues with wrong LOC directions after a Navigraph AIRAC cycle update fixed with the help of the Navaids Tools (https://www.aero.sors.fr/navaids.html), needed to restore from a harddrive backup image of the P3D original version without updated AIRACS.
I had a chat with the editor of the german magazin "FS Magazin" (https://fsmagazin.de/) on the topic: He pointed me to a recent article where a real-life pilot analyzed the situation of navigation data for MSFS. The general difficulty is 1) many scenery developers unnecessarily define own navaids and do not consider that some navaids like LOC are not subject to magnetic variations as in the case of NDBs, and 2) the priorities by which navigation data is analyzed by the sim. He told me that for MSFS this issue now got fixed by changing priorities of navigation data to (highest prio at the bottom):
- Simulator airport data
- Additional airport data (e.g. Navigraph)
- Add-on airport data
- Navigation data
Maybe this is also something to consider for LM? If this got fixed, I would be happy for a patch for my P3Dv4! :-)
Just failed to get airport issues with wrong LOC directions after a Navigraph AIRAC cycle update fixed with the help of the Navaids Tools (https://www.aero.sors.fr/navaids.html), needed to restore from a harddrive backup image of the P3D original version without updated AIRACS.
I had a chat with the editor of the german magazin "FS Magazin" (https://fsmagazin.de/) on the topic: He pointed me to a recent article where a real-life pilot analyzed the situation of navigation data for MSFS. The general difficulty is 1) many scenery developers unnecessarily define own navaids and do not consider that some navaids like LOC are not subject to magnetic variations as in the case of NDBs, and 2) the priorities by which navigation data is analyzed by the sim. He told me that for MSFS this issue now got fixed by changing priorities of navigation data to (highest prio at the bottom):
- Simulator airport data
- Additional airport data (e.g. Navigraph)
- Add-on airport data
- Navigation data
Maybe this is also something to consider for LM? If this got fixed, I would be happy for a patch for my P3Dv4! :-)
