Pils

The developer will look at ways to reduce this risk. In the meantime don’t park at airliner stands.

Should be fixed in an upcoming update.

To be clear manual entry didn’t work? Please also provide logs.

Yes. You can’t. It’s true. And that is very strong language for a minor inconvenience. However, feedback will be passed on.

They’re buttons too.

Yes, that’s how this feature works. Think of the popups as being all on a single “layer” and when you hide them the layer is hidden, as such when you click another popup it’s added to the layer and the whole layer is shown again. Having multiple layers/groups of popups would make the implementation a whole lot more complicated. It may get more sophisticated in the future, or it may not.

Yes, a plain vanilla X-Plane install using OpenGL is what Laminar would suggest I'm sure. If you only select one of the smaller regions to install global scenery for the size shouldn't be too large. Unfortunately, Vulkan device loss errors are a known problem with XP's Vulkan engine, however LR stopped debugging the resultant X-Plane 11 crash reports from users many months ago. And as there will be no more bug fixes for 11, our only hope is that the situation is improved in XP 12 because OpenGL will no longer be an option!

Yes. Preferably over more than 60 seconds so we can see a long term trend from start of flight to crash. I’m not sure if Task Manager can do that though?

Thank you. What is more useful is the memory usage graph so we can see a trend.

There is apparently no way to detect that the IVAO pilot client is online therefore the realistic altimetry, which is the cause of the altimeter under reading in your case, is always enabled. I believe there is a request with the Altitude developers to provide a mechanism. If you lend your voice to this request then it might help hasten its implementation. If/when this means exists then a feature request will be submitted to the CL-650 developer. Thanks.

Can you confirm that Task Manager or your local OS equivalent shows X-Plane is the source of the RAM usage? Screenshots showing main memory, page file, and GPU usage periodically would be useful. Thanks.

Yes.

Ok, I see where the confusion comes from. That doesn’t meant 3 units of stab (pitch) trim, it means set the 3 types of trim, i.e. pitch, yaw, and roll.

Ok, thanks for the extra info. I meant for the next flights you do. As I said, we need more detailed information.

Can you screenshot the checklist you referring to, please? Trim would usually be roughly 5-6 units for average weights.

We need more to go on. All the log shows is the CL-650 asked the OS for more memory and was told NO. Can you post details of routes, altitudes, etc. Also screenshots of Task Manager showing page file and main memory usage total, by process, as well as GPU VRAM usage, at various times before the crash. Please also try running the sim without any custom scenery, only stock airports/mesh. Thanks.

How many units of pitch trim are you using?

Those datarefs are for the ALT button state, not the altitude on the EFIS. You can’t find them because they don’t exist. The feature request is open already. I will post updates to the following thread. Thank you for trying to help the product better!

Do you recall when it switched over to green needles? Was it before CANES?

This sounds like a Configurator/Bridge problem, as you’ve indicated it works fine in X-Plane itself (which is what I use—I want to use the Configurator as little as possible because I find it to be quite a terrible user interface personally). In the X-Plane plugin SDK there are two ways to actuate commands, “CommandOnce” or “CommandBegin”/“CommandEnd”. The correct way is the latter, and this is what the CL-650 is expecting. This is important because it allows the aircraft systems plugin to know when you’re holding a key/button down and when it’s released, this is tied directly to the animations, for example. Sometimes hardware integration plugins default, or only support, the former which can cause issues like you’ve described. I don’t know this is the issue in this case but it’s a possibility. Is there a way to force the Configurator to use the Begin and End method if it’s not already to eliminate this as the cause?

That appears to be a good old X-Plane-caused crash.

Please attempt this linked solution, and then also other suggestions in this thread if it didn’t work.

Local time must be set manually.

Do you know exactly how SmartCARS is making the sim pause? Just so you know the add-on has built-in support for "pause at TOD", maybe use that in the meantime?

Unfortunately that is not the reason for the crash, that is a “red herring” as the saying goes. Specifically it’s a known issue that has no real impact on the operation of the plane. This is why we ask each user to report their crashes individually and with full logs attached. Thank you for your understanding, and future cooperation.