Eurosky

Yep, all working now after latest SimApp update.

Installed it from the IniManager. Deleted in the Marketplace. SimAPP pro in administrator mode had no effect either. It's strange because everything works just fine in the Fenix with the dual MCDU setup. I honestly have no idea how to get both MCDUs to work with the A340.

IniSteave, I cannot get it working with both WinWing MCDUs connected. Got it set up independently as you described in the SimApp Pro. I am on the latest firmware and SimApp version. With both connected none of my Winwing products work. When I disconnect FO MCDU, all good. I cannot understand how you guys got both working.

I can confirm that. With both MCDUs connected and correctly configured, none of my Winwing products work (I have pretty much all of them). As soon as I disconnect the FO MCDU, everything comes back to life. Worth mentioning that everything connected from Winwing works flawlessly on the Fenix A320.

I have a dual WinWing MCDU setup. Capt & Fo. With both MCDUs active none of my WinWing products will work. Disabling/unplugging one MCDU and ops normal. I contacted WinWing support about this. This is the answer I got from WinWing support in regard to dual MCDU support for the A340: Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side. Please wait for the plane model manufacturer to update the plane.

So are you guys getting the Wingwing FCU, 32 AGP, MCDU etc to work with the Ini A340? I can't get anything to light up. Using latest SimAppPro. Everything working with the Fenix but nothing from Winwing works on the latest Ini A340 on my end. Found the problem. I have a dual MCDU setup (Capt & FO). With a dual MCDU setup nothing will work. I assume dual MCDU is not supported. Disabling/unplugging one MCDU and ops normal. This is the answer i got from WinWing support in regard to dual MCDU support: Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side. Please wait for the plane model manufacturer to update the plane.

Strange thing recently happening. Latest MSFS 2024 beta and lates A340 build. Every time I try to load up a flight with EIS1 I get CTD. It loads up fine with EIS2. Cleared WASM and reinstalled the plane. Only CTD with this plane. All other planes working just fine. Strange indeed. Any suggestions?

I do love the feel and the look of the A343. I do appreciate the updates. Did a nice trip to EDDF yesterday and as soon as I approached position Kerax on the Kerax5A arrival, the immersion and enjoyment was swiftly over. The ND was painting a nice picture of a slalom track on the arrival. Still got some work to do with this airplane.

EFB - MY FLIGHT - IMPORT FROM SIMBRIEF. ERROR: Instance was null. Any suggestions?

Did the restore default configuration. Any fix to get the Winwing MCDU display to work?

Having access to the aircraft tablet on your own personal device like an Ipad would be very helpful. Perhaps similar setup like the Fenix A320. Christian

How did you resolve it? Mine is still black after updates.

The biggest A340 problem is the Phoenix A320. Flying the Ini A340 after flying the Phoenix A320 is like trying to sing after Sinatra. The bar is very high. Dropping a product without offset, non-existing acars, no etp, time markers etc. So many things are lacking. Center Mcdu not working. It is a long-haul aircraft. I honestly don't think a single wide body Airbus long haul aircraft has ever been produced without the center MCDU configured and working. Potential indeed, These things are a minimum in the 2025 payware environment. Get the managed descent sorted and above items added. Then you are singing.

When flying on Vatsim, proceed direct to a point is an issue. The direct to function works borderline intermittently. Takes many tries to get it working. FS2020.

The A350 is in many ways a switch in FS simulation. Going from the solid, old-school aircraft to a seriously modern sophisticated airliner. Difficult to simulate and replicate. I am mighty impressed by the Inibuild team. Yes, there will be teething problems initially. Feedback and information will assist in enhancing this product. The FMS on the real thing has over 70 pages, they got most of them working. That by itself is impressive. With time, feedback from the community and tweaks will undoubtedly mark this as one of the best and advanced products ever created for MSFS. Keep up the good work Inibuild. Tweak it, listen to the feedback and make this thing shine. If you are able to go the extra mile, syncing the ECAM to the FCOM level 2/3 notes on the OIT and the TOPA (Performance calculator). Next level indeed, as this is one of the many features of the A350/A380 that makes it different and unique. OPS Library (FCOM/FCTM, FCI, Bulletins, MEL) etc is indeed vital and used on a daily basis. Flying an Airbus is an exercise of manual searching, knowledge and comprehension. MSFS operational MELs addition to the TOPA would be just like the real thing. (Very rear for an Airbus to push without an MEL). System resets, pretty much a daily occurrence and done with FCOM/FCI guidance, hence the need for the OPS Library. The addition of the Loadsheet and refueling application to the OIT would be next. Trying to accurately simulate an Airbus A350 is a big ask. Amazing job Inibuild!