Winwings MCDU Progress

[Eurosky]

Same here. WinWing MCDU froze up after some time. MCDU in the plane was working, but MCDU on WinWing froze up.

[KSJ]

I have also now noticed this. To reset, I am having luck unplugging the MCDU, then killing Simappro, then restarting Simappro, then reattaching the MCDU. I haven't had to do this again for the rest of the flight. Just for refererence I'm also running the L+R EFIS and the FCU.

[janiTTor]

30 minutes ago, KSJ said:

I have also now noticed this. To reset, I am having luck unplugging the MCDU, then killing Simappro, then restarting Simappro, then reattaching the MCDU. I haven't had to do this again for the rest of the flight. Just for refererence I'm also running the L+R EFIS and the FCU.

Nice to hear that you found a workaround. I’ll wait for A340 v1.0.13 before starting the next long haul flight. Because I don’t want to skip the flight in APLv2 I will fly it with the A350. The 340 is going back to the hangar for maintenance meanwhile 🙃

[Marcocessna84]

Make sure your SIm path and fleet are on the  link address. I had the same issue and was adviced per winwing to make sure the path are the same. But my MCDU freezes up after a while when flying with the A340

[KSJ]

The suggestion would be relevant if the MCDU was not connecting at all. That's not what we're discussing.

[Arty57]

Howdy iniBuilds.  When do you see the freezing issue with WNWING MCDU being addressed and resolved?  WINWING has issued two updates.  Ini has acknowledged that the ball is now in their court and a software change is needed for the 340 to be fully functional with the WINWING MCDU ( and FCU/EFIS).  Having expensive hardware designed for use with specific aircraft is wonderful but when that is not possible due to issues with that specific aircraft the magic is gone and the specific aircraft goes into the hanger.  Can ini please provide a timeline for resolution?

Please and Thank You

-A

[KSJ]

I'm working this issue directly with Winwing. Note that I am not part of Inibuilds. With regard to Inibuilds, my experience has been that they are very responsive to this Forum and most likely already are working this issue as well. Patience is the order of the day.

[KSJ]

Looks like Winwing has released update Simapp 1.16.69. I tried it this morning and it seems to be promising. No freeze in a short 0.8 hr flight. Suggest we all update it and report here.

[KSJ]

On 10/31/2025 at 12:11 AM, janiTTor said:

Now that I’ve had a little more time for testing I’ve tried DLH422 EDDF-KBOS. After about 100 nm the MCDU didn’t no longer respond. I restarted SIMAppPro. After the restart the Buttons worked again, but not the Display. Another 300 nm later I’ve got a WASM crash. All displays frozen, not possible to disable the AP and the plane no longer followed the Route. In my opinion the A340 is not seriously usable with or without WW MCDU. Back to Fenix again.

Agree - same happened to me & I have reported same to WW. BTW, when Inibuilds puts out a new A/C it's always a good idea to delete the WASM folder. Flight sim will rebuild it on next load.

[janiTTor]

Hi all,

today i've started the flight back from KBOS to EDDF (DLH423) with SimAppPro 1.16.69_beta on board of the A340 1.02 in MSFS 2024 SU3. First after about an hour, the MCDU was frozen again. With KSJs workarround to restart the SimApp and restart the MCDU (plug out an in the USB connector) it worked again but after about 5 hours of flight near the european coast, what do you think what happened? Right, all the displays and buttons in the virtual cockpit frozen and the plane (i'm not sure to call it a plane) goes straight foreward --> WASM Crash. That is very timeconsuming and disapointing. I think, that was my last try with that piece of software. The idea to use the autosave feature kills the immersion. If your software is so bad that you think you need that kind of feature you know everything you need to know.

Bye bye inibuilds A343

Best wishes Kai

[Arty57]

Team lnibuilds. It appears that the long awaited ver 1.03 which ini themselves alluded would cure the MDCU / WINWING freezes has indeed cured the freezing BY BREAKING THE MDCU ONCE AGAIN (black screens once more).IniBuilds handling of this issue has brought it no glory, only shame.  This is a very bad joke and nobody is laughing.

-A

EDIT: Just discovered that EFB pushback appears broken also. So sad. So much potential.  So much missed.  Back in the hanger for me again and btw I own EVERY ini plane made for 2020 and 2024. I used to unreservedly endorse your products. No more.  If asked I will recommend potential buyers avoid your aircraft products until such time that ini demonstrates some notable improvements in Quality Control and Release Management.

Edited Friday at 02:43 AM by Arty57

[janiTTor]

Cause I can’t leave it, I’ve tried another flight DLH423 with A340 1.0.3 and SimAppPro .70 (.69 scrambled the font is on the MCDU with Fenix) and this is what I experienced.
After about 3h of flight (2000nm to EDDF) the MCDU freezes again. After about 5h of flight the WASM crashes again while I was in bed. When I came back to the Sim the plane was almost half way back to KBOS 🤣. This time I used the Autosave feature. It worked, but saving a flight and revert back is killing the immersion.

If I had more time, I would test more and would use the Devmode, but 3 to 5 hours testflights are not possible.

Conclusion:

Ini A340 1.0.3 with SimAppPro 1.16.70 still not working (for long haul flights).

[Farlis]

4 hours ago, janiTTor said:

It worked, but saving a flight and revert back is killing the immersion.

And flying long haul alone and letting the aircraft unsupervised isn't?

[Astro_Liam]

How are you all even getting your MCDU to work in the first place. Mine just loads with a blank screen and the buttons don’t seem to do anything. On latest aircraft update and latest sim app 

[Ruivers2]

 

Now on simapp version 1.16.70_Beta, A340 version 1.03, with several days of communication with Winwing, no solution on the black MCDU monitor.

 

-Rune-

[KSJ]

1 hour ago, Ruivers2 said:

 

Now on simapp version 1.16.70_Beta, A340 version 1.03, with several days of communication with Winwing, no solution on the black MCDU monitor.

 

-Rune-

Haven't seen the black screen since 1.02. Suggest you delete your cache(s) in flight sim and also delete your wasm folder and let flight sim rebuild them.

[Ruivers2]

On 11/8/2025 at 8:28 PM, KSJ said:

Haven't seen the black screen since 1.02. Suggest you delete your cache(s) in flight sim and also delete your wasm folder and let flight sim rebuild them.

Thank you. I got it all sorted out. I am the only one to blame, as I made a mistake in the USER DATA PATH in Simapp settings. All good now.

-Rune-