According last Dev UPDATE ‘‘Is not repro since december’’ is other evidence then DevCom from Microsoft and Asobo Dev team have misscomunication …
This bug still repro with the hotfix before holiday patch, but a fix is ready to deploy since mid december but is only available with SU1 According SDK Team
so agreed, A300.300 dont work problems every time here…
As the OP mentioned correctly, the problem of freezing MCDU/PFD etc. already existed in FS2020 and was carried over to 2024.
I think it started when the 320V2 was introduced, but maybe I did just not fly them enough before.
Meanwhile I had it in 320, 330, A400M at least
Very frustrating because it ruins the complete flight.
And what angers me most meanwhile: it still seems to be not officially logged as bug! In spite of reports all over the forum 
Asobo/WT not use WASM on own aircraft … is full JS … (this reason performance suck)
Also, inibuild down use avionic suite from WT …
I would think WASM would perform worse than JS… why do you say JS causes performance to suck? Are you a programmer with knowledge of the difference between the two?
because C++/WASM have a better performence then JS, Compiled vs Interpreted language …
Do you happen to remember the threads where you found this info? I’ve been searching for it but didn’t find the source just yet, thanks!
Just got out of quickly testing my use-case of the inibuilds A320 v2 with the SU1 beta. Issue of freezing on exiting the mission seems to be fixed, I was able to get back to the menu without any freeze 
Thy would be great.
But please note that this thread is not about the freeze on exit.
It is about freezing MCDU etc. during flight.
I did two flights recently, one in A333 and another in A32N. A333 before installing SU1, A32N after. In both cases the plane stopped working during approach. All displays froze, cockpit become unresponsive, the animation was there but pressing buttons and moving levers didn’t do anything. The only way to interact with the plane was using HOTAS. It was responsive to joystick movements, and I was able to extend gears for landing using buttons on my throttle.
How people are able to fly these planes? For me they fail in almost every other flight.
Give the Beta a shot, this has given me very promising results so far with the ini airliners, and I’m on Series S. I basically couldn’t finish a flight into a larger airport on them, it worked today!
I am on SU1 beta, as I mentioned earlier. iniBuilds planes still go nuts during approach.
Inibuilds A320s don’t work very good at all for me, They dp lock up later but aside from that it just takes way tp long to program the MCDU and flying it with autopilot is terrible. I keep going up and down with master caution warnings and chirps with the Autopilot. I see on Youtube people are able to fly this but I sure don’t have much luck. These are the issues that I am having:
1 Setting Altitude
2. Setting Airspeed
3. Programming MCDU
4. Plane keeps going up 6000ft and down 6000ft a min. It’s seems like I can;t control the plane without or with autopilot.
Am I missing something? I am thinking seriously about getting Fenix as a trial for MSFS 2024 and seeing if that works any better than inibuilds.
Thank you,
Kurt Jungwirth
Hi Kurt,
this all sounds really strange. I’ve never experienced these problems and there are many Youtube videos of people flying those airplanes without any issues. In fact I don’t have any problems flying them in FS24 and I find them pretty good given they’re free airplanes (especially A400M and A330). The only issue is the simulator freezing when quitting a flight, but that’s Asobo issue and AFAIK it’s fixed in SU1 beta.
Are you sure there’s no controller/addon conflict or just plain operator errors?
Go ahead. I bought the Fenix A320 about week or so ago and I have no regrets. It’s way better than the iniBuilds ever was back in FS20, and back then was flying it a lot before switching to the FlyByWire A32nx, but the Fenix is even better, just get the EFB SimBrief plugin and enjoy. Remember only to go to the MCDU first time and calibre the axis for throttles, flaps and speedbrake. I’m using the Thrustmaster Airbus Captain Pack, and Logitech switch panel. After solving initial issues (had to remove entirely and reinstall Fenix all together) offers great experience and everything works perfectly.
Fenix works flawlessly in FS2024. It’s the plane that keeps me playing this game, otherwise I’d be still flying in FS2020. If you like A320, buying Fenix is a no-brainer. One of the best addons ever made for MSFS.
Hello. I only use keyboard and mouse right now and I do plan on gettting other supplies to fly MSFS2024 but that’s all I have right now. I can control the cessna 182 though with the keyboard but when it comes to airliners I must be doing something wrong. For auto pilot I use the mouse and it tells me what to do but it doesn’t activate anything and all i get is chirps and master caution warnings with the A320neo I did fly a little with the A330 though but the throttle was pretty sensitive in my experience. I guess I will have to study the YT again but I sure wish MSFS came with lessens with flying the autopilot and have PDF readme files for each plane in it. It sure would be helpful. Another thing is I wonder if I have a corrupted installation because I had downloaded on the MSFS website with a wifi connection and not the ethernet cat 8 cable that I have now. I also checked my library with MSFS 2024 and it had MSFS 2020 content streaming and it should have the United 787-10 livery but I don;t have that livery for the 787-10. I really new at this sim so please bear with me. The last time I fly the simulator was FS2004 about 20 years ago and I was pretty good at it and this is a new ballgame to me.
Thank you.
Kurt Jungwirth
Setting Altitude
Setting Airspeed
I’ve found in 2024 the controls are different (I guess there’s still legacy controls somewhere in the settings to see the different click icons), see: Inibuilds A320 V2 How to push/pull for managed/set modes? - #9 by TenPatrol
The main consideration worth noting here, is that the dials need to be pushed/pulled to give control to the plane, or give it to you. I’ve also noticed you have to “toggle” between the two modes in some case to get the plane to respond, I have no idea if this is accurate or not though.
Programming MCDU
I usually use the simbrief integration to get a flight plan setup, then import it into the MCDU using “init request” (note this will freeze your game when you end flight in the live build, but is fixed in SU1 beta). This leaves filling in the other pages during startup, but you don’t have to enter in all aspects of your flight plan everything manually. (Its worth noting entering the first init page can get you close for many flights with minimal waypoints outside of the airport dependent departure/approaches/etc)
I’ve never seen this, but then I rarely fly without auto-pilot being heavily involved (that’s why I’m in the airbus, to kick back relax and “fly” hehe).
This actually was available in FS20 and I used it since the release of FS20. If you want then that can be switched back to the legacy type of knobs interaction with mouse, afair in the interface options, for sure not in the controllers.
Just go to the FlyByWire website and go to the documentation for their A32nx. There you can find pretty much excelent guide not only for the MCDU, but almost every aspect of the Airbus A320neo.