Pils

Hold X key to crouch.

Deleting the CL650 directory from Output will reset your user settings including any charts service selections and authentication data. You’re 100% sure you reset your settings afterwards? Also, clicking the “visit” button isn’t what brings up the authentication page, it’s the act of turning on the power to the FMS(es) and it determining an (re)authentication is required.

No, it uses X-Plane 11.50+ format from Custom Data directory. If the data is correctly installed in this location (check cycle_info.txt) then read the FMS Primer document provided either the plane for more information about selecting active nav data.

You mean the drop down in the Airframe Manager?

I’d still bet it’s just running in 30hz mode! Care to clarify, @rjsict?

I assumed OP meant the former, but I guess the latter is possible. I agree it would be unusual, there may be cases of using an old HDMI with limited bandwidth or something. ¯\_(ツ)_/¯

This kind of “real time” cooling is not currently simulated. This and cooling/heating of other fluids, surfaces, etc., will be added in future updates as development priorities permit.

What are the ice dataref numbers for when you can’t see the visible ice?

On M1 Mac?

A lot of monitors can run in 30hz mode. It’s a fairly common trick for simmers (particularly in P3D) to limit FPS.

That sounds like a known X-Plane issue, especially on the ground, I’ve found no way to completely eliminate it. You can try using a framerate limit instead of V-Sync. And borderless windowed mode.

Thanks. Known issue and fixed for next update.

The issue was very specific to macOS. Please post a Log.txt from your X-Plane session that was affected by this issue.

Have you ever seen ice on the wings in your sim? Can you force weather to be icing conditions, wait a while, and show the ice dataref output on screen (like you have FPS)?

Looks like potentially a legit bug. Is it repeatable?

Please post your Log.txt for the sim session where this issue occurred. Thanks.

That should work fine. It behaves no differently than any other button/command. I’m not familiar with the GIT software unfortunately. Maybe you can post some screenshots?

Not sure what to say, but it works fine on my Saitek panel and Honeycomb Bravo. Do you have an open thread to discuss your hardware in particular?

The two are independent. If you have disabled Hyper-threading (not recommended, you’re losing performance you’ve paid for!) then Windows won’t see the virtual processors, therefore for the worker count they should be disregarded.

That’s correct, from what I’m told, I only sat in the real plane’s cockpit for an hour or so and wasn’t paying that close attention!

As @oisin650 asked, are you using UI scaling in X-Plane? Or some kind of resolution trickery in Windows? Can you enable the developer menu option to show the manipulators (in Green) and take a screenshot, please?

I hope the community can help. I’ve put out a call on our Discord also.

The commands are working as intended; flaps up means more flap deflection, and vice versa. Maybe counterintuitive but that’s how it’s implemented. Thanks for the feedback!

I know it’s not ideal, but can you still fly not in VR without crashes?

Unfortunately from the log this shows as a Vulkan Device Loss caused crash generated by X-Plane itself, rather than the CL-650’s systems plugin directly. There is not much, if anything, we can do to troubleshoot this further. If you reported this to Laminar Research they would just advise you to use OpenGL, as unfortunately they have stopped investigating these crashes in X-Plane 11 many months ago. (We all hope X-Plane 12 will be more resistant.) The other things you can try are to (a) make sure your GPU drivers are up to date; (b) lighten the load on the GPU by reducing the graphics settings in X-Plane; and (c) stop running any other applications alongside X-Plane (web browsers, flight trackers such as Volanta, etc., are all GPU accelerated these days and can interfere with X-Plane access to the GPU).