reported Track/Desired Track/Bearing not working correctly?

[lmp]

I was flying to a waypoint with a desired track of 288. I drifted slightly off course - the virtual CDI "needle" went left and the bearing changed to 287. So far so good. I turned to track 286 (according to the GPS display) to get back on DT. At this point I was expecting the bearing to come up to 288 but it continued to drop to 286. I turned to track 284, the bearing to waypoint continued going down. I had to make a much coarser correction to get back on DT. Once I managed that, I carefully turned back to track 288 and quickly started to go off course according to the GPS.

 

In the map view, it looked like I had to be tracking several degrees to the left of the flight plan leg in order to stay on DT.

 

The entire time I was using only the GPS track/bearing/DT indications, ignoring the gyrocompass.

[heloguy]

Is there wind in the mission? A crosswind will cause you to have a different heading than your desired track in order to hold that track.

[lmp]

There was, but the GPS is not showing heading - it's showing track. It has in fact no way to get any heading information. It can only determine where the helicopter is going, not where it's pointing - the opposite of what a compass can do.

 

EDIT: However, if the GPS was erroneously showing heading instead of track, that might be the source of the problem. I'll look into it at home.

Edited October 2, 2017 by lmp

[gospadin]

It is erroneously showing heading. I will make sure that's properly reported (I had thought it was, but now I am not sure, and I cannot access the bug DB while at work)

[GUMAR]

It is erroneously showing heading. I will make sure that's properly reported (I had thought it was, but now I am not sure, and I cannot access the bug DB while at work)

Same report was in russian thread. Definitely - bug. Reported.

[Tippis]

Bumping this because I was playing around with the Yak-52 and its ARK navigation wasn't working so I tried using the NS430 instead… and ended up flying in pretty silly circles.

 

Some experimentation made me eventually find the right track to fly to get to where I wanted.

 

It looks like, quite simply, the TRK is using some kind of misapplied true heading rather than magnetic. The attached image shows me flying pretty much dead straight and true towards Gelendzhik (mag.var +6.3°). Flying at a 283–284° indicated track would keep me right on top of the desired track of 291° and with a constant bearing towards the nav point (everything with a ±1° rounding margin of error).

 

 

So the bug is still around 10 months later, and looks like it's mainly a superfluous addition or subtraction at some point.

[Ramsay]

Bumping this as I've just picked up the NS430 on steam and test flown a couple of F-5 flight plans that I've already planned/flown manually.

 

TL;DR:

Desired Track Caucasus

• Desired track bearings are out by ~6° in the Caucasus. Ground track is correct.

• Desired track bearings are correct in Nevada

 

Map

• Map objects and track are offset to the right (MagVar ?) in both Caucasus and Nevada theaters.

 

Details:

Checking a flight plan from Batumi (UGSB) to Tbilisi-Lochini (UGTB) using the F10 map ruler

 

Batumi to Tbilisi-Lochini = 81°T for 151 nm

 

 

Using the 'Direct To' function, the NS430 gave

 

 

UGTB = 81°M for 150 nm (changing "Aux>Page 3> Units / Mag Var" to True, adds +6 i.e. 87°T)

 

To follow the desired track I flew approx 75°M using the F-5 HSI, the NS430 confirmed the 75°M ground track, however although the HSI/TACAN showed Tbilisi directly ahead, the NS430 always showed the desired route/Tbilisi approx 6° to the right.

 

 

Tested DCS Open Beta 2.5.3.21235

 

Mag Var as measured by a Gazelle NADIR at Batumi was +6°36' (+6.60°)

 

Edited May 24, 2021 by Ramsay
Fix formatting following migration to new forum

[Ramsay]

Testing in the AV-8B confirmed the problem.

 

The incorrect Desired Track only effects the Caucasus map, track headings were correct in Nevada.

 

The misaligned NS430 map is similar to the AV-8B's misaligned ground track when using Magnetic Bearings.

 

However unlike the AV-8B, the misalignment is not corrected by switching to True bearings.

 

Hopefully this will give sufficient detail to fix the Desired Track issue in the Caucasus and perhaps the misaligned map.

 

Tested Open Beta 2.5.3.21235

 

Mag Var as measured by a Gazelle NADIR:

Nellis = +11°35' (+11.58°)

Batumi = +6°36' (+6.60°)

 

 

 

 

AV8B_Landing_Batumi.mi

AV8B NS430 TACAN-ILS Test, Nellis.miz

Edited May 24, 2021 by Ramsay
Fix picture formatting

[canned_fire]

ED,

 

I was happily surprised with the 2.7 clouds. So I purchased the GPS and and got disappointed that this bug from 2017 is still present (or maybe it went away and came back I don't know). 

 

Anyway, as already reported, the DTK and BRG are being displayed in True Heading, instead of Magnetic Heading. TRK is OK in Magnetic Heading. The difference is about 6 degrees which makes me think it is a mix up in the magnetic deviation (Caucasus map). Could you please take a look at this?

 

[bertOC]

Can confirm, even tho the heading is set to magnetic in the NS430's settings page, it's showing true heading in the default nav page.

Changing the setting to true heading will change the heading shown to true heading + magnetic deviation, so a complete nonsense number.

 

A fix would be much appreciated...

[v81]

Coming up to a 5 year anniversary on this ED.

8 Years on the Mi8 hardpoints bug.

Can we get a real bug tracker yet and start getting these triaged?

It's starting to look grossly unprofessional from the point of view of a paying customer.

It's a complex product and i don't expect instantaneous fixes or perfection, but you have admit this is getting silly.

[Flappie]

This should now be fixed. Can someone please confirm?

Quote

• Fixed. MAGNETIC heading is stored as TRUE heading

 

[Sobakopes]

В 19.12.2023 в 23:59, Flappie сказал:

This should now be fixed. Can someone please confirm?

 

Nope.

On caucus it works well.

On Syria magnetic headings are different for f10 and ns430.

F10 - 7 degrees = ns430

 

https://forum.dcs.world/topic/73024-bagi-dcs-world/?do=findComment&comment=5364577

Edited January 11, 2024 by Sobakopes

[Flappie]

I thought the problem would only happen over Caucasus.

Thank you for the link. I'll check.

[Flappie]

I've just checked every single terrain and this is what I get when I'm facing my next waypoint:

Terrain	Cauc.	S.A.	Kola	Marianas	NTTR	Normandy	P.Gulf	Sinai	Syria	Channel
F10 (mag)	67	281	205	68	79	90	77	11	241	87
TRK (mag)	67	281	204	67	79	89	76	11	241	86
DTK (mag)	66	278	195	66	68	92	73	6	234	---
BRG (mag)	66	278	195	66	68	92	73	6	234	---

1. I'm not sure why I got no DRK/BRG over the Channel (year is 2016). Is that a bug?

2. Can someone please tell me if the readings were OK for all other terrains prior to the Caucasus fix?

(I assume Marianas looks of because of the very small magnetic declination)

[Flappie]

The issue is reported (again), this time for all terrains.