Pils

Nope! Thanks!

Flight model crashes need to also be reported to Laminar Research. Thanks!

The route on the plane's map isn't like an Airbus where it'll fly exactly along the line, so some deviations are expected. Looking at attempt 3 again (at 4x speed???), I see it did draw a turn to the right, but when it sequenced it took the shorter path to the left. That's maybe a corner case that the developer needs to address. But, I think to get you passed this issue, an adjustment to flying technique will put it inline with what's expected (and demonstrated by us).

You're flying the climbs in PTCH mode (and at a pitch less than 10 degrees in some cases), while not accelerating past 185 kts (as per the chart). From what I can tell the plane flew exactly as you commanded it to, at low pitch and low thrust (due to low speed target), with attempt one being the lowest (zero climb rate/VS at times, should be something you're monitoring). After initial take off phase you should be switching vertical mode to VS or FLC. The plane is capable of climbing at several thousand FPM, not hundreds. Obviously in hot weather (like ISA+19 you have) and with a heavy fuel load that will be lower. FWIW the chart may show this, as that's what's expected, but it's not enforced in the database coding. If you leave the PFD ROSE in HSI mode and the CDU on the LEGS page you'd have shown what exactly it was flying more clearly. The popup makes it easier to see the DTK, it was flying to course 331, which is a "shorter" turn by going to the left. I think it all comes down your procedures, and the plane is flying exactly what the database tells it to. Hope this helps. P.S. X-Plane's default video capture is terrible, I suggest using OBS Studio. Also uploading to YouTube or Streamable.

I think it starts to go “wrong” (it flew what the coding was in the database but not what was depicted/expected) when it turns inside the Navigraph estimate and reaching the 10500’ restriction too soon. Were you flying at 185 kts max as charted the whole time?

Change display scaling and text size back to 100% https://support.microsoft.com/en-us/windows/change-the-size-of-text-in-windows-1d5830c3-eee3-8eaa-836b-abcc37d99b9a

A bug triggered by noisy hardware. Will be resolved in next update. Workaround is to add a dead zone to Yaw axis.

You’ll need to provide something to base that help on, such as the Log.txt from X-Plane containing the crash.

Not in a million years.

Buy an x-aviation product that uses it.

Scenery also includes plugins. ¯\_(ツ)_/¯

There’s no crash reported in this log so there’s nothing for us to investigate unfortunately. I suspect the “livery spam” is from one of your plugins.

I would suspect your FPS is way too low. What kind of PC/Mac hardware are you using? Uploading the Log.txt from X-Plane would be helpful.

“This problem will be rectified with X-Plane 12.3.1” I guess that’s resolved now, but I guess was worth a (long) shot.

Please attach the original Log.txt What was the thinking for doing this?