WOPR Posted May 16, 2019 Posted May 16, 2019 Description: When spawning in at a time later than mission start time, the F-14 clock shows mission start time instead of current time. Work around: Manually set clock as close you can to current mission time. Can't tell if this intentional or not, and it's probably not a big deal to most players, including myself. It's just a minor nuisance when knowing the current mission time matters.
eatthis Posted May 18, 2019 Posted May 18, 2019 what clock lol 7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr
Boagord Posted May 20, 2019 Posted May 20, 2019 I guess this clock http://www.heatblur.se/F-14Manual/cockpit.html#clock http://www.heatblur.se/F-14Manual/cockpit.html#rclock
Nealius Posted June 26, 2019 Posted June 26, 2019 I just noticed the same on MP flights. I haven't cross-checked SP flights yet.
Super Grover Posted June 26, 2019 Posted June 26, 2019 It's fixed internally and should be available to you with the next update. Krzysztof Sobczak Heatblur Simulations https://www.facebook.com/heatblur/
CoBlue Posted October 2, 2019 Posted October 2, 2019 It's fixed internally and should be available to you with the next update. OB, latest. This bug is still present in MP. i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
IronMike Posted October 4, 2019 Posted October 4, 2019 OB, latest. This bug is still present in MP. Thank you, I forwarded it to Grover. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
Boagord Posted November 30, 2020 Posted November 30, 2020 (edited) Bump! the clock shifts approximately 13 seconds every 20 minutes, tested with the cold start instant action mission. I don't know if it's the same bug or another one. Edited November 30, 2020 by Boagord
Nealius Posted December 10, 2020 Posted December 10, 2020 Yes, clock is still inaccurate. CASE III push timing is not possible without using the info bar.
RustBelt Posted December 10, 2020 Posted December 10, 2020 (edited) Problem is 65535 (the "full defelction" integer DCS runs its needles on) divides by 60 to make 1092.25 and by 360 to make 182.0416666... so every 1 degree on needle movement is an approximated position. where as 360/60 is a nice sane 6. Guess what happens if you round up that 0.25 to 1093 every second over say 20 min? The Second hand needs a re-sync with the game clock to 0 every time it passes 60 or the error adds up. Computers HATE round things. Edited December 10, 2020 by RustBelt 1
sublime Posted December 11, 2020 Posted December 11, 2020 also I thought there was a timer button but dont see one. I dont even touch the damned thing after messing with it once and regretting it terribly
Recommended Posts