Pils

Sounds reasonable. Or your flight controls aren’t calibrated properly.

Suggest looking into https://obsproject.com and their game capture feature

Would it be possible to post a recording?

Shutdown and power off the plane as per the checklists.

It may require a full shutdown.

That’s easy, create a new airframe and it’ll start “fresh”! If you then save a “cold and dark panel state” after initial customisation you can always go back to it whenever or wherever you’d like.

Use career mode, that’s what it’s there for.

Highly likely that Windows Defender is wrong. Feel free to refer to VirusTotal: https://www.virustotal.com/gui/file/0f19f8abf18356f9f21d97a3bcd594ad8cf39ee28089925f6e1ae79e2acf2321/detection And submit a false positive report to Microsoft: https://www.microsoft.com/en-us/wdsi/filesubmission/

https://discord.gg/wyN8eaKK

https://discord.gg/Jz4teBPd

Probably you just have to disable Zink (as mentioned in many posts recently).

https://www.macworld.com/article/338843/how-to-force-a-native-m1-mac-app-to-run-as-an-intel-app-instead.html As explained on this thread, do this on the X-Plane executable.

Use Rosetta for XP.

I don't think there's a limit on the ground power unit(s) being available from the ground services. I've heard of people having the A/C GPU connected and actively powering the aircraft for hours at a time. But they will be removed if the plane moves. That's right, the TURB mode is for passenger comfort. Because it affects the autopilot responsiveness, I assume it's not on by default as it's considered "safer" to be more responsive under (ab)normal circumstances. Not silly at all. Keep them coming.

You can cancel the F/O actions from the Challenger 650 top menu. You should check the bindings you have for anything related to TO/GA (take-off/go-around), and remove them all to avoid this as a source of issues. In particular the default sim/autopilot/take_off_go_around should NOT be used.

At that point maybe best to leave the ATS disengaged, once things go sideways better to fly the aircraft yourself and not worry about the automation “going haywire”, if that makes sense.

I don’t think the memory functions apply to the PFD mode, but let us know.

If the extra monitors are setup as 2D in X-Plane may want to try changing to Unused. Might get better performance. The GPU is very overloaded on your system.

No, they are completely independent systems.

An overview: https://developer.x-plane.com/2023/02/addressing-plugin-flickering/ It was enabled by default for everyone in 12.1.x

There's no reason for it to. Going back to the FMS LEGS page you can see the constraints are 4600A, 3700A, etc. This reflects the altitudes on the chart being safe minimums, one is not expected to "dive-and-drive" anymore. You can see the TOD is just ahead of SILEX, that's where the 3 degree FMS glide path (not slope!) from the runway intercepts the current altitude (4600 feet). After approach was engaged and it switched to LOC guidance it was waiting to intercept the glide slope (GS was armed), you didn't have to do anything other than wait. In the video you're in PPOS map mode, you're only going to see ghost needles in ROSE mode. Seemed fine on capture? If you're referring to later in the approach this all comes down to the right engine going way up in N1 (multiple times) and hence a huge yaw moment being present, which the autopilot tried admirably to counteract, but there's only so much it can do. (Maybe there's some wild rudder input from the noisy hardware too.) Also appears that the rudder and aileron trim aren't centered. I wouldn't be surprised in the low FPS also came into play with the flight control laws and physics going into time dilation.

Something made the right engine spool up to over 50% N1. When there's a split between the engines of 13% or greater the ATS disengages automatically. (In the start of the video the controls are jittering all over the place making me think the hardware controlling them is very noisy, might be related.)

Do you have multiple monitors? There appears to be a lot going on "off-screen". (Also, oof that FPS.)

First step in troubleshooting: Remove all third party plugins except Gizmo64 (especially garbage like SAM).