Pils

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.

It's because this specific command needs to be "held" active for more than 1 frame, and XSaitekPanels is actuating commands in X-Plane incorrectly, so this can never happen or work without custom integration.

You’d use FlyWithLua probably

Yes we’ll need to find and use new URLs in a software update.

You must use time dilation NOT ground speed acceleration.

The only “clever” part is setting up Discord to have a “push-to-mute” keybind that matches the xPilot PTT button to avoid echo if you’re using Vatsim. Vatsim Audio is not smart enough to not play your partner’s audio back at you over the radios.

I’m sorry I don’t understand the question.

That’s up to you to organise outside of the sim. I use Discord or FaceTime.

https://discord.gg/KSkkkMP8jH

Make sure your X-Plane audio sliders aren’t at zero. Also post your Log.txt

You haven’t installed the XP12 nav data properly it looks like. Look at the contents of the Custom Data directory.

Maybe a build with some debug output?

You’ll have better luck getting in contact with Just Flight, this forum has nothing to do with them or Air Hauler. https://www.justflight.com/support

There is no difference in the log, regardless my request hasn’t changed. Simply disabling the plugins is not sufficient, they must be completely removed. There is nothing to debug with regards to the Challenger’s systems.

It wasn’t supported then either, and isn’t now, for reasons I can’t go into. No. It’s been there since day 1.