Pils

Yes, because I only set that up to test for this thread, but it worked fine.

I’m curious, why would you need both?

You may want to move your Windows page file to the drive with more space, that’ll give your PC a bit more room to handle memory issues. https://www.tomshardware.com/news/how-to-manage-virtual-memory-pagefile-windows-10,36929.html

They’re talking about the CL-650’s systems, specifically (which don’t have Librain integrated at this time). But I really don’t understand how they came to that conclusion from the logs you posted here (assuming they saw the same ones), but I’m no expert. You may have to just not fly in VR, sad to say. Just curious, what does the “--force_vr” command line option do exactly?

Technically you gain a button because two of the handles can have red A/T disconnect buttons on the side, as this is the configuration for the A330/340/350/380.

Jelly! I was told I have to wait 2 months.

Thank you for your help!

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?