Sequential Direct Tos
-
I had some potentially weird behavior on a flight today to KBNA. I had a filed flight plan that of KLBE AIR HVQ VXV KBNA that ATC promptly threw in the garbage. Shortly after making contact past AIR, they directed to me proceed Direct GROAT, PASLY, BNA, KBNA. No big deal, I hit Direct, GROAT, and off I went from PPOS to GROAT.
As I was approaching GROAT, they had me turn 180 for spacing as I had another jet running me down. After a good 10 or 20 miles south, they had me proceed direct GROAT again.
The issue here became that rather than trying to go from PPOS (actual present position), it tried to bring me north back to the track between PPOS (the original position when I started direct GROAT 150 miles north east) rather that from my actual current position.
The solution ended up trying to do a direct to from instead of just direct to, I selected GROAT and PPOS and that made GROAT PASLY the active leg, and from there I was able to direct GROAT the way I expected, with it starting from my current position.
Is it unable to do multiple sequential direct tos? I just read that part in the manual this morning, I thought I had a decent grasp of it, but it could be user error.
-
I'm afraid I might have to have seen this one for myself to tell you. I will try to recreate something similar for myself and let you know if I get the expected behavior.
-
That's the simplest form of what I thought you were describing. I believe I've tested that before, and it should work. A new PPOS will be generated, and the direct-to target will be made the active waypoint. I'll try it.
-
I just took the opportunity on my current flight to try this. I had a very sharp turn to double bank on my route and it was turning to intercept the line between waypoints it turned to wide to make.
I did a Direct To to stop it from intercepting and it pointed directly at the waypoint, then turned a few degrees off using heading mode, and Direct To a few minutes later wouldn't update the PPOS location.
It seems to work fine if you have at least one waypoint between your active leg and PPOS, but not trying to do it twice in a row.
Deleting PPOS and then doing Direct To got it going this time, though.
-
I think I found where I added a piece of code within a few days before release that probably caused this. I'm giving Direct-To a major overhaul anyway, so this should be fixed in the process. Thanks for telling me so I knew what I was looking at in my code.
-
J jmarkows referenced this topic
