Pils

You need to reduce the brightness of cockpit displays to minimum during night times.

The purpose served was to inform you that X-Aviation does not preannouce sales in my experience. However, they had one last year.

https://discord.gg/aUsQPKN32

You'll have to wait and see!

That is my understanding of the situation, yes. But I don't speak for X-Aviation.

You are free to, however it won't be supported by X-Aviation. Maybe there's no license/agreement to do so, we don't know, you can't just assume there's nothing other than technical reasons at play. Regardless, X-Aviation have decided that removing Gizmo completely is a better long term solution. I don't see this changing.

I refer you to the above.

Apple Silicon support will come when an addon is updated to remove the use of Gizmo completely. Not any other way. (And if it's never updated, it'll never have support.)

https://forums.x-pilot.com/settings/account-security/

This means that you've signed into X-Aviation using a different account on this computer ("machine") in the past. Each machine can only be registered with ONE account. This often happens when people have shared accounts with each other, which is EXPRESSLY against the terms and conditions of the store, and which they consider to be software piracy. Only X-Aviation Support can help at https://support.x-aviation.com/index.php?a=add.

Yes, V1.8 still runs on XP11, with some limitations. However, consider that X-Plane 11 is an End-of-Life platform, no updates will be made to it by the vendor (Laminar), no bug fixes, no new features, nothing. The CL650 will stay compatible where possible, but do not expect it to be fully featured at the level of X-Plane 12 version. E.g. There will never be a functional weather radar for XP11. If you computer has the performance for XP12 it's long passed time to move on from 11.

Have you asked Laminar's X-Plane Support? The GNSes are their code.

https://support.x-aviation.com/index.php?a=add

They are encoded the same as the default CDU: https://developer.x-plane.com/article/datarefs-for-the-cdu-screen/

Some difference on the thrust limit page input. Check on PERF - THRUST LIMIT page that you have the same OAT entered on both FMSes.

There’s no setting. Nose wheel axis mapping is auto-detected, and IIRC defaults to Yaw until dedicated NWS is used.

One day. Not a high priority.

This isn't an XPilot forum but some people use 123.45 as a shared air-to-air frequency.

I’m sorry you’re having problems, but this is not an xPilot support forum. You can access their Discord to talk to their developers and users, which might be more fruitful. https://docs.xpilot-project.org

You have not completed a crucial part of the checklist:

If you're expecting a "fast" reply, yes. This forum is primarily for support done by the community, not necessarily the developers. In this case, Hot Start has a Discord server for direct developer support: https://discord.gg/T7F8MmmD

Can you indicate on the screenshot exactly what button you pushed to start the engine, please? Also, please include a screenshot of the multi-function display.

The one on the glare shield? The ATS mode depends on what vertical AFCS (autopilot) mode is active (on FMA).

https://discord.gg/kPhA2YsVJ