Silent Film Posted Saturday at 08:52 PM Posted Saturday at 08:52 PM The clock in the cockpit is 3 hours early. For example, when it is 7 PM, the clock shows 4 PM.
Galinette Posted Sunday at 06:52 AM Posted Sunday at 06:52 AM It's UTC, and you can also adjust the time yourself 2
Silent Film Posted yesterday at 09:06 AM Author Posted yesterday at 09:06 AM On 5/11/2025 at 8:52 AM, Galinette said: It's UTC, and you can also adjust the time yourself There is no reason whatsoever that the clock in the cockpit should be automatically adjusted to the Greenwich time and not the time in the mission.
ED Team BIGNEWY Posted yesterday at 09:08 AM ED Team Posted yesterday at 09:08 AM Just now, Silent Film said: There is no reason whatsoever that the clock in the cockpit should be automatically adjusted to the Greenwich time and not the time in the mission. Hi, GMT / UTC is also the same as ZULU which is the NATO standard time used for the military. Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
razo+r Posted yesterday at 09:30 AM Posted yesterday at 09:30 AM (edited) 28 minutes ago, Silent Film said: There is no reason whatsoever that the clock in the cockpit should be automatically adjusted to the Greenwich time and not the time in the mission. There is no reason to use local time, UTZ/Zulu time is basically the only used time in aviation. Imagine having to coordinate a package in an area with one or more time zone borders inbetween, that can cause a lot of issues so UTC is used instead. Edited yesterday at 09:35 AM by razo+r 1
Dragon1-1 Posted 29 minutes ago Posted 29 minutes ago Sometimes a mission could be briefed with TOTs and such in local time, but as converting between local and Zulu is fairly straightforward, in-cockpit clocks would typically be set to Zulu.
Recommended Posts