2 hours ago, Skycowboy said:

I noticed the same Problem. Yesterday I updated the SimAppPro to Version 1.16.88 and proceeded with Firmware-

Updates for MCDU-Cpt (v1.04), MCDU-Co (v1.04) and btw.ECAM (v1.01). After loading MSFS2024 and iniBuilds A340-300

respectively restart SimAppPro all was working fine, that means : FCU, EFIS 2x, MCDU (2x), ECAM and AGP.

Yep, all working now after latest SimApp update. 

5 hours ago, Lude2Envy said:

Did you install the 340 from the Marketplace or the iniManager? When I had mine installed through the Marketplace, I had it actually "installed" instead of "streamed." If there were updates I had to manually update it. Since they now offer it through the iniManager, I uninstalled it from the Marketplace and now have it installed through the manager. Just a thought in case you're in a similar position and running an older version of the 340. Try running SimAppPro as administrator too. 

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. 

13 hours ago, Lude2Envy said:

I only have one MCDU so I can't confirm or deny that you can use two units with the 340, but can you confirm that you have one MCDU set to CA and the other set to FO in SimAppPro? 

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!

 

Are the normal checklists, correct? Airbus changed the checklists some time ago. 

 

 

Don't get me wrong, I do think your team has done an incredible job so far on the A350. It is a great plane with a huge potential. With updates and tweaks this has the potential to be an incredible product. 

I have not tested this airplane in depth and I have never flown a real A350. A see a lot of the same 'issues' as the posters above. Lots of minor things, when adding them all up, makes a difference. 

Brake temps as an example, Huge differences normally on the A380 on individual wheel brakes. One brake can be 120C while another can be 270c etc. Depending on direction of turn, brake wear etc. Things seem a bit too pre-calculated. This is just a minor thing though.

The normal checklists, On the A380 with latest Batch 7 Airbus changed the Checklists (And a bunch of other things). Cockpit Preparation Checklist added and After takeoff Checklist removed etc. Not sure if this was incorporated into the A350 as well?.

 

Keep up the great work. I am excited to see what the Inibuild A350 future brings. 

As a A380 pilot, lots of similarities to the A350. Just not as modern, I have to say after testing this airplane. I am honestly disappointed. It feels like the numbers are scripted. Pre-loaded. Not fluid with the conditions. Potential is there, but in this state it's a toy and a game. Nowhere close to the real A350 in terms of accuracy and precision. This aircraft needs a lot of work. Surprised this version passed the so called A350 pilots testing this thing. I would never signed off on this avionics wise in terms of a 'study level' realistic simulation of the A350. Its a decent product, but needs a lot of work to reach the level of accuracy and precision. 

Just did a quick flight. Swapped active to SEC 1. Returned to departure airport. BTV setup.  Plan, zoom and select. I was able to select the runway, unable to select runway exit after the wet line. Hence BTV not working. Am I missing something? 

I am a A380 pilot, we always select an intersection (magenta line ) after the wet line. I could not get that to work. Am i missing something? Nav also did not tune to diversion airport. No ils ident. 

I get a fair bit of shimmering with this airport. Secondly, you missed the large car park garage on the left side of the Emirates Group Headquarters building. There are two huge car parks on either side of the EGHQ building. You got one. 

Hi,

Minor thing.

I have seen on several occasions where the Altitude prediction (Yellow Banana) is not aligned with the current track. If going direct to a waypoint the Altitude Prediction symbol is offset and not directly over the track line. 

Christian

I have to say it, hate saying it. PMDG, Fenix and Maddog have been solid. PMDG a bit hesitant on Hoppie but they bit scared of progress and cash flow, I guess.

IniBuilds somehow manage to go back in time on latest A300 update. Latest update, gents.... you can do better. I do like the A300, you got my money. Shape up, sharpen up and test before fly. The last update is an indication of lack testing and communication. Guys, come on. U can do better. Tad embarrassing. 

 

Actually, I mentioned 2 issues😜. NAV mode not re-engaging and DIR-TO function. 

DIR TO not working for me after latest update. When in HDG reverting to back to NAV not working. Impossible to get the aircraft back into Nav mode. Aircraft just flies set Heading/Direction. DIR TO not working in terms of Nav mode. 

Christian