Pils

You could analyse the FDR files in \Output\CL650\FDR after every flight to build a log. Or use X-Plane's built-in logbook. Or, better, use an external flight tracker like Volanta.

https://discord.gg/tCver5En You can try deleting the CL650 directory in Output. This’ll remove all airframes and settings. (However this doesn’t happen when uninstalling so not sure what’s happening there.) You seem to be using the 2D panel display feature of XP. I recommend against this, this is not the intended use of the pop ups. Each secondary display should be set to Unused in XP graphics settings, and then each popup turned into an external window for placement by the default OS window manager (or some third party tool such as Sizer4 on Windows).

If you want to start over create a new airframe. Every airframe will restore its last state by default, it’s persistent. If you want it to be in a different state you have to put the plane in that state and save it for later use.

https://discord.gg/RwH3JBpT

https://discord.gg/RwH3JBpT

That’s just how it works. There’s no negative axis position in X-Plane.

Can you screenshot what you’re clicking?

I think some operators use a fixed 91%, as it’s close to the limit for ISA at sea level, and really only a placeholder.

The key is to get at least the Max variant, with the most GPU cores available, and 24 GB of unified memory if possible. Anything less will likely struggle to get good X-Plane performance.

Yes, by getting in touch with X-Aviation https://support.x-aviation.com

Network sync of aircraft state will never work properly for addon aircraft. I don’t know about your specific setup/issue, but TBM most likely needs to only be run once on the main computer with the controls and avionics displays.

https://discord.gg/NW4bxAAF

You probably switched database on FMS1 before the AC power was applied to the FMS2/3, by going out of order from the checklist.

Gizmo is not required for activation on Linux. You, and the others, can ignore this specific error.

Last backtrace isn’t similar, points more at the sim itself, which would require reporting to LR. However as you have many plugins you’ll need to remove all third party plugins except Gizmo64 in order to test on a “clean” system.

The SAM plugin is highly likely to crash X-Plane. This will need to be removed before we can troubleshoot reliably. There is an alternative available as SAM is no longer supported by its developer. https://forums.x-plane.org/index.php?/files/file/90865-opensam-an-open-source-replacement-for-sam/

I’m sorry this isn’t an xPilot (Vatsim client) support forum.

Is it possible to post a video of this behaviour, please? Thanks.

Ah ok. If using Xsaitekpanels, or similar interface, plugin I suggest removing all the default functions, if they’re still in place. Can be in basic function, there’s commands for all the FCP functions.

Any chance you can provide a sim screen capture and log.txt, please?

Sure: 1. Open the zip file from downloads folder 2. Run the installer for your OS (Windows or macOS, probably) 3. Follow the on screen instructions

Yes. No. (There's no way to do this.)

Are you using Zink? If not, try to. Also... Please also attach a Log.txt from XP.

The configurator is the only way the autopilot controls on the Bravo can be used as intended, which my profile does. The course selector moves the course knob, which isn’t always what one needs/wants.