Jump to content

Track line always indicating 10 degr left of heading, no matter what the wind is, on NORMANDY map


Recommended Posts

Hi Razbam, 

 

Just want to report an issue I found on the Normandy map. The track line on the EHSD is always indicating 10 degrees left of my heading, no matter what the actual wind is. I have tried this with  no winds, strong winds, changing dates, changing from magnetic to true but the track line remains in the 11 (ish) o'clock position on the EHSD.  I think the post below (about Nevada HUD issue) has some screenshots where the trackline is 10 degrees to the right of the actual heading, this is the same problem except it's to the right, instead of left.  This does not occur on the Caucasus map. 

 

Please find attached the track file where before take off, the track line indicates 350 degrees. As soon as I take off it indicates 10 left of my heading. The wind is from the south, the ghost vector is working as expected but the EHSD trackline is not. I turned on to a heading of 180 degrees (straight into a headwind, no drift) and yet the trackline says 170. I turn to 090, wind from the right, track indicates 080 degrees. I turn north , tailwind with no drift, track says 350 degrees but my actual real track is 360 degrees.  

AV8Bweird trackline.trk


Edited by Bbow
Link to post
Share on other sites
  • Bbow changed the title to Track line always indicating 10 degr left of heading, no matter what the wind is, on NORMANDY map

Mag variation in Normandy is 0. Plus, variation has nothing to do with the track line, or better to say...in real life it doesn't affect track. In DCS however...who knows, could be some weird bug. 

Link to post
Share on other sites
2 hours ago, tea_cypher said:

Sounds like magnetic deviation to me.

 

I confirm there's a large (~10°) error in the AV-8B's EHSD ground track on the Normandy map when using magnetic bearings.

 

gdhGUEp.jpg

 

Switching MapM to TRUE is boxed fixed it for 21 June 2016 (MV = W 0.7° both historically and in the A-10C).

The magnetic variation (both historically and as measured by the AV-8B) is not large enough to cause the error.


Edited by Ramsay
  • Confused 1

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites

This is weird...have you tried it with wind though?  

I have another bug with TCN offset waypoints but that will need to be another bug thread. 

Link to post
Share on other sites
Just now, Bbow said:

This is weird...have you tried it with wind though?  

No, I just did a quick sanity check with the default time and weather.

i9 9900K @4.7GHz, 32GB DDR4, RTX2070 Super 8GB, 1TB NVMe, 6+4TB HD, 1+1TB SSD, MSFFB2 joystick, X52 Pro Throttle, TIR5, Win 10 Pro x64, 1920X1080

Link to post
Share on other sites
1 hour ago, Ramsay said:

No, I just did a quick sanity check with the default time and weather.

Thanks for doing that, the screenshots are great to illustrate the issue. I'll have another play with it later. 

Link to post
Share on other sites

Tried it last night and you are right Ramsay, switching to TRUE fixed the trackline issue. Thanks for your help.

 

The trackline indicates drift correctly when TRUE is switched on, it's not the way it should work but it's a good tempo fix because the variation is so small in Normandy. 

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...