EasyEB Posted October 13, 2020 Share Posted October 13, 2020 Syria local time (F10 map) 07:51:26, in cockpit clock shows 00:18:34. Link to comment Share on other sites More sharing options...
RglsPhoto Posted October 13, 2020 Share Posted October 13, 2020 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 Link to comment Share on other sites More sharing options...
EasyEB Posted October 13, 2020 Author Share Posted October 13, 2020 Then ZULU time should be three hours behind? Link to comment Share on other sites More sharing options...
RglsPhoto Posted October 13, 2020 Share Posted October 13, 2020 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 Link to comment Share on other sites More sharing options...
EasyEB Posted October 13, 2020 Author Share Posted October 13, 2020 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. Link to comment Share on other sites More sharing options...
Stuka Posted October 13, 2020 Share Posted October 13, 2020 (edited) A prepared mission maybe? If so, remove the CDU folder from the miz file. Edit: reported for the "prepared" missions Edited October 13, 2020 by Stuka Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro Link to comment Share on other sites More sharing options...
Rookie1983 Posted October 13, 2020 Share Posted October 13, 2020 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. Link to comment Share on other sites More sharing options...
Stuka Posted October 14, 2020 Share Posted October 14, 2020 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. Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro Link to comment Share on other sites More sharing options...
EasyEB Posted October 27, 2020 Author Share Posted October 27, 2020 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. 1 Link to comment Share on other sites More sharing options...
Recommended Posts