Jump to content

Recommended Posts

Posted

default ZULU time is displayed. You have to set time offset in CDU in order to display local time.

I7-6700K OC 4.9G, 896G SSD, 32G RAM @ 2400MHz, NH-D15 cooling system,TM Hotas Warthog,Saitek Pro Flight Rudder Pedals,TrackIr 5, BOSE M2

Posted
Then ZULU time should be three hours behind?

 

 

Syria local time is UTC3, so the answer is Yes.

I7-6700K OC 4.9G, 896G SSD, 32G RAM @ 2400MHz, NH-D15 cooling system,TM Hotas Warthog,Saitek Pro Flight Rudder Pedals,TrackIr 5, BOSE M2

Posted
Syria local time is UTC3, so the answer is Yes.

 

So then local time 07:51:26, and in cockpit clock shows 00:18:34 is completely off.

Posted (edited)

A prepared mission maybe? If so, remove the CDU folder from the miz file.

Edit: reported for the "prepared" missions

Edited by Stuka

dUJOta.jpg

 

Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro

Posted

It's always 4 hours behind, no matter what time you enter in the mission editor.

The only way to fix it : in CDU go to NAV, select TIME, adjust time in the menu by adding 4 hrs.

Posted

The clock shows ZULU (GMT) time by default.

If you want it to show local time, you have to configure it on the time page in the CDU. (feature, not a bug)

 

Using ZULU is easier to coordinate in some cases, as other jets only have ZULU.

 

There is currently a bug where a prepared mission will screw up the clock on CDU startup.

dUJOta.jpg

 

Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro

  • 2 weeks later...
Posted
There is currently a bug where a prepared mission will screw up the clock on CDU startup.

 

Update: If you remove the [time_time] line from the SETTINGS.lua in the CDU folder the clock seems to work as intended.

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...