MCDU A321 not working

I tried to recreate that but for me everything works fine. Have you tried completely restarting the sim? And if that doesn’t work just post some extra info of exactly what you are doing so the devs can solve the issue.

The INIT page on the MCDU is improperly formatted and merges with the previously used page.

Buildings don’t spawn and aircraft are not responsive to all touch inputs since the memory-saver update. Perhaps the cut-backs should be an option for higher end devices?

It seems that after entering a flight number or cost index on an Airbus, all other interactions freeze.

Many éléments were also removed from the Boeing flight computers, such as QRH speeds, à clicking sound for the ATC page, and FIX INFO functionality.

Curiously, when I touched the INIT page during the cruise phase, the entire aircraft model detached from the camera view automatically, although the internal piece of the compass remained with the camera, which automatically stopped. I will attach photos shortly.

By merely touching the INIT button, I was ejected from my aircraft.

These issues begin once a flight number is entered.

Quote from Jet-Pack (IPACS)

Thank you, we recently made an optimization for the texts and it seems some special characters have gone missing.

---

What device are you using?

iPad Pro M2, 16GB RAM.

And yes, I am on the current version.

I have the same issue in the A320. It only affects the INIT page. The page seems to merge with other any other MCDU pages whenever you try to select it. So the top part of INIT appears on the display, but the bottom part stays as the previously selected page.

I’m on the iOS beta with version 1.04.10 installed and use an iPad Pro A2377 with iPadOS 18.1.1

Okay, I tested it and found out what causes the problem. The same problem appears on every plane of the A320 series whenever you enter a flight number with 7 digits. So I have tried the format XXX0000, with different characters and numbers an it always glitches out after that. Shorter flight numbers don’t produce the problem.

Hey Jan,

if I do exactly the same as you (I spawn the A320 at RWY18 at EDDF ready for takeoff) and enter 1234567 as FLT NBR I get the error as described. Fo me it doesn’t matter in what configuration I spawn, I can reproduce the mistake consistently. But I’m on an iPad ofc.

Oh found it. You have to have a route planned. So what I do: I plan a route (EDDF - LEPA), then spawn at EDDF in whatever config, then I go to INIT and enter 1234567, then I get the mistake.

And I also get the error with 8 digits for the FLT NBR, but not with shorter flight numbers. So I guess it could have sth to do with the character limit of the FLT NBR section or the INIT page.

The flight number issue happened to me recently while flying the A319. I had to restart the sim a couple of times but the issue persisted so I ended up doing the flight without entering a flight number. Next day I flew the A319 once again but this time without the issue, everything worked normally.

Maybe try un-installing and re-installing the sim?

Quote from Jet-Pack (IPACS)

Please make sure not to enter a flight number longer than 6 digits. Please confirm if this is the same issue as discussed here:

Thread

MCDU A321 not working

I cannot make any changes in the MCDU of the A321 at any starting point in EDDF. Is this known?

SamoaJon

November 25, 2024 at 10:16 PM

The update didn’t fix the issue for the A319.

The 737 MAX’s squawk code doesn’t update on the PFD panel any more.