Systems

The apu gets stuck and does not shutdown and the Master switch gets stuck, I follow a checklist or try several ways to solve this annoying problem and it just does not work That annoying bug is still there, the apu does not turn off, that is also seen in the airbus A321/A330/A320, both from msfs2020/2024 it only happens with inibuilds planes How can I fix this annoying system error?

I've encountered this issue multiple times now that when flying to a destination and then preparing everything for your return flight, the engines won´t start. N2 won't go over 29.6% even though the aircraft is configured properly.

I have MSFS 2020 on Xbox Series X, when I load simbrief flight plan into A320 Neo V2 there is always an additional waypoint that is in FMC that is 3000NM from my intended route. this only happens at EGSS. Anyone help.

Since the last sim update, I have had problems performing RNAV and RNP approaches. When activating APPR mode, the Vdev indication appears on the screen but it is not activated. Following the image below, it is possible to see that the mode is selected, I am on the final approach, aligned with the runway and the final app is not activated. The V/dev just passes by my altitude but it is not captured

Hi Everyone! I am building a panel for the a320, however I cannot seem to find any LVars that are associated to the annunciators of the panels (I am currently working on the EFIS, so by annunciator lights I mean the green portion of the korry switches). I did dump all the Lvars using FSUIPC, but I cannot seem to find anything that corresponds to the annunciator lights, only to the button presses. (I am attaching the full dump in case it helps somebody else) A320Neo2 LVARS.xlsx

On a flight from ENSB to ENGM, and the ETAs aren't working: The time is 1541Z, and that is also the time shown at ATSOT on the MCDU, although it is over 400NM behind me. It's supposed to be showing the time I reached ATSOT, but it's showing the present time and keeps updating. The ETA for NORVA. the next waypoint shown on the ND is over an hour away (ETA 1647), though only 120NM away (GS 431kt, should be about 17 minutes). Correct ETA would be 1704. Could this be investigated please?

When I do my flight everything is fine, until I reach the final approach. The plane moves and I can controll it, despite the engines, brakes, flaps, spoilers, gear...basically the whole cockpit just freezes. This happens consistently every time. Is there a fix for this?

Hi! On Xbox. On autopilot. After engaging Manual mode (heading), managed mode (nav) will not re-engage. Pic is just for showing the button. I know i am on the ground.

Departing EIDW 28R, using the PESI2J SID. The A320 levelled off at FL090 after passing waypoint DW991 because the next waypoint (DW122) has a -FL090 ALT constraint. However it recommenced CLB before reaching that waypoint. A pseudo waypoint for the 250/10000 speed limit appeared between these two waypoints and I think that may have broken the CLB constraint logic. A later ALT constraint at -FL230 was correctly respected. AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4). Kevin

I was flying the SUTE4L STAR to EIDW 28L. This creates several waypoints at FL070 from SORIN to DW706. After passing DW706 the A320 did not resume the descent automatically, as I expected. I had to press the ALT selector again to make it continue. AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4). Kevin

Hi, I’ve got a strange problem, i can get weather radar or TCAS or TERRAIN on my PFD. It look like a problem on the overlay (different kind of black in the PFD background). Any ideas ?

When you spawn at night at the runway in the 320neo, the DOME lights don't work. You have to select cold and dark mode from the EFB and then turn on the power and then the DOME lights work again. Am I the only one facing this bug?

As mentioned in the title; the display always shows TCAS STBY even though TCAS knob is set to TA/RA. Thanks..

I was flying from Helsinki to Stockholm arlanda on my xbox series s and everything went great, no issues whatsoever until all of a sudden at around 3000 feet during approach my systems froze and my aircraft plummeted into the ground nose first shortly after even though i wasnt even touching my mouse or sidestick, i know this is a common WASM issue that has been around for a while but is there still no fix?

When I select the arrival scheme in MCDU, the aircraft does not allow me to select the arrival and approach connection waypoint (trans), so the scheme is incorrect and misses many waypoints on arrival. Instead, it displays NONE. I am using the standard navigation database from the simulator, and this is not an its error. When I fly on another aircraft model, such as to Sheremetyevo, I see "TRANS - KEZVU," but on the A320 v2, it only displays "NONE" in this selection field.

Hello iniBuilds team and Microsoft Flight Simulator, I’m an Xbox user and a big fan of your A320neo V2, but unfortunately, I’m experiencing significant problems with the VNAV, TOD, and other key aircraft functionalities. These bugs severely impact the flight experience and make it difficult to use the aircraft realistically and reliably. Despite the release of MSFS 2024, which I hoped would bring improvements, the issues still persist on console, especially regarding memory management and proper navigation logic execution. I kindly ask you to prioritize these fixes for Xbox, as many users are waiting for a stable and complete version of the aircraft. T…

Hi! Today I was flying the following route on Xbox when all of a sudden during the last steps of the climb, the autopilot switched off and the aircraft banked heavily to the left and down, activating TOGA LK. I cleared that and managed to level off the aircraft, then re-engaging autopilot. It did not, however, follow the set course or follow the set altitude. The aircraft also didn't accelerate and struggled to maintain speed at flight level 320. I had to end the flight since the FMC and thus, the airplane, was unusable. I remember having this same issue sometimes on the A310 as well, although on a different route. No directs or SEC FP were used. LEBB 12 - AMTO…

Hello, I don’t know if you have done any update to the a320 v2 in msfs 2020 but I had some problems in my last 3 flights. On the final like FL150 all screens are going black, the systems work but the screens are going dark. The plane is powered and even if you cut the power and start it again noting happens. Please solve the problem is very annoying! (I’m playing on Xbox series x)

I have a Xbox x with ms2020. Installed 3 months ago. I don’t seem to have a320 neo on my aircraft marketplace or as my default. Checked content manager but no reference to any pending installation or updates. Tried reinstalling ms2020, still no aircraft. The only inibuilds aircraft showing is the a300.

I almost can't turning after taxi out. I have set efb.

When I input the arrival information into the FMC where I would expect a discontinuity, the FMC always joins the last waypoint of the SID to the initial approach fix of the ILS - for example when flying LOGAN 2H at LHR and selecting no via for ILS 09L. This is also the same for SIDS - the runway and the first waypoint are automatically linked. I have tried a removing and reinstalling the aircraft - any other ideas? Michael

Noticed tonight that if you start cold and dark then the pedestal lighting on the FO’s side does work (no other lighting does as identified in other threads). Conversely, if you load in and start on a departure runway, then the FO pedestal lighting doesn’t work.

Hi, when flying the A320 v2 I've had the same problem occur twice in exactly the same place. The problem is that, although the flight controls remain active, all the MCDU functions, flight displays and autopilot lock. The problem appears to be reproducable. Flying from KLAX to KLAS, when I reach the MILSEN waypoint the problem occurs. Attached is a screenshot of the PFDs and the LittleNavMap flightpath trace. The current flight (slightly right of the flightplan) is showing a 4000' difference to the cockpit after I descended manually. The previous flight (branching to the right and ending abruptly) is from the previous flight where I tried to reset the cockpit b…

When taxiing to the runway I usually like to use the AI Copilot to get me to the edge of the runway so I can focus on setting the cockpit up for takeoff, and it’s more realistic to a shared cockpit etc. this works fine with most aircraft in the sim, but I’ve noticed when I try to do this with the A320 v2 the AI Copilot is unable to steer the aircraft or adjust the throttle to much capacity and it just goes straight ahead into grass or buildings it seems unable to steer/turn the aircraft, I’m not sure if this is a silly thing to be posting about but it’s just something I’ve noticed.

Trying to download my Simbrief flight plan to the A320, but in the ATSU menu there's no option to enter my username/ID. It works fine on the EFB.