Pils

Maybe you need to try range? The default is relative already.

mode = "relative",

I don’t think so? I think it’s expecting the Vatsim controllers be signed into Hoppie as CZQX because that’s Gander in real life. I’ll ask the developer if they can add an option to override the station for “GANDER”. Maybe next time you could ask the controller why they’re using Moncton and not Gander?

There is a backtrace but it says the Nvidia driver crashed not the CL-650. :-(

Can you go on http://www.hoppie.nl/acars/system/log.html and find your messages please? (As far as I recall OCEANIC CLX isn’t part of FANS CPDLC on the CL-650 so logging on wasn’t technically necessary, cool that’s it worked though.)

Unfortunately you experienced the dreaded unexplainable VK_ERROR_DEVICE_LOST crash. Something in X-Plane’s rendering engine or the graphics driver had an issue and interrupted the program flow enough to cause the crash. It’s a known issue with the Vulkan rendering mode, as such if you reported it to Laminar Research they’ll just tell you to use OpenGL instead. Hopefully things are improved in X-Plane 12 (because there’ll be no more OpenGL fallback option!). If it happens repeatedly you could try removing all third party plugins (except Gizmo which is required for the CL-650 to operate) and/or reduce GPU burden within X-Plane graphics settings and close any external programs you might be using while flying (Chrome, Volanta, etc.), but it’s a shot in the dark.

What was the airport(s) that didn’t work? Confirm this is Autorouter charts? Please provide screenshots.

No, they just go to the “top left” as far as X-Plane layout is concerned. But I don’t know how this translates on Macs. Maybe a screenshot of the Graphics settings page would help?

Can you set the weather to CAVOK and try to repeat it?

Is there a way in MacOS to make the external display the primary display so that X-Plane considers it the Main Monitor? If so, try that.

You’ve attached a second monitor to your iMac and are using (only) this for X-Plane?

It’s a bug in the message handling that is fixed for the next update. Thanks.

Probably don’t want to change those particular values. I’m not 100% sure they’d have any effect on the CL-650, but any effect may well be changing the flight model to be something not what the developer intended. If you want to have more “precision“ in the controls (and a lot of this comes down to the hardware one uses), one suggestion is setting up a custom response curve so that the (for example) 90% position of your hardware isn’t the 90% position of the sim controls. Rather flatten the “curve” (linear, straight line) from 0% to (say) 90% input results in 0% to (say) 60% output (or whatever range makes sense for “normal” flight envelope deflections). And then 100% is 100% so you can still do flight control checks, etc. If that makes sense.

It does not. (At least incorrectly/artificially like the other examples.)

Thanks. It’s a known issue.

That’s probably just the X-Plane lightning/reflection model playing tricks. I’m sure @Goran_M was well aware of their chrome finish.

Looks like the crash was in the Nvidia driver, not the CL-650 itself, so unfortunately not much can be done by the developer, sorry. Can only suggest making sure Nvidia drivers are up to date.

AH2 also has rudimentary GPWS call-outs (for some reason).

Do you perhaps have the TerrainRadar plugin?

Read the Power Lever Auto-Latch section of this post which I think will help you.

Hard to tell but may be a couple of days…

Seems the NOAA server(s) are down, just have to wait. Sorry.

You need Gizmo.plugin to be enabled, signed in, and a licensed CL-650. Please post your Log.txt file.

This looks like a familiar crash, you may need to use a new airframe until the next update is released.

On the right. It’s just a documentation error.