Waypoint Number / Distance not showing on HUD

[glen.a.williamson]

This may relate to another topic ( ETA and Distance Not Showing on HUD) which has already been locked and referred to the Development Team.

I was not seeing the Waypoint Number and Distance to my next waypoint on my HUD .... and ... at first, I thought I had one of the HUD Display switches in or wrong position, or perhaps the system was not working properly.  But, then I began to wonder whether I had remembered to confirm my LATITUDE, LONGITUDE, and ALTITUDE within the first two minutes of commencing the alignment of my INS.  I went back and started the mission again, doing the whole alignment process as described in Chuck's Tutorial Manual (including confirming my Lat, Long, and Alt during the start of the alignment process) .... and lo and behold ... Waypoint Number and Distance to my waypoint were now shown on my HUD and worked flawlessly. 

If anyone else is experiencing this type of problem ... I hope this info my help.

[BIGNEWY]

please include a short track replay example so we can check it. 

thanks

[glen.a.williamson]

Position NOT Confirmed during Alignment .trkPosition CONFIRMED during Alignment .trk

Edited February 24, 2022 by glen.a.williamson

[Frederf]

If during a normal align the position isn't confirmed then the alignment is 'flagged as degraded'. In real aircraft documentation that phrase is used but it's not clear what the practical effects would be. DCS's interpretation seems very clear and deliberate. My feeling is that 'flagged as degraded' doesn't have the effect we see in DCS (just some error calcs are skipped) but in no way can I prove it.

[glen.a.williamson]

Here's what Charly Owl's most excellent Viper Guide has to say on this matter ...

 ( I believe full normal alignment status may have changed since the above excerpt was written ... It may now be "10 ready" for both cases.)

But, it seems that NOT CONFIRMING your Lat, Long, and Alt at the start of your INS alignment degrades the next Waypoint Number and Distance to your next Waypoint ... and the ETA information as well.  

It seems that the issue of the "ETA and Distance Not Showing on HUD" may not be something the Development Team necessarily needs to get involved in ... it seems the problem may have simply been due to a procedural error, or oversight, by the OP.

Hope this helps. 

 

Edited February 24, 2022 by glen.a.williamson

[Frederf]

Note: altering/confirming system altitude is optional in both normal and stored alignments and is not mandatory (both real and DCS). In the real airplane entering/confirming position after the 2 minutes simply results in the alignment starting over again. Altering/confirming position during a stored alignment reverts to a BATH type alignment (typically avoided).

From what I've read failing to enter/confirm position during normal alignment should only "flag" that alignment. After every mission there are some calculated errors which are taken into account for monitoring the long term health of the INU and trimming out errors. A flagged alignment doesn't produce these results (RER and one other) which won't be counted toward the upkeep. The consequence of an alignment being flagged in the real airplane is (I think) only the absence of these performance metrics and the airplane performs normally on that mission (except for any navigation degradation due to any poor position info if any). DCS obviously doesn't have (seems intentionally so) normal mission performance when this alignment flagging occurs.

[JTFF - Raph]

Hello,

I was asking myself the same question, but i finally understood. In DCS now you have to validate your location in NORM within 2 minutes, but it's not mandatory in the case of a Stored alignment.

If you don't confirm your coordinates, you will be aligned, but it seems like the HSI and HUD have no inputs about the flight plan.

 

Kind regards,

 

Raph.

[JTFF - Raph]

@BIGNEWY

Sorry for the ping but this thread seems to be in relation with this one : 

 

 

Proof of concept here : https://www.dropbox.com/t/BMLOpihqauNaX707

My track reached 5.3MB.

Kind regards,

Raph.

[BIGNEWY]

Thanks I will revisit it in the morning. 

 

[Tom Kazansky]

On 2/24/2022 at 3:09 AM, glen.a.williamson said:

Here's what Charly Owl's most excellent Viper Guide has to say on this matter ...

 ( I believe full normal alignment status may have changed since the above excerpt was written ... It may now be "10 ready" for both cases.)

But, it seems that NOT CONFIRMING your Lat, Long, and Alt at the start of your INS alignment degrades the next Waypoint Number and Distance to your next Waypoint ... and the ETA information as well.  

It seems that the issue of the "ETA and Distance Not Showing on HUD" may not be something the Development Team necessarily needs to get involved in ... it seems the problem may have simply been due to a procedural error, or oversight, by the OP.

Hope this helps. 

 

 

Thanks! Yes, it helped me a lot to get the range to next WPT shown in the HUD.

And I bet @JTFF - Raph is absolutely right, too. My HUD looked exactly the same (like in the shown screenshot of the other thread) without confirming the LAT LONG coordinates (and ALT) while INS alignment on the ground.

Edited July 7, 2022 by Tom Kazansky