Since that always is the most up to date value based on the newest available Magvar models The Magnetic value would then be the result of True + Magdec.bgl. Then we might see again small differences to charts but those are negligible compared to bad autopilot behavior.
#LOCALIZER COURSE SYMBOL CODE#
The best way would be, if Asobo would go back to the old FSX/P3D way and code Localizers only with the true value (same as currently RWY) and do the Magnetic Autotuning based on the True + Magdec.bgl value. (The airplane cannot fly the localizer properly if the CRS on the CDU NAV RAD page is set incorrectly) To compensate for this, we recommend setting this option to ON, and we will read the appropriate P3D localizer course and adjust the setting for you, thus saving you time and frustration." Since many users are also using real-world navigation charts, this can create some confusion and can also create problems if the LOC course is not correctly set to match the P3D hard-coded information. The end result is that the localizer final approach course in the P3D world will sometimes vary from the real world. "CORRECT LOC CRS TO P3D: When it comes to navigation data, P3D has an inherent weakness in that data related to ILS/LOC stations is hard coded into the simulator and is not updated to keep it current with the normal magnetic shift.
This is also one of the reason why PMDG did is as follows when tuning the Inbound CRS for P3D: If the calculated RWY Heading (True + Magdec.bgl) and the Autotuned course differ, it may result in negative consequences when it comes to Autoland behavior of several aircrafts as the Autopilot tries to correct against an imaginable crosswind which is not there. The coded Inbound CRS is on top used for the Autotuning of the Inbound course. To get a properly aligned Localizer on extended MSFS centerline, the combination of coded Magvar and Inbound CRS in the Localizer definition must always match the exact RWY true of MSFS. MSFS at the moment replicates how Localizers are stored in ARINC 424 files (True + Magvar + Magnetic Inbound CRS) with all its bad consequences for the MSFS environment.
0 kommentar(er)
