Jalava Posted November 9, 2020 Posted November 9, 2020 On OB 2.5.6.57264 Using DTOT Adjust doesn't seem to update the new DTOTs for waypoints to all systems. Steps to reproduce (For sake of simplicity let's assume mission time is around 12:30:00 and distance to WP1 is around 50 miles or so to get relevant numbers): 1. Setup waypoint 1 on WP page DTOT to 00:00:00 2. On NAV page TIME subpage, Set DTOT Adjust to lets say 13:00:00 3. WP page now shows DTOT as 13:00:00 4. However, while TOT delta is shown correctly, the RIAS on CDU and on HUD will still show incorrect value like DTOT were still at 00:00:00, not in 30 minutes with 50 miles to go or around RIAS 100 We use this for setting times in waypoints when push time at WP1 is still unknown when starting up and adjust DTOT based on given push time to adjust the whole plan Workaround: For each waypoint after step 2. copy the time from DTOT for each waypoint into scratchpad and re-enter it as DTOT. After this RIAS is also corrected.
Stuka Posted November 10, 2020 Posted November 10, 2020 I just tried this out, but I don't see an error. What I did: Start mission at 08:30Z, WP1 is about 50NM away. Set the required TOT for WP in the CDU to 08:39 -> RIAS is showing a speed I might be able to handle Got to the DTOT adjust and set it to -00:01:00, effectively making my desired TOT a minute shorter (08:38). -> RIAS showing higher speeds Back to DTOT adjust, and set it to +00:01:00 . Now my DTOT for WP is 08:40 -> RIAS showing lower speeds. By the sounds of it, you interpret the DTOT Adjust as "The new DTOT". The value you enter there, is a correction to the existing DTOT in hours, minutes and seconds. Please post a track with you step in case I'm misunderstanding you. Windows 11 | i9 12900KF | 64GB DDR4 | RTX 3090 | TM Warthog HOTAS | Saitek Combat Rudder Pedals | TM MFDs + Lilliput 8" | TIR5 Pro
Frederf Posted November 10, 2020 Posted November 10, 2020 I see what's going wrong. You're using the system a little weirdly and getting unexpected (but correct) results. If you enter waypoint DTOT as "0" then you're going to get midnight in the future, not the past. I.e. if it's actually January 15th 12:00:00 and you enter DTOT 00:00:00 you're really entering a TOT of January 16th 00:00:00. Then when you adjust DTOT forward another 13h you get January 16th 13:00:00, not January 15th 13:00:00. That's not 1 hour from now it's 25 hours from now. It's impossible to enter a DTOT in the past from the pilot seat. If for whatever reason you wanted a TOT that was 2 minutes ago you'd have to enter a future DTOT and then a DTOT adjust of negative time. The only real bugs I see is when you enter 24:00:00 into DTOT adjust it displays as "+00:00:00" instead of "+24:00:00". As such +24h and +0 looks identical. And all negative adjusts have an off by one error of 1 second. E.g. +00:00:01 negated becomes -00:00:02, +00:00:02 negated becomes -00:00:03, and so on. 1
Jalava Posted November 15, 2020 Author Posted November 15, 2020 I stand corrected, you cannot set TOT into past hence it will assume 24 hours forwards in time for TOT. Setting the original TOT do some easy time bit forward in time from takeoff and then adjusting it back to push time works correctly.
Recommended Posts