Direct To feature not working smoothly

  • Ipad pro 12.9’ 4th gen

    IpadOs 27.0.1

    Latest aerofly version

    The direct to feature does not work very well in both airbus and boeing - when trying to select a waypoint that is in a departure procedure on Boeing it basically erases your entire route, while on airbus it simply doesn’t work.

    I might not be entirely correct, since it is hard to tell exactly what happens in what exact situation, but certainly things don’t behave as they should.

  • I can confirm I have the same behavior on my Mac. (Specs below)

    Today I flew the A350 from OMAA-LEMG while recording a new future video for my channel, and a direct that was PAST the SID behaved very weird:
    First it accepted the Direct To BOPIT and flew toward that waypoint that I directed it to, but when arriving at BOPIT it flew off the route, turned into heading mode, and the waypoint that was supposed to come next, called DANOK, simply was ignored. (I checked in the upper right corner of the ND and it said constantly BOPIT 1.0nm, like it "did not step over" that waypoint and did not transit towards DANOK.)
    Also: When using the Direct To feature, there was suddenly two waypoints BOPIT in the Flightplan of the MCDU of the A350.
    See the screenshot below to understand the explanation of both the issues that I mention here:



    It's definitely not working as it must be working, and the only way out of this mess is to do what I did in the previous version of AeroFly:
    Fly heading mode toward the new waypoint, (in my case DANOK) then wait long enough until its about 4-5nm near the waypoint, then in the upper right corner of the ND it suddenly says DANOK, and when reaching DANOK it goes back to NAV mode.

    This is a clear bug and must be fixed!