frank_m

This is most likely a wrong configuration in the controls. How are Rudder and Tiller Axes configured, and what is in the EFB set regarding Rudder, Tiller and Auto Disconnect? Please show screenshots.

Are you using Navigraph Navdata in the Simulator? Then it is most likely the package_order_hint problem. There was a similar issue a few days ago. Please look at the Navigraph Forum for details. Long story short: you are using old MSFS2020 addons lacking for the package_order_hint entry in the manifest.json. This disturbs other addons, although the critical addon itself works flawlessly.

For me it works perfect in SU5. Have you analysed the CTD in the Windows logs?

Yes, EVERY single addon. As I said, an addon don't has to be active or in use. It is sufficient if it is available in the community folder.

No, it is not the Navigraph integration. It is the "package_order_hint" problem. You have at least one addon not compatible with the FS2024 in your community folder. It has no package_order_hint entry in its manifest.json. This leads to addons sorted and applied in an incorrect order, and the Navigraph navdata does not work like expected. The addon don't has to be active or used in the current flight, it is sufficient, if it is in the community folder. Also the addon itself works flawlessly, but it distubs others. There are many and long threads in the Navigraph forum dealing with this problem. Long story short: You have to ensure, all your addons have an appropriate package_order_hint entry. Either by using only addons released for FS2024 or by adding the entry yourself.

This is a WASM Crash. You should file a report in the corresponding thread.

Did you test the package_order_hint Problem?

Can't confirm. The notification disappears as soon as you have read the messages.

Please test it without the Navigraph Navdata Addons (remove both!). If it works, it is most likely the "package_order_hint" problem. At least the symptoms match exactly.

Yeah, hot off the press: When it's ready. Don't tell anyone!

Which airport? I did a flight EDDF -> EDDB 2 hours ago with 1.7.21.0, and it was perfect.

Which problems? Used it a few minutes ago flawlessly. Boarding, Fuelling, Catering, Cargo.

Oh, you can easily find that out by reading the relevant forums.

Yes. Switch cockpit interactions to legacy.

This is a simulator setting and required in order to be able to push and pull the cockpit buttons.

Reading some of the English threads in this forum will show you the solution: remove incompatible addons and liveries. The question pops up once a week (this was a hint for the search function).

No problems here, did it an hour ago. Sure you pulled the knop for switching to STD and pushed the knob for switching to QNH? Sure the cockpit interaction system is "legacy"?

The problem of this thread is solved for a long time already.

You have waited 15 Minutes for compiling the WASM code? The installation is clean? Try to uninstall and reinstall the plane. And cleanup the WASM folder of the plane.

This is a typical problem if multiple sceneries are active.

I use Mobiflight instead of the SimAppPro, and it works perfect. If you are using SimAppPro you have to wait for an update from Winctrl.

You can read the Messages in the ATC Com section. Afterwards the ECAM Message is gone.

Can't confirm, works as usual.

- Uninstall and re-install - remove incompatible addons.

But this is the case for a lot of versions, and it is definitely the better way, since you can activate and deactivate the items before they disappear finally. So it is a feature, not a bug.