Skulleader Posted January 1, 2016 Posted January 1, 2016 Hello, The clock aboard the cockpit don't work, if my mission is 10h00 my clock show me 6h00. Is it just me or other members have this problem ? Thanks in advance, Skull. [sIGPIC]http://forums.eagle.ru/signaturepics/sigpic93192_6.gif[/sIGPIC] My Facebook: https://www.facebook.com/profile.php?id=100006748814655 My P-51D's Mod: http://forums.eagle.ru/showthread.php?t=142739 One of my few skins : https://www.digitalcombatsimulator.com/en/files/1452845/
Flagrum Posted January 1, 2016 Posted January 1, 2016 According to the manual, the clock is supposed to show Zulu time (i.e. UTC+0). So it is correct that it shows a different time. But if the time offset is correct - for Georgia and for Nevada respectively - I have not tested ...
Flagrum Posted January 1, 2016 Posted January 1, 2016 Just tested it now (mission start time 12:00): Georgia is UTC+4, the cockpit clock shows 16:00. Correct would be 8:00! Nevada is UTC-8, the cockpit clock shows 16:00. Correct would be 20:00!
grunf Posted January 1, 2016 Posted January 1, 2016 In NTTR Take off Instant action mission the clock doesnt work at all.
Skulleader Posted January 2, 2016 Author Posted January 2, 2016 Hello guys, thanks for your explanations. Bye, Skull. [sIGPIC]http://forums.eagle.ru/signaturepics/sigpic93192_6.gif[/sIGPIC] My Facebook: https://www.facebook.com/profile.php?id=100006748814655 My P-51D's Mod: http://forums.eagle.ru/showthread.php?t=142739 One of my few skins : https://www.digitalcombatsimulator.com/en/files/1452845/
Azrayen Posted March 7, 2016 Posted March 7, 2016 Reported. As DCS gives the local time instead of GMT (UTC) time, it may be easier to stick to this local time for now. Otherwise, the aircraft should know on which map it is to be able to set its clock correctly. I'm not sure this information is available to it (nor if it's a good idea to do so because each new map will require aircraft upgrade).
PE_Tigar Posted March 8, 2016 Posted March 8, 2016 But LAT-LONG is available to the plane, isn't it? If you anchor the clock offset parameter to that, you can consistently get proper UTC time on the clock.
YoYo Posted March 8, 2016 Posted March 8, 2016 I miss this topic. I wrote about this too: http://forums.eagle.ru/showthread.php?t=162123 . Good point, I hope ED or Razbam will solve it. The time is from Mission Editor. Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 5090 32Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro
Rangi Posted March 8, 2016 Posted March 8, 2016 Perhaps an easier solution would be to make the clock manually adjustable. PC: 6600K @ 4.5 GHz, 12GB RAM, GTX 970, 32" 2K monitor.
Recommended Posts