narfnarf Posted January 24, 2013 Posted January 24, 2013 Hello all, currently I'm trying to create missions which require the pilot to reach/attack their target at a defined time. To do so, I set an appropriate time including the checkbox for each waypoint in the editor. The first waypoint gets, for example, 09:15:00 when the mission start is 09:00:00. When I start the mission the calculation seems to be off a couple of minutes. I did not have time to do extensive tests yet, but it seems that the DTOT in the plane for each waypoint is calculated using the CDU start as reference and not the mission start time like the editor does. Am I doing something wrong here? Or is this intended behaviour? If so, what exactly is the behaviour? Or is this simply a bug? PS: I vaguely remember that something like this was discussed earlier (during the public beta?) but I did not find the thread so here's a new one :)
narfnarf Posted January 27, 2013 Author Posted January 27, 2013 Hm, is no one here able to help me with this issue?
nomdeplume Posted January 27, 2013 Posted January 27, 2013 It's been like this since forever, I think the issue is that it automatically adds some time to allow for startup but this isn't communicated via the mission editor UI. You can work around it by working out what the offset is and then decreasing the desired TOT by the appropriate amount. Alternatively, instruct the player to check and correct the TOT for any waypoint for which it's important, which will give them something to do during startup and ingress.
narfnarf Posted January 27, 2013 Author Posted January 27, 2013 Thanks for the feedback. Unfortunetaly the time added to the DTOT is dependant of the star time of the CDU (look like the time when the CDU finishes its BIT +30sec are added to the DTOT). So, it is not really possible to anticipate the offset and modifiy the WPs in the editor accordingly. Adding all WPs manually in the CDU is not an real option either. And the DTOT-Offset in the GPS/Time settings do not allow negative values. Looks like this is a annoying little bug. Bummer. I'd love to hear that a tester can confirm this behaviour and report this issue (if not done already).
narfnarf Posted February 5, 2013 Author Posted February 5, 2013 No tester can acknowledge this issue?
narfnarf Posted February 27, 2013 Author Posted February 27, 2013 Ok, now with 1.2.3. out maybe some tester has enough time to take a look at this aka bump
Eddie Posted February 27, 2013 Posted February 27, 2013 I'll add it to my (rather long) to do list. It's been around forever, but it's one that has been forgotten about. 1
narfnarf Posted February 27, 2013 Author Posted February 27, 2013 Thanks, take your time. It is not really a showstopper. But glad to know that it is not forgotten any more.
narfnarf Posted May 23, 2013 Author Posted May 23, 2013 Hey Eddie, did you find some time to check this issue? Will this be fixed at some time? I'd love to fly some mission with precise timing in the future...
TC Posted May 23, 2013 Posted May 23, 2013 You can adjust your TOT via the CDU. Nav/ Time/ DTOT Adjust. Cheers TC
narfnarf Posted May 23, 2013 Author Posted May 23, 2013 I know. But the offset created by this issue is kind of erratic, so I'd rather have the bug squashed...
Eddie Posted May 23, 2013 Posted May 23, 2013 Yes, it ha been reported. When it will be fixed is in the hands of the devs.
narfnarf Posted September 6, 2013 Author Posted September 6, 2013 I'd love to know whether this bug will get attention from the devs or not, AKA shameless bump :music_whistling:
Recommended Posts