Pils

The log contains no useful crash information. Please remove all third party plugins except Gizmo64.plugin and try again.

That should probably always be zero for custom planes.

AMD GPU?

Still no API available in 12.

Glad it working. Thanks for the feedback.

Possibly it blocked the entire installation. Check the enforcement/protection history, and the size/contents of C:/Users/brian/Desktop/X-Plane 12/Aircraft/X-Aviation/CL650/plugins/systems/win_x64/systems.xpl. It should be over 22 megabytes.

Yes, without systems.xpl loading it's going to be broken. Something is wrong with your particular installation. But we have to figure out what. Do you have anti-virus software? P.S. You missed NavigraphSimlink and AFC_Bridge.

Please remove all third party plugins except Gizmo and try again. This’ll at least give a cleaner log.

No. They are incompatible due to both manipulating the camera. Tobii need to add a way to disable their system temporarily in the sim like X-Camera has.

As far as we know, common SOP is 200 kts, unless there's a (lower) speed restriction, either on SID or by ATC.

Or hit me up on Discord.

I don’t know how Spad works but if you tell me what you’re looking for I can look it up. However everything should be in DRE.

No. If the real plane has no data for a bleed configuration we aren't going to invent it.

This is the simulator itself causing the crash so would need to report to Laminar Research. However make sure sound is enabled in X-Plane and Windows, and the master volume slider in X-Plane isn’t zero.

Please post your Log.txt from a session where you have issues. Also please make sure you're using the numeric pilot ID for SimBrief configuration.

I assume you didn't buy it twice, because X-Plane 12 was a free update! But, as far as you report goes, I'm guessing you're on an Apple Silicon-based Mac...

This all comes down to X-Plane's VRAM management system. It believes you are running so low on VRAM that it has to make all textures lower resolution. Assuming you have reasonable amounts of VRAM on your GPU (at least 4 GB), you can/should report this as a bug to Laminar Research. The next version (V1.8) is also going to attempt to workaround this, but there's no estimate for when that will be released. In the mean time you can try reducing the texture quality setting so your VRAM is not under as much pressure.

Did you have an N1 thrust limit available and active? TO or TGT?

Disable X-Camera or similar (TrackIR, Tobii, etc.) if used.

I don’t believe there’s been an intentional change in behaviour. I have a feeling that it’ll only spawn you back in the cockpit once engines are running? I’ll have to confirm with the developer, but at least the button should change from Enter FBO to Let’s Fly (or something like that).

There’s been no change to this functionality. Do you have a screenshot of the airframe manager?

Try dragging display 3 so its bottom edge is level with display 1. And don't use anything but display 1 in X-Plane. If you want an MFD on a secondary monitor, use a pop out (native window).

The machines are not product specific, they are shared, and tied to your x-aviation account, as a whole.

Use the X-Plane default autopilot commands, they have "auto-repeat".

A few posts up..