frank_m

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.

Of course you have the OIS also on XBox.

Where have you changed the fuel? In the OIS Loadsheet page? There you have to adjust the fuel, not in the MSFS EFB.

How often has it to be repeated? Cabins are not supported any more!

I'm not sure regarding D-ATIS, but CPDLC is working (as far as BATC supports it).

No problem here. Maybe you should show screenshots, what you have done: SimAppPro settings and profiles (in particular the operating mode of the throttle), Windows calibration, control assignment in the MSFS (Axis and buttons) and calibration in the plane (including the settings like "Reverser on Axis"). Be aware: ALL mentioned items are important, and we need information from all of them.

Now you got it. There are several planes not allowing to set the simrate - Fenix is only one example. And others reduce the rate even if they allow it to be set using the standard key bindings - FBW for example. Good and complex planes ensure the simrate is small enough to guarantee a flawless simulation. This is usual.

Yes. Please read #2, and you'll have the answer. It is not possible to enter 2x or 4x manually. You have to use the OIS.

It is still the same reason as in the few hundred threads before asking the same question: Cabin Packs or incompatible addons like liveries. Details in the other threads.