[REPORTED] NSEQ CS/T behaviour

[lukeXIII]

Attempting to fly a TOT or TTT with a non-sequential route is causing issues with the Command Speed where it instantly drops after selecting the next waypoint in the route and progressively increases until the next waypoint is reached. This happens until the final waypoint is selected.

To show this I made two flight plans which are 100 nm from the initial aircraft position to the final waypoint. The single waypoint plan is used as a reference for what the CS/T should be. Initial time was 04:00:00 and TOT was set to 04:15:00. For reference the CS/T from the single waypoint flight plan was around 362 KCAS.

• Initial position to WP1: CS/T was around 360 KCAS and didn't change (consistent with the reference speed)
• WP1 -> WP2:  CS/T instantly dropped to 310 KCAS on selecting WP2 and progressively increased to 370 KCAS as aircraft approached WP2
• WP2 -> WP3:  CS/T instantly dropped to 290 KCAS on selecting WP3 and progressively increased to 402 KCAS as aircraft approached WP3
• WP3 -> WP4:  CS/T stayed at 413 KCAS

 

Some other observations whilst testing this:

• SEQ route not functioning
• NSEQ route includes waypoint before first waypoint in the ingress string e.g selecting an ingress string of W3-W4-W5 will also include W2
• Selecting TTT does not show the time-to-target counting down on the UFC
• Timer does not count down on CS/T display

 

 

NSEQ_test.trk NSEQ_test.miz

[gulredrel]

Bump... I had problems even getting a route line to work.

Looked pretty strange to me. After fiddeling around setting, deleting, resetting things on the ODU, I ended with a CTD

dcs.log-20220623-180853.zip

Edited June 23, 2022 by gulredrel

[lukeXIII]

After some more testing I'm fairly confident that the extra waypoint that gets added is what's causing all the issues. 

[CornAddict]

Might be worth posting in the Razbam discord.

[AlphaJuliet]

Issue confirmed and reported, thanks for the report and track.

Cheers,

A.J.