HI,

I have a question here for the community and devs,
Is it normal/realistic to have the LNAV do squiggly zig zag lines, double turns and etc., and extremely tight physically impossible turns right after takeoff? (I'm pretty sure not..)
Also after it draws and plans idiotic tight turns, it fails to follow them and turns 360 degrees, goes back to the previous waypoint and keeps missing the turn and circling.
Attached is an image of what I saw, these stuff happen all the time and modifying speed constraints sometimes fixes it, but yet there are un-explaned random turns like at SDV, why does it point out a bit between SDV and XIBUS? that turn can easily be taken.
And again, what is the zig zag on final? why can't it just draw a straight line and with what calculations does it get to this result?
if I set speed 200 knots at TOMOS the lines get straight, but if i set 200 knots at LALTO too the zig zags come back,

With another VIA, which was right at the blue 10 marker on the screenshot, it would go from LALTO to "10" and then back to TOMOS in such a stupid curve that it wanted to do a 15 mile wide turn followed by a stand still 290 degree turn and then back to TOMOS for a misaligned path,

literally makes zero sense and it's just god f***g awful to release an aircraft like this and not fix these base type of stuff after a year,
complete disappointment.

I have seen similar behavior on the GIP28 arrival into LSZH - between ZH449 and ZH457, it created a similar set of bizarre S-turns.

Exactly, I keep getting this and as a matter of fact the instant 360 turn departure happend at Zurich today.

Now don't take my word for it but have you checked your speeds at waypoints when that happens. I know that even the PMDG does this when the speed is too high for the waypoint.

5 minutes ago, MITCH1988 said:

Now don't take my word for it but have you checked your speeds at waypoints when that happens. I know that even the PMDG does this when the speed is too high for the waypoint.

The speeds were fine, there is no way takes 15 nautical miles to take a turn at 200 knots, as a matter of fact the lower speeds i set the worse the zig zags and huge turns god

The problem isn't really the fact it does these, i know it's not easy to code, but compared to any PMDG, I never had this issue ever there and I flew a lot with the 777, the ini A340 cant fly. I literally can not make a full flight without these zig zag lines and 40 minutes of deleting waypoints in the middle to help the route straighten out

Edited June 22Jun 22 by sajtww

Just had another bad one: VEBIT4N from Zurich, runway 32. After reaching OBEDU we went around in a big circle until we were cleared direct to GERSA.

The 777, which uses ARINC data also has had issue recently with STAR waypoints. Having fly-over coding where there shouldn't be and distance to go errors. I'm wondering if maybe something changed coding-wise with the latest AIRAC cycles.

An update on this, flew to GCLP the exact same airport in the Original post, and the PMDG 777 did a Fly-by for LALTO, executed it perfectly and went straight to final for a perfect turn.

Hi,

These issues are known to the team and being investigated. Thank you all :)

I had this when i used simbrief to import a flightplan, and got 2 navfixes (CELQU and DKB (vor)) imported and they are on the exact same lat long. Wich resulted in curvy turns for the entire flightplan. So always check

Yeah I've noticed this to. Yesterday I loaded up an autosave from Johannesburg to Perth and the LNAV was always 0.1R with minimal wind that would cause that. And it was wonky with some turns as well,
The plane also oscillated with 4x time acceleration left right, down up so on so forth. However it was working perfectly fine before I went to bed and loaded the autosave the following day. I don't know if the performance degrades after loading an autosave but it was a factor.