Pils

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).

https://discord.com/channels/397379810067742721/397408003348889600/1098619351113932820

Yes.

https://discord.gg/eRqyn7am

https://discord.gg/eRqyn7am

https://discord.gg/eRqyn7am

If CDU 1 is blank when you press the FMS function then you probably have a popped circuit breaker.

Attach your Log.txt from a session where this issue occurs and we’ll see.

This usually means you're not following the checklists closely enough and are not waiting for A/C power to be applied to the aircraft and the FMS2/3 to power up before using FMS1 to set up databases, enter flight plan, etc.

https://discord.gg/cq4B783U

Not your fault. It wasn’t really messaged/communicated that well by Laminar, to be honest.

The Zink incompatibility has been known for a long time, but the developer has chosen for next update of the Challenger to have an extended development and beta cycle, so there’s a lot of fixes that aren’t released to “the world” yet. If you’d like to join the Discord and get access to the beta then you’d be welcome!

Did you restart the sim afterwards? Please provide screenshot of Graphics settings and Log.txt from X-Plane, please. Thanks.

A bit rude, but ok. I can't confirm without the Log.txt from X-Plane, but 12.1.0 made the Zink plugin bridge the default, and V1.7 of the Challenger does not support this option. If you disable it then you'll be back to 12.0 behaviour.

https://discord.gg/cq4B783U I'm not sure, to be honest. In that scenario a manual nav source switch may be required. I'll try it in the beta. Do you publish video of the issues you mentioned?

It's the same on PL21, except the knob is on the PFD's control panel.

(WebFMC is a far superior solution regardless.)

Try not maximising the window.

I made a couple of videos to demonstrate the difference: 1. Early APPR: 2. LNAV/VNAV: