Flight plan shows bearing and distance relative to current position, not flight leg

[Ramsay]

I don't own the NS430 module yet but it seems the flight plan page displays waypoint bearings and distances relative to the current position, not the flight leg.

 

Here Anapa Rwy 22 Departure via TUNOT 3 has been selected, the last leg of the flight to TUNOT should be 121° for approx. 27 km (15 nm).

 

DCS NS430 shows the leg to TUNOT as 167° for 17.8 nm

 

 

rather than flight leg bearing and distance as found in Garmin's training simulator

 

 

Although DCS and the real departure charts are unlikely to be 1:1, it looks like an error?

 

Source Video:

 

Edit: Reviewing the video, it's possible, he selected departure TUNOT 1A or 1B which may be closer in bearing/distance but shouldn't his departure runway switch to 04 ?

 

It's probably impossible to report flight plan bugs if there are no published charts and DCS differs significantly from the real ?

Edited September 9, 2017 by Ramsay

[gospadin]

I reported the DTK/DIS errors with flight plans, since DTK should always represent the waypoint-to-waypoint track and DIS should represent leg distance (with the exception of the currently active leg destination)

 

Regarding the procedures itself, it seems that the RWY22 TUNOT3 departure indicates a standard rate turn at 10 DME from the end of the runway, followed by a flight track of 121 for 15nm. With the garmin sim, you can see these two segments are disconnected. In game, I am getting 132 for 17nm. This would appear to be the direct track assuming no implied position change in the turn. I don't know if they plan to implement that in their embedded procedures, but I'll report that too.

Edited September 13, 2017 by gospadin

[gospadin]

Okay, reported the procedure bug specifically. It seems to affect any procedures with disjointed flight segments connected by standard rate turns.

Edited September 13, 2017 by gospadin