Jump to content

Time On Target gets dropped when time passes through 00:00z


Recommended Posts

Not sure if this is how it's meant to operate or a bug, but I have experienced the following behavior.

 

If the current time is prior to midnight zulu, (such as 23:50:00z), and you set a time on target for a future waypoint that is beyond midnight zulu (such as 00:05:00z), it requires the time to be incorrectly entered as 24:05:00z for the system to give correct speed indications.

 

However, once the actual time passes 00:00:00z, this become invalid, and no longer provides correct speed indications. The time on target then needs to be changes from 24:05:00 to 00:05:00 to work correctly.

 

NATOPS paragraph 24.2.5.3 states valid TOT inputs as 00:00:00 to 23:59:59, so my guess is this is a bug simply due to the calculations not continuing smoothly through midnight zulu. It therefore thinks 00:05:00 is actually in the past up until 23:59:59, hence the need to use 24:05:00 instead, until the actual time has passed midnight.

 

A lot of number in my explanation, but I hope that makes sense.


Edited by norman99
  • Like 2
Link to post
Share on other sites

Reproduced. Track attached.

FA-18C_TOT_midnight_ZULU bug.trk

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

1197644828_Screen_200911_044202-Copy.png.74d8c09ee9060cffd7408a75ab2c13ef.png

Z370 Aorus Gaming 7, i7-8700K, 3090 FTW3 Ultra, 32GB DDR4, 960 Pro, 970 Evo Plus, WD Gold 6TB, Seasonic Prime Platinum

F/A-18C, AV-8B, JF-17, A-10C (C II), M-2000C, F-16C, F-14, BS2, UH-1H, P-51D, Sptifire, FC3

Link to post
Share on other sites
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...