fixed Clock time unreal.

[MicMic]

The clock shows the hour incorrectly. Only the minutes needle is on the correct position, but not the hours needle.

[razo+r]

What time is it showing? UTC or LT?

[Dragon1-1]

Most DCS modules show UTC. When someone expects LT (which, TBF, is what it'd be set to IRL), it might seem off in this exact way.

[gulredrel]

I was in NTTR map last time. ME time set to 16:30.

F1CE clock showed 12:30 at mission start.

So NTTR Nevada being UTC-7 would be okay I guess. With military coordination based on UTC time all is okay.

I would rather prefer local time, but you can set the clock, no problem.

[Lace]

ZULU is standard for most ops.  You could be coordinating with units outside the immediate area, or even within the AO.  For example, Turkey is Z+2, Iraq Z+3, Iran Z+3.5.  There is usually enough going on without wondering what time it is.

[Vibora]

Most, if not all, DCS modules use local time. And so we do as well. We'll probably add an option to choose between LT or UTC.

If you have other time set please add a capture, video recording or very short trk, notifying DCS version used.

[gulredrel]

18 hours ago, Vibora said:

Most, if not all, DCS modules use local time. And so we do as well. We'll probably add an option to choose between LT or UTC.

If you have other time set please add a capture, video recording or very short trk, notifying DCS version used.

Hi @Vibora,

new mission Nevada Nellis AFB. ME set to 16:30 (4:30PM). The clock in the F1CE cockpit shows 12:30 track attached, and screenshot here:

2023-07-09 11:36:53.590 INFO    APP (Main): Command line: "E:\games\DCS_World_OpenBeta\bin-mt\DCS.exe" 
2023-07-09 11:36:53.590 INFO    APP (Main): DCS/2.8.6.41363

google states Las Vegas time: "Current Offset:UTC/GMT -7 hours"

So even 12:30 AM would be wrong in the example above if the clock is showing UTC, this would be 11:30. But this may be something with daylight saving times and so on.

Thanks

Jens

F1CE_Nellis_AFB_Nevada_clock_1230_vs_mission_1630LT.trk

[Vibora]

AFK. Is it a MP mission?

[gulredrel]

4 hours ago, Vibora said:

AFK. Is it a MP mission?

No, totally new simple single player mission. ME, new mission - map Nevada - F1CE player aircraft ramp start cold and dark - select time in ME and fly. Nothing special.

Edit: mmhh... tried the same in Kobuleti:

and Akrotiri:

 

ME time set to 16:30. The clock in cockpit always shows 12:30.

Just speculating: The time the clock shows is UTC, but based on UTC+4 offset in Caucasus regardless of the map?

So 16:30 Kobuleti local time translates to 12:30 PM UTC?

I'm sure you will find the answer in the code

F1CE_Akrotiri_Syria_clock_1230_vs_mission_1630LT.trk F1CE_Kobuleti_Caucasus_clock_1230_vs_mission_1630LT.trk

Edited July 9, 2023 by gulredrel

[MicMic]

The clock works properly at AM local time, but with time at PM the hours needle starts at 12.

Persian Gulf 06:05

11:05

16:05

 

Edited July 11, 2023 by MicMic

[Vibora]

Fixed. Thank you all for your reports.

It will be included in next OB updated.

Edited July 11, 2023 by Vibora

[Caldero]

For anyone interested in the F1 clock, there is an excellent article in the web:

https://www.hablemosderelojes.com/t/el-mirage-f1-y-su-dodane-type-11/230898

And a bonus F1M cockpit picture

Regards

Edited July 12, 2023 by Caldero

[gulredrel]

On 7/11/2023 at 12:49 PM, Vibora said:

Fixed. Thank you all for your reports.

It will be included in next OB updated.

 

Last weeks changelog stated: "Fixed the initialization of the mechanical clock hours hand when the aircraft start time is more than 12:00 PM."

@Vibora Just started a mission with OB 2.8.7.42718 MT (at least DCS log is showing this information, I also deleted fxo and metashaders after updating) and mission time is 19:00 in Caucasus and the clock shows 12:00. How can I confirm that I really have the latest files? Could run repair. Anyone else seeing weird results?

[gulredrel]

*bump* Now I created some tracks which show the wrong time when mission time is set in the afternoon.

Was in OB, but this currently should be the same as stable.

Tested both F1CE and F1EE single and multithreaded DCS version 2.8.7.42718.

When mission time is set to 08:13 local time, cockpit clock is okay.

But setting an afternoon time like 20:13 local time, hour hand is at 12 o'clock position showing 12:13 here in the example:

F1CE_Kobuleti_clock_1213_and_mission_2013.trk F1EE_Kobuleti_clock_1213_and_mission_2013.trk F1EE_Kobuleti_clock_0813_and_mission_0813.trk

F1EE_Kobuleti_clock_1223_and_mission_2023_DCS_single_thread.trk

Edited August 5, 2023 by gulredrel
added info about ST / MT DCS version 2.8.7.42718

[gulredrel]

Thanks @Vibora and @fausete, fixed now in 2.8.8 OB

[Vibora]

You're welcome.