[RESOLVED] Clock stuck at 12:00 when Zulu time is the day before local time

[Steph21]

Noticed on release (not sure if it was working before last update) and checked only on Caucasus

If in a mission, local time set make the zulu time being on the day before, clock in the cockpit will indicate 12:00 and needles won't move.

 

Example on caucasus:

Set local time between 01/06/09 00.00 and 01/06/09 03:59, then Zulu time will be between 31/05/09 21:00 and 31/05/09 23:59. Clock will then display 12:00 and needles won't moved instead of displaying Zulu Time

 

If local time is set to 01/06/09 04:30 for example, then Zulu time will be 01/06/09 00:30 and clock will display Zulu time correctly.

 

To sum up, if local time and zulu time are not on the same date, clock won't display Zulu time but 12:00 and needles won't move

If Zulu time and local time are on the same date, then it works fine

 

To be confirmed on other maps...

Edited July 8, 2019 by Steph21

[Steph21]

Up

Still not working on latest release

[Steph21]

Issue is still here on latest open Beta

here is a track file showing the issue in a mission on Caucasus with start time set at 03:59:00 am Local time (23:59:00 Zulu time the day before).

Clock stays stuck at 00:00:00 (Zulu time) until 04:00:00 am local time (00:00:00 Zulu time the same day as local time), then seconds needle start moving and clock displays current Zulu time

Clock bug Zulu_Local time.trk

[myHelljumper]

Can confirm.

[RAZBAM_ELMO]

If still an issue please update with a current OB version thanks

[Steph21]

Still an issue on latest OB

New track attached

Clock bug Zulu_Local time.trk

[RAZBAM_ELMO]

Issue resolved in latest patch. Check patch notes. Marking as RESOLVED and moving to RESOLVED.