HOLD is a mess
-
Hello,
I tried to execute a non-published hold inbound LFBD LMG2L instructed by IVAO ATC (MARRE FL240 RIGHT TURN 1min30), I initially set up the speed to be 210kts then decided to change the hold speed to 240kts before starting first turn, the aircraft had huge issue to fly the hold, it made a very shallow right turn before trying to catch an imaginary nav on the left (in downwind, so I had to select heading to force it into the right turn back to MARRE), then when I tried to re-programmed it while turning right (as it was totally off set), selected direct to MARRE, it removed the whole approach setup and bugged out the hold by becoming a square that the airplane kept overshoot
the square allows the aircraft to fly the hold after a few pattern but in a very innacurate behavior (it keeps trying to catch up with 90° nav turn so the flight path looks like a giant peanut, see image bellow).
Alex
F28, F70/100, A320, B737, B777 & DH8D sim-pilot -
Hello,
I tried to execute a non-published hold inbound LFBD LMG2L instructed by IVAO ATC (MARRE FL240 RIGHT TURN 1min30), I initially set up the speed to be 210kts then decided to change the hold speed to 240kts before starting first turn, the aircraft had huge issue to fly the hold, it made a very shallow right turn before trying to catch an imaginary nav on the left (in downwind, so I had to select heading to force it into the right turn back to MARRE), then when I tried to re-programmed it while turning right (as it was totally off set), selected direct to MARRE, it removed the whole approach setup and bugged out the hold by becoming a square that the airplane kept overshoot
the square allows the aircraft to fly the hold after a few pattern but in a very innacurate behavior (it keeps trying to catch up with 90° nav turn so the flight path looks like a giant peanut, see image bellow).
I attempted two holding patterns during an approach yesterday and also experienced very poor execution from the aircraft, particularly on parallel and teardrop entries. Direct entries weren't as problematic, but honestly, it's surprising to see such a glaring error in an add-on of this level.
It makes you wonder how no one noticed something this basic during the beta tests.
FYI, I've already submitted a support ticket to Just Flight reporting this inconsistency.
-
I agree with both of you. That holding profile does not look right at all.
-
Same happened here, in all cases, published and non published holds, direct, paralel, drop entries, L turns, R turns
I'd say that's a basic for this level of aircraft... -
Just wanted to share a very specific example of the holding pattern issues some of us have been discussing, in case anyone else can replicate it or has seen something similar.
I was flying the ILS X approach for RWY 15 down here at my home base in Curitiba (SBCT). I executed a missed approach, and initially, the LNAV tracked the profile perfectly towards the CT171 missed approach holding fix.
However, upon reaching CT171, the system completely failed to establish the hold. Even worse, instead of initiating the published left-hand turns, the aircraft inexplicably banked to the right. After that wrong turn, it completely ignored all time constraints for the holding legs and essentially just flew in endless, uncoordinated circles.
It seems the LNAV logic completely breaks down during this specific transition. Bizarre.
-
Thank you all for the feedback. That's very odd, as the behaviour is very different to what we have seen in our tests.
For any AFCAS/ATS/FMS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support
The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product.
Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s-
With holds in particular, it would significantly help us track this down if specific examples could be provided for us to replicate on our side. For that, we would need: the flight plan, including the specific waypoint where the hold was created, if any edits were made to the HOLD page, and the aircraft weight (either at the start of the flight, or when entering the hold).
Mark - Just Flight
