frank_m

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.

In the same way as in all other planes. You have to assign controls for the sim rate of course.

You have to configure the Simrate 2x and 4x in the OIS. At Simrate 4x you can enter 8x or 16x manually using configured hotkeys.

That is most likely a problem of your control configuration: Joysticks, pedals and so on.

That is a typical problem if the hardware is overwhelmed with SimRate 4x.

That is most likely due to the planned approach. Then you are using outdated navdata from 2023.

There is a setting in the OIS for automatic remove of the covers. Alternatively you map a key in MSFS for "Quick Pre-Flight Control". I have mapped it to Shift+C, so the Pre-Flight control is performed automatically as soon as I enter the cockpit - and all covers are removed, not only the engine covers.

You can do it "half by half" in an iterative way. Divide your add-ons into two halves and test which of the two halves is causing the problem. Then divide the problematic half into two halves again and test again to see which one is causing the problem. Divide it into two halves again and continue in this manner. Even with 250 add-ons you need only 8 steps to identify the bad one.

You have incompatible Liveries, Cabin Packs or other addons installed. It is sufficient if they are installed, you do not even have to use them. Try again with empty Community folder.

Yes, if it's new information. But why spread it across the whole forum? Developers have to search dozens of threads to collect information and get a complete view. Wouldn't it make more sense to have all the information in one thread? This is particularly important if the information comes from the same person. Whether these threads make sense if there is no new information and it is always the same question is something you can decide for yourself. Every forum I know has the following rule: Use the search function before you start a new thread. There is a reason for this. What conclusions can be drawn about the reported bugs if the thread creators can't even follow the simplest rules?

The issue is known, there are plenty of statements from the team. It does not help, if always the same people are opening new threads.