Knock-Knock Posted January 23, 2019 Posted January 23, 2019 The Mission time or runtime counter in either DDI under TAC/SUPT, doesnt tick over after 59m59s, it just runs from 59m00s to 59m59s and keeps looping that. Id imagine it should just continue counting minutes, so 61m32s etc? - Jack of many DCS modules, master of none. - Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS. | Windows 11 | i5-12400 | 64Gb DDR4 | RTX 3080 | 2x M.2 | 27" 1440p | Rift CV1 | Thrustmaster Warthog HOTAS | MFG Crosswind pedals |
Ramsay Posted January 23, 2019 Posted January 23, 2019 (edited) The Mission time or runtime counter in either DDI under TAC/SUPT, doesnt tick over after 59m59s, it just runs from 59m00s to 59m59s and keeps looping that. Id imagine it should just continue counting minutes, so 61m32s etc? AFAIK there is • ZTOD - Zulu Time, (00:00:00) • LTOD - Local Time of day (00:00:00) • TOT - Time on Target (00:00:00) • ET - Elapsed Time (increments 00:00 to 59:59 and rolls over to 00:00 to continue counting) • CD - Countdown Time (decrements 59:59 to 00:00, defaults to 06:00 with WoW) Do you mean Elapsed Time ? I expected ET and CD to be TIMEUFC stopwatch like functions, started and stopped with ENT on the UFC. Edited January 23, 2019 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Knock-Knock Posted January 23, 2019 Author Posted January 23, 2019 Yes ET, Elapsed Time, thank you. - Jack of many DCS modules, master of none. - Personal wishlist: F-15A, F-4S Phantom II, JAS 39A Gripen, SAAB 35 Draken, F-104 Starfighter, Panavia Tornado IDS. | Windows 11 | i5-12400 | 64Gb DDR4 | RTX 3080 | 2x M.2 | 27" 1440p | Rift CV1 | Thrustmaster Warthog HOTAS | MFG Crosswind pedals |
Recommended Posts