I just experienced a new bug concerning the ECAM which I think was NOT present on older versions:

On the real Aircraft, when you are on an ECAM system page (for exampe Fuel) and press the key for THIS system page again on the ECAM control panel (so yes, a second push on "fuel"), you return from the system page to the basic ECAM page (on ground: Doors / in flight: Cruise). I think this worked on older versions and for sure works like this on the A350 (just checked it).

Now you have to press the ECAM pushbutton several times, to return to the "basic" page.

I hope you understand my problem and have look at it... 😄

regards,

Benni Thill

Step climbs are still not being executed correctly in automatic mode.

I've only done 2 flights so far, but both have had the same issue, about 1-2hrs after departure in the cruise, I notice all of a sudden that the MCDU's are frozen with no way to input or change anything, the aircraft also locks me out of changing any autopilot inputs and goes into what I assume must be heading hold, as it drifts off the track in a straight line for eternity. Not sure if anyone else is having this issue or not, but I'm concerned to see it twice in a row on my first two flight attempts!

Tried to fly the A340 today. When loading the a340 in, the game continuously crashed. Tried at different airports, same thing. On Xbox. Loading in other aircraft, like the a350 was perfectly normal

When applying the update for the A340 terrain under the ini app : Failed to verify the integrity and noted the path is correctly. I have tried to reinstall this multiple times directly from the ini app and in microsoft store for the MSFS2024 version and this had not resolved the matter. Any suggestions or advise would be appreciative.


Warm Regards

I am getting a hung start on each engine everytime I get in the A340.

- All fuel pumps on, APU bleed ON, APU bleed pressure at engines 36psi, throttles idle, no hardware bindings for fuel control or engine starters.

The engines will start eventually but each one is hung and takes about 2 minutes each to become available.

Starting procedure at the time was 1 engine at a time 1>2>3>4.

Hardware connected is: WINCTRL  MCDU, WINCTRL ECAM, WINCTRL Throttle w/flaps/Speed Brake, Mini Cockpit MiniFCU, WINCTRL Ursa Minor Side Stick and BlackBird Controls Airbus tiller. 

I cant see any hardware interfering but I dont know what else it can be. I've flown the ini A340 many times before and never ran into this. I had to recover my PC recently and after reinstalling everything, now I get hung starts every single time.

When do you do power the aircraft the MCDUs go to its normal status page, but when you depower the aircraft, it stays on and on the same page, but its frozen.

SU 5 came out today alongside the 1.0.11 on Xbox Series X, and I have tried 5 different flights all of which resulted in a CTD.
The first 3 had a CTD during the loading into the airports, before even clicking “ready to fly”

The 4th came when trying to use the ATC, after setting up the flight, and was ready for pushback. 

Before every CTD i got the “Memory resources are getting low, disabling avionics to grant stability. Some settings may be lost due to this process” message. 
This has never happened before for me.

I am on SAP 1.16.75.  I am on a340-300 1.0.5.  All WINWING hardware has firmware checked and is current.  The symptom of this failure is as follows.  Initialize plane at gate on APU.  Enable SAP.  MCDU and FCU/EFIS come alive and function. Set fuel and weights via EFB and Simbrief. Flight Plan into MCDU via SOP.  When everything is set depart as normal.  Every flight at some point the MCDU freezes.  Screens locked. LSKs and buttons still function as can be seen on virtual cockpit MCDU. Only the physical MCDU is affected and only then the screen.  This usually occurs within the first ten minutes of flight, sometimes sooner, sometimes later.  When this happens a power cycle of my switched and powered USB3 8 port hub restores functionality of the MCDU and it operates without issue until the next occurrence at which time a power cycle is needed again.  Rinse and repeat throughout the entirety of the flight, two, three even five hours.  I have never once experienced a flight without an MCDU freeze and most flights are two or more.

As I type this I am engaged on a test flight KLAS to KBOS.  In the first 30 minutes of this five hour flight I have had two MCDU freezes.  The MCDU is the only component in the WINWING chain that is affected.  The virtual cockpit MCDU and physical FCU and EFIS continue to work as expected and all functions of those components are available.  I have Airbuses from other vendors, Fenix and FSL, that operate the same way (MCDU, FCU/EFIS via SAP) that have dozens of flights each, never once with a lockup or freeze. Only the iniBuilds a340 exhibits this consistent anomalous behavior and failures.  A solution is desired and requested.  Please assist.

-Braun T

I have no clue what has happened.

I like the A343 very much. Today I tried to use it with beyondATC. I've encountered the problem that I can't request WX: If I enter an ICAO code and send the request nothing happens. Also the WX on the EFB flight overview page can't be updated. 

So far have been doing traffic patterns and general handflying to get used to it. Great so far.

For some reason my Simbrief wont play nice. I have a unlimited account with Navigraph. Any help?

In most other payware aircraft I repeatedly tap the brakes (bound to a button on my joystick) to release them and roll to a nice slow speed, however this doesn't seem to work in the A340.

Also, not sure if it is related but on pressing the brakes during a taxi to slow down a little, I'm struggling not to get the aeroplane to stop dead. There seems to be a very fine line between slowing down and coming to a complete halt.

Thanks!
 

I am having an Issue with the Inibuilds A340 IRS initalization.
After a cold & dark startup, as soon as I switch on BAT and External Power, the MCDU already shows "Aircraft Position Invalid"
This happens before I align the IRS or interact with the MCDU in any way. The IRS Init page never shows "SET IRS POS" and alignment is not possible.

Because of this, LNAV probably doesnt work:
The ND displays the aircraft position, airport and route correctly and the programmed route is shown normally on the ND.
However, the aircraft does not follow the route and pulling or pushing the HDK/TRK knob does not engage Navigation.

Other aircraft (e.g. Fenix) work normally on the same system and airport.
I already tried reinstalling the Aircraft but still, no change.
Any help would be appreciated.

1 - Since the ALTN field on the INIT B/FUEL PRED page is blue, wasn´t I supposed to be able to change it?

2- The EXTRA/TIME field isn´t supposed to use the MIN DEST FOB page as reference instead of ALTN+FINAL?

SBBRSBEG_PDF_1774354130.ddbb62cb.pdf

Configuration: ZFW 172 to, Fuel 85 to, Cost Index 200

Starting with MTOW the airplane accelerates not to 250 kts, but to the green dot speed of 269 kts. Reaching the first flight level 320, the managed cruise speed is .805 Mach (at CI 200?).

At Opt FL 320 / Rec Max FL 348 I climb to FL 330. During the climb phase the airplane accelerates to Mach .82. Reaching cruise FL 330 the managed speed falls to Mach .799. The Rec Max FL jumps to 354.

At Opt FL 330 / Rec Max FL 361 I climb to FL 340. Again, during the climb phase the airplane accelerates to Mach .82. Reaching cruise FL 340 the managed speed falls to Mach .792. That is IAS 274 kts, near green dot speed 272 kts.

At Opt FL 340 / Rec Max FL 370 I climb to FL 350. Again, during the climb phase the airplane accelerates to Mach .82. Reaching cruise FL 350 the managed speed falls to Mach .786. Suddenly, the Opt FL falls to 325 and the Rec Max FL falls to 348, so I fly over Rec Max FL. The managed speed is now Mach .822.

From now the GW has to fall 26,6 tons until the Opt FL is 350 and the Rec Max FL is 375.

I think, there is a bug in the “air data”, especially in the flightlevels lower than 360.

Inibuilds A300 and A350 don´t have such discontinuities.

 Greetings from Germany

Franconia15

Hello all,

I noticed that switching the north ref to "true" doesn´t effect the DDRMI (right next to the button). However, as seen below, the switching seems to affect the DDRMI  in the real aircraft. The displayed courses slighty move in the same way as they do on the ND. 

Would be great to have that effect added 🙂