UpUpandAway

To further illustrate the point, see comparison below, all aircraft roughly pointing at the VOR (CTV 115.70): Fenix A320 iniBuilds A310 iniBuilds A300: The A300 RMI is off by what appears to be the airport's magnetic variation (26°W), despite the CDI on the ND actually being centered on a valid radial.

I've already used Hervé's file, no change unfortunately. Default airport. In my first screenshot, I'm 17.5 nautical miles from the station flying directly towards the airport (visually and according to FMC). Using basic trigonometry, that 26° offset on the RMI would put the station 8.5 NM away from the airport! I'm suspecting it is related to the aircraft dealing with variation or station declination, as I've experienced other variation related issues affecting the FMS: The above issue was fixed for 1.1.1, the VOR bearing/declination issue remains.

Should I report this variation anomaly elsewhere, or is it an acknowledged bug?

Unfortunately the RMI seems to be affected by variation, CTV at FACT in this example. I'm pointing straight at the station, but the needles are (about 26 degrees) off: I can further confirm this after parking on stand. The VOR is behind me, to the left: But the RMI shows it's to my right: When I enter the VOR on the PROG page, the bearing to the station is shown true, without the 26 degrees magnetic variation.

The sync doesn't seem to be importing what is shown on the METAR, including temperature.

After this morning's hotfix was downloaded, the issue is fixed, thanks!

I noticed the following in the v1.1.1 release notes: Fixed - Wrong bearings on SID (FACT RWY19 TETAN 1A SID) Unfortunately this is not the case. It appears to be a general issue, see RWY 19 OKTED 1B below: Again, I suspect it has something to do with the variation not being applied properly.

For some reason, the TETAN 1A SID off RWY 19 in Cape Town is not following runway track to 5 DME CTV as intended, but veers off to the left instead. The below screenshot shows the charted track in red: I have a suspicion the magnetic variation (26°W) might have something to do with this (similar issues at FAOR), is this an issue with the A300 or with the Navigraph data?

Could I confirm that the EFB performance pages use magnetic heading for the runway and true for the METAR? For Cape Town (magnetic variation 26 degrees West) I noticed that the true wind from the METAR is inserted into the performance page when syncing: But the runway heading is magnetic: If the EFB were comparing apples with apples, it would need to use 156/17 magnetic for the wind, or is the variation taken care of in the background?