Pils

This appears to be crashing in the Nvidia GPU driver. Not really something we can trace back to the CL650 easily. You should remove ReShade and all other third party plugins except Gizmo.

I assumed they meant the Cyber Protect anti-malware feature.

Have you looked in the Output directory? That's usually where addons put persistent state.

Disable Zink.

Please also attach full log file.

Linking the account doesn’t do anything with nav data. You need to install that to the sim separately.

IDX > STATUS

Made me think of Philipp’s ESP is trying to be “helpful”.

This comes up when pressing the TO/GA button on the side of the throttle levers. There’s a command in the CL650 tree for these buttons. Or try search for “take_off_go_around”, I think is the default. There’s also commands for the flight director sync buttons on the control wheels (search for “sync”), or use the default control wheel steering.

Run the engines at high power. Or create a new airframe.

Create (and load) a new airframe in career mode and you’ll be back to “out of the box” state.

Private message. The little envelope icon.

Post your Log.txt, please.

It's OK for them to be in MAN, that's what the LOC WILL BE TUNED message is for, to remind you that the FMS is going to retune the radios.

Firstly, may I suggest this video: https://www.youtube.com/watch?v=dvQsqCypHCg Secondly, the most common reason is the off-side nav source not being in FMS as you suggested, so it's good you checked that. There's also a scenario where if one manually tunes the localizer frequency before entering the terminal area, and switches back to AUTO, then the setup may not complete successfully. If an appropriate approach is selected and FMS is the nav source then this setup should happen at ~31nm from the destination, and that's when you'd see the "ghost needles". There could always be bugs in this process. Maybe you could reproduce a specific occasion and record a video of the approach, FMS setup, etc.? Please also provide full flight plans.

*Fingers crossed*

Yes, or possibly removed.

Are you using X-Camera, Tobii Eye Tracker, or ProCam XP?

There is not. What’s provided with the plane in the Documentation directory is what’s been written.

The latter will be bound to the former, and no.

https://support.torquesim.com/hc/en-us/articles/1500004699102-Multi-Threaded-Uploader-Causing-Crash Try this?

You’ll need to post the X-Plane log.

I'm not sure these data refs are ever meant to be used for this purpose so there may be nothing we can do; the axis is the correct way to do this. But did you still have something bound to the axis at the time?

Hi. Firstly, please don't reuse other people's posts for unrelated issues. Secondly, you didn't mention removing the safety pin for the nose gear bay door; was that done?