Pils

That isn’t the cruise level, unless you’re cruising at 370 feet.

I think the current beta version has hundreds…

Yes. What are you looking for specifically? Most (all?) of the issues/missing features you mention are due to XP 12 itself, and can only be solved/added once LR do their side of the job. Sadly this is happening very slowly.

You can’t do this, but if you get updated IXEG nav data from Navigraph then maybe it’ll exist?

Unfortunately there's not really enough context (or quality) in the photos to tell what went wrong. A couple of things from the description you gave: 1. It's not necessary to preselect zero feet for the altitude; the FAF/GS intercept altitude is sufficient. 2. Once in VALT you have to fly at least one dot vertical deviation away from the path before VPATH will capture again, which you have to do explicitly with another vertical mode (FLC, VS, etc.) 3. I can't explain why the cruise altitude would populate the estimated altitude, unless you never reached the planned altitude and the FMS still considered you to be in climb phase. Is it possible to reproduce and screen record this full flight, and publish a video (preferably in native resolution) to YouTube or similar? Also please post your Log.txt from X-Plane after loading the CL650.

There’s no limitation of running the APU during fuelling operations, that I know of. Operators, of aircraft and/or fuel truck, may limit starting the APU during fuelling, however.

Did you forget this was already answered?

Press the MFD DATA button on the CDU.

Sorry this isn’t an X-Pilot the Vatsim client support forum.

Unfortunately the custom TCAS MFD page has been nonfunctional since Laminar Research changed the way traffic works in the sim in 11.50. It'll be resolved with the next update, which also brings X-Plane 12 support (don't ask for an ETA because there is none).

Can you just do us a favour and unlink/remove your custom scenery please?

They said Windows 11. ;-)

It’ll happen to everyone not using the V1.8 beta.

APPR/VNAV is the correct way to fly an RNAV approach with Pro Line 21, yes.

The sat phone feature simulates an Iridium station. The feature is broken now.

The delay itself isn’t the issue, that’s logic in the Chally simulation (for reasons not relevant to this). The issue is not actuating commands when a hardware button is pushed, held, and released using the correct API functions.

How are you trying to raise the gear? With keyboard? Mouse? Physical gear lever? Would help by providing a video showing the state of the aircraft, e.g. overhead, hydraulics, etc., and the issue at play.

@richjb Have you discussed with the GoFlight developers about using the X-Plane SDK properly?

He might have forgotten about that already. ;-)

If there is an "AT"/"AT or ABOVE" constraint on the descent and VNAV is active (annunciated as VALT when at cruise level) then it'll automatically arm the PATH vertical mode (VPATH), which as explained follows a default 3 degree angle to meet the first constraint.

I can't answer this question without more information. You'd need to provide a video and the full flight plan. It will level off after altitude constraints have been met until it needs to descend again at the default descent angle to meet the next constraint. Maybe that's what you're seeing? Please take actual screenshots, or better yet a video screen capture (with OBS Studio or similar), of the whole screen. X-Plane even has this ability built-in to take screenshots (don't use it for video), see the keyboard assignments window.

Have you left the gear securing pins installed?

We don't recommend using the beta Gizmo V23 (yes it's still beta) at this time.

Is it possible to provide screenshots or a video from prior to and during the descent, please? That'd help us figure out what's happening. Just a clarifying note on some differences between the 737 and Challenger: 1. VNAV isn't a descent mode unto itself, rather it's a modifier on the other modes, e.g. FLC, V/S, PATH, and PTCH. Enabling VNAV will allow the FMS to control altitude preselection to meet flight plan restrictions, and also speeds if separately enabled. 2. The descent path calculated by the FMS is not an idle power descent as is often used in airliners. The Challenger will fly a geometric path, based on the default descent angle set, a per-leg override, or what's required to meet a restriction.