msfs2020-go
msfs2020-go copied to clipboard
Heading shown on Map is up to 12 degrees higher than MSFS2020 display? Every other number is right on!
At least 18 ('cause I just looked lol). Magnetic bearing vs. true bearing?
yea, it's true and not magnetic https://github.com/lian/msfs2020-go/blob/master/vfrmap/main.go#L30
think we should switch to magnetic instead? or show both?
Both would be fine with me.
Get Outlook for Androidhttps://aka.ms/ghei36
From: lian [email protected] Sent: Sunday, September 13, 2020 5:00:11 PM To: lian/msfs2020-go [email protected] Cc: BistroAir [email protected]; Author [email protected] Subject: Re: [lian/msfs2020-go] Heading shown on Map is up to 12 degrees higher than MSFS2020 display? Every other number is right on! (#42)
yea, it's true and not magnetic https://github.com/lian/msfs2020-go/blob/master/vfrmap/main.go#L30
think we should switch to magnetic instead? or show both?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lian/msfs2020-go/issues/42#issuecomment-691744810, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ4JZAJSYAYJFXF7DSIAB7DSFVMIXANCNFSM4RK4IZGQ.
going into next release then :+1:
Thank you
Get Outlook for Androidhttps://aka.ms/ghei36
From: lian [email protected] Sent: Monday, September 14, 2020 4:25:21 PM To: lian/msfs2020-go [email protected] Cc: BistroAir [email protected]; Author [email protected] Subject: Re: [lian/msfs2020-go] Heading shown on Map is up to 12 degrees higher than MSFS2020 display? Every other number is right on! (#42)
going into next release then 👍
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lian/msfs2020-go/issues/42#issuecomment-692370318, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQ4JZAKSWQSTR6JGSJ5XWTDSF2Q6DANCNFSM4RK4IZGQ.
Any updates on this as makes it a bit hard when the heading is off from what's expected. Otherwise a very helpful app!
Same as Issue #68 above. Was this eventually corrected? I'm using the latest version and still see the same problem.