Pils

Please provide the full flight plan, and attempt to reproduce it with full steps. I assume this is on V1.7?

It’s a 4-year-old Intel mobile processor in a laptop, I’m not surprised it’s a bit slow. Also what kind of drive is X-Plane installed on? An external?

Do you have brake pedals? Are they setup the same way in control profiles? Maybe the axes need to be reversed.

Potentially a permissions issue. Try deleting /Volumes/T7/Jeux/X-Plane 12/Output/caches/CL650 directory.

https://x-plane.helpscoutdocs.com/article/26-mac-xpl-not-starting

https://discord.gg/TqeDwEwh

WIP.

Might just be using the defaults?

Probably referring to the EVS control. It’s not functional.

That’s no different from creating and using a new airframe though.

It’s the opinion on discord the APU is broken beyond repair and you’ll need to create a new airframe.

Remove all third party plugins except Gizmo and try again. There’s no crash information here.

Please provide Log.txt file

Correct.

Can you post a screenshot please?

You can set the knob positions for main display brightnesses, DataRefEditor is available for that. The CDU brightnesses are internal and not readily accessible.

The issue with DRT?

This is being adjusted for the next version, available in beta via Discord now.

Not the latter, but somewhat the former. It was an FAA outage that induced the simulated total WAAS outage, but it wasn't an outage in their real-world SBAS service itself, rather the reporting systems that the FAA uses to publish the service's status to the public via the internet. It's this system that the Hot Start CL-650 relies upon to determine WAAS coverage, signal quality, availability, etc., according to sim aircraft location. Sure, we could have "failed safe" and kept the in-sim WAAS "operational" based on the last reported status, but where's the fun in that? I think the failure was a nice opportunity for sim pilots to learn a thing or two!

https://www.x-aviation.com/catalog/product_info.php/take-command-hot-start-challenger-650-p-212

What you would do is disable WASD in User Settings, and bind whatever keys you like for moving the view, e.g. move view forward fast (or similar), etc.

Tobii must be disabled by turned off the whole plugin via Plugin Admin, not their interface.

Thanks for clarifying. I didn’t follow before. The “X” prefix is used in Gateway for anything that doesn’t have an ICAO code, basically, so that it can be globally unique.