Unaligned INS affects Emergency compass but not waypoints

[CrashO]

So i'm not sure what is going on here.. but since last week, I have had several occasions (on servers like 104th and TAW) where the settings forced me to start unaligned (my preferences have always aligned enabled, but if the server forces it on me for realism, The lazy guy I am, will just takeoff with faulty navigation.

 

So, so far, everything is just as one would expect. Alignment is required by server settings, I skip it and just take-off. Taking the lack of INS precision (if any) for granted and generally having a HSI pointing 160 degrees the wrong way. No problems there :D

 

However.. in cases where I do want to navigate, I intent to use the emergency (magnetic..) compass . And what happened? It showed the same deviation the INS had.

And what makes it even more interesting, after I entered a waypoint using its coordinates (Bullseye on the screenshot). The needle on my HSI pointed straight at it when flying towards it. And while all of the instruments where telling me I was flying somewhere towards 344, right towards the bullseye. I was actually flying east (right towards the bullseye).

 

[vparez]

I encountered the same problem on Open Conflict server with the winter map; and it doesn't help to do INS alignment, the heading in both the INS instruments and the backup compass were shifted by about 90deg.

[Zeus67]

Folks, last week we discovered a DCS bug that affects the magnetic declination for compass alignment. It seems to be date based. Basically any mission that has the month of the mission date set to January (any day, any year) will experience over 100 degrees difference between true and magnetic headings.

 

There are two ways to check: set the heading to true (select Cv in the HSI) or check the date of the mission.