VarZat Posted January 7, 2023 Posted January 7, 2023 I was working on a mission, which has Time-Over-Steerpoint as a intergrated element in the mission when i realised the in-game TOS was off. I made another mission file and the issue persisted, and below are pictures from the times in the new example mission file: Time of the mission is set at, 01:30:00 LOCAL Dubai (GMT+4) ↓ ETA of the flights 1st waypoint 01:42:35 LOCAL Dubai (GMT+4) ↓ Now, jumping in the cockpit is were the issue appears, video below ↓ I hope the video is clear enough. Attached below is the .miz file. I did not get a track file for this but if you need itt let me know and ill make on replicating the bug. TIME TEST F-16.miz 4
VarZat Posted January 8, 2023 Author Posted January 8, 2023 Could someone replicate this? Im using the latest Open Beta
=617= Evil Posted January 8, 2023 Posted January 8, 2023 1 hour ago, VarZat said: Could someone replicate this? Im using the latest Open Beta So, I did your test and it did the same to me, but then I hopped in one my own missions in the Caucuses in an air hot start jet and the whole TOS system worked perfectly. I could change the TOS, the required airspeed would change correctly, I could M-SEL the TOS at the top of the DED page and then jump to other pages and the speed carrot would stay on the HUD, all that good stuff. Not sure why your test showed the results it did, but maybe you just have to get in the air first? 1 In Thrust We Trust.
VarZat Posted January 8, 2023 Author Posted January 8, 2023 3 hours ago, =617= Evil said: So, I did your test and it did the same to me, but then I hopped in one my own missions in the Caucuses in an air hot start jet and the whole TOS system worked perfectly. I could change the TOS, the required airspeed would change correctly, I could M-SEL the TOS at the top of the DED page and then jump to other pages and the speed carrot would stay on the HUD, all that good stuff. Not sure why your test showed the results it did, but maybe you just have to get in the air first? Alright so i just hopped into the "Takeoff" missions on both caucasus and PG and they both worked without flawlessly.
VarZat Posted January 8, 2023 Author Posted January 8, 2023 So i just loaded up an old mission that has not been saved in the latest update. TOS works fine. I load up another old mission, save it and TOS does not work
ED Team Lord Vader Posted January 9, 2023 ED Team Posted January 9, 2023 Hi @VarZat I'm sorry but I tried a clean mission with exactly those settings and TOS worked fine. I think this may be a question of how that mission was originally created. We'll keep an eye out for other reports and make sure this was just an isolated case. 1 Esquadra 701 - DCS Portugal - Discord
VarZat Posted January 9, 2023 Author Posted January 9, 2023 (edited) @Lord Vader Hey, thank you for responding I found out that this might be happening just at a certain time in the mission. I replicated a mission where i left the time alone and didnt touch the time which worked as intended, and then i made the mission to night time at 01:35:00 on PG map and it occured again. Plane time is around 21:35 at start. Waypoint time in ME is set at 01:43:00, but in the mission the TOS is 3 hours ahead just like before. Could you try to replicate it this way? Edited January 9, 2023 by VarZat
Solution _SteelFalcon_ Posted January 9, 2023 Solution Posted January 9, 2023 Sounds like it‘s an issue if local and zulu are on different dates then? 1
VarZat Posted January 9, 2023 Author Posted January 9, 2023 Just changed the time off the original mission i noticed this on, works!
_SteelFalcon_ Posted January 9, 2023 Posted January 9, 2023 Interesting, but still strange that it‘s an issue.
Lookiss Posted May 8, 2024 Posted May 8, 2024 I came across this bug when creating a night mission, starting at 02.00, on the Persian Gulf map. At 02.00, system time 22.00, go to CRUS page and you see 05.00 as ETA Same, but starting at 10.00, Zulu 06.00, go to CRUS and you see 06.00, so that matches. Maybe it's related to night time, maybe it's related to the map and time? See track files for both cases ETA match_10.00.trk ETA nomatch_02.00night.trk
WHOGX5 Posted May 18, 2024 Posted May 18, 2024 On 5/8/2024 at 10:17 PM, Lookiss said: I came across this bug when creating a night mission, starting at 02.00, on the Persian Gulf map. At 02.00, system time 22.00, go to CRUS page and you see 05.00 as ETA Same, but starting at 10.00, Zulu 06.00, go to CRUS and you see 06.00, so that matches. Maybe it's related to night time, maybe it's related to the map and time? See track files for both cases ETA match_10.00.trk 596.2 kB · 2 downloads ETA nomatch_02.00night.trk 671.72 kB · 2 downloads It's an old bug. The issue arises when local and zulu time are in different dates. So in your example, 22:00 zulu is one day ahead of 02:00 local, meaning the TOS calculations will not work. 1 -Col. Russ Everts opinion on surface-to-air missiles: "It makes you feel a little better if it's coming for one of your buddies. However, if it's coming for you, it doesn't make you feel too good, but it does rearrange your priorities." DCS Wishlist: MC-130E Combat Talon | F/A-18F Lot 26 | HH-60G Pave Hawk | E-2 Hawkeye/C-2 Greyhound | EA-6A/B Prowler | J-35F2/J Draken | RA-5C Vigilante
Lookiss Posted May 19, 2024 Posted May 19, 2024 On 5/18/2024 at 3:07 AM, WHOGX5 said: It's an old bug. The issue arises when local and zulu time are in different dates. So in your example, 22:00 zulu is one day ahead of 02:00 local, meaning the TOS calculations will not work. Thanks, that explains it. Easy to work around for now.
Recommended Posts