Farlis

Same here.

Can confirm. Same bug here. Only when you set the cruise altituted in the MCP will it go into clb mode, anything below it it stays in descend mode, for whatever reason. And this isn't a "minor" issue. It's a MAJOR bug. No it does not. When you reenter the cruise altituted again it just blanks the entry and you remain in DES mode.

Another thing I noticed now twice is that upon climbout the aircraft deletes the cruise flightlevel and goes into descend mode. As a result you end up in open climb and have a green dot with the number 99 at the top of the altitude band indicating the flightpath vector. This was on the TULNA8C SID out of VOBL. Later in the climb it returned to normal. Very odd.

There is a 4th Option: In SimApp Pro simply push the "Reset Default Configuration" button.

I vote to give @Der Michel a free copy of the A380 upon release, for all his efforts in finding and squashing bugs and innaccuracies of the current Ini Airbus Fleet.

Not true. It works on both the A340 and the A350.

Most likely cause is that the ISA temperature is too high. Sometimes the sim gets erroneous upper temperatures and then your engines will fail to produce enough power.

No they don't. They go to the forward crew rest but they most certainly don't walk through the cabin. Security reasons. And Merry Christmas to you as well.

Just use this https://de.flightsim.to/file/100679/ini-cabins-compatibility-mod and you get your cabin packs back. Holy hyperbole Batman! You fly an aircraft from the Cabin? I though this is about being a pilot and not a passenger.

Most likely. It already happened back in FSX when I was using Active Sky. Sometimes the data delivered to the weather engine is simply faulty.

I'm confused. Autothrottle engages the second you push the thrust lever pass the clb detend. On the ground.

Maybe using the forum search function would have given you the results? Anyway, the workaround is to wait a bit longer before entering the aircraft after you initially spawn in walk around mode. Let the load settle first. So waiting 10-15 seconds before pressinc crlt-c and spawing into the flightdeck should help.

Then it's probably something on your set up. I see it in neither aircraft.

You both have a keybinding somewhere that moves the ailerons. Most likely because you use the default keyboard profile. So everytime you use the w or d key to move the camera you can accidently move the aileron.

Is BeyondATC's D-Atis already supported with v1.0.19? Or is that to come in the next update?