There’s been something about the cockpit lighting that has been annoying me and now I know what it is. There are 4 panel floodlights in the A320, relatively evenly spread in front of both pilots. And this is modelled perfectly on the A20N v2 in 2020. But in 2024, there are only 3 light sources. The ones furthest from the centre are ok(ish) but the middle 2 have been replaced by a single yellow source that sits slightly beneath the glareshield and this lights up the whole of the centre of the panel. Will post comparison pics at some point to highlight it
1 Like
Here’s the offending light source. You can see that the floodlights are casting light against the panel but then there is this horrible yellow extra one making everything, well, yellow
Edit: funny enough there is also one in each corner
1 Like
Honestly as much as I love flying the a320 Neo V2, I would rather fly the a321 Neo and the different a321 variants, and instead of the a320 Neo, I would rather have an default a220 300 to fly
I’m currently learning to fly the A320neo V2, and it is an incredible aircraft—definitely my favorite so far. However, I have a quick question regarding a warning light. Every time I land, a red AP light appears. I can temporarily silence it by toggling the autopilot on and off, but the alarm eventually returns. It’s driving me crazy! Does anyone know the proper way to deactivate it? 
If you click the little red button on the side stick, this should disarm the auto pilot.
Thank you I’ll give it a try
First press on red button on side stick should disengage autopilot and a second press should stop the alarm / chime. I think this does matter that you have the red button binding to “toggle disengage autopilot” and not “toggle autopilot”.
2 Likes
The sounds in this aircraft have fallen off the cliff, and to be frank most the Inibuilds aircraft have sound problems
The A320 the cockpit is too quiet, and outside camera is deafening
The A310 the cockpit warnings will make you deaf, the AirCon on the ground is also deafening this has been an issue since release and not fixed. Many years
Can Inibuilds or Asobo whoever is looking after these default airbuses pls focus on sound improvements, it’s really letting these aircraft down
5 Likes
Does anyone else occasionally wind up with corrupted times on the MCDU? This seems to come woth some extra lines on the PFD which seem to connect the aircraft to the destination at all times. The flight plan does not have any misplaced waypoints.
TOD does not calculate in this state. Sorry about the photos… I’m on XBOX.
Thanks in advance.
As of SU4, the aircraft is overall pretty good!
The main quirks in my experience are:
- Engines not starting properly on turn-around. N2 stuck at around 29%, as described on iniBuilds forum.
- Trim wheel stuck on turn-around. Can’t be adjusted via binding nor mouse interaction.
- Random Traffic Advisory calls. Even though there is no traffic to be seen, TCAS is randomly yelling with advisories, like descend, maintain vertical speed etc.
- Any interaction with the EFB also interacts with the sun screen behind.
- The EFB option to toggle chocks and covers does not work.
I would also very much like to see a build in landing calculator in the EFB, and ACARS implemented (as a minimum for D-ATIS, but CPDLC would be great).
5 Likes
Importing data from MCDU (to EFB) set FL to 220, even if you set your FL in the MCDU to something else (Ex: FL370)
Try going to Fuel Pred in MCDU and pressing the ZFW/ZFWCG again to recalculate.
I get this often in the A330, there will be a rogue waypoint which will be a couple thousand miles away, delete it along with the discontinuity it will then recalculate and make sense, when it happens to me it’s a waypoint with a couple letters only such as ZK
I’ve definitely seen the rogue waypoints issue, but that shows up as a very long distance between two way points in the FP ~4500 nm, for example, and a fuel prediction of -99.
This issue was different, and the times were all totally corrupted. I cleared the reserved space, and I have not seen it happen again, so maybe that fixed it. I’ve had many good flights in the A320 since.
I’ve now moved on to the A330 and have no airspeed indication… so now I’m trying to figure that out. I may post something on the A330 topic about that.
Edit: the A330 airspeed issue also seems to be fixed by clearing the reserved space.
Is there a reason why my A320 refuses to show the weights in kgs/metric? Ive tried changing it in the EFB and nothing works. Ive checked my settings in the Option screen and its set to metric there as well.
Its not a major convenience to calculate kgs to lbs, but I wish I didnt have to as it seems the option is there in the EFB to switch over.
I stopped flying the a320 because I kept flying the a321 more, it’s strange we don’t get the current smaller default airbus option like the a319 or a220 with these default Airbus aircraft because what other default airbus options do I get to learn next after learning the a32X and a330’s?
I started flying the A320neo in Career mode. I’ve flown the aircraft several hundred hours in MSFS 2020 so I’m broadly familiar with its systems, however in Career mode I’m having difficulties triggering descent mode during missions.
The problem is this: I’m getting close to the top of descent (indicated on the ND as usual). I set the lower altitude target and press the knob to enter descent mode. However, the aircraft doesn’t start descending at 1000 fpm until the VNAV profile catches up. Instead, it stays at cruise altitude, and DES mode appears blue on the PFD, indicating that it’s armed.
However, as the aircraft reaches and passes the top of descent point, nothing happens. It stays at cruise altitude, DES remains blue and the VNAV profile indicator green dot just races down on the altitude tape. The aircraft never follows it.
During every mission I have to switch to open descent mode in order for the aircraft to catch up to the profile indicator, after which it can capture and follow it. However, in normal DES mode the aircraft doesn’t level off at the target altitude, instead it keeps going down, following the green dot.
Is this because Career flight plans are not correctly imported into the MCDU? I see several issues with the flight plans upon startup, fake waypoints at the other end of the world, double waypoints on approach and often no altitude data filled in at approach waypoints. Could all this confuse the aircraft’s systems? Is there a way to manually fill altitude data in flight plans?
Speculating based on A320 experience here …
DES should only ever appear in blue if you arrive at a waypoint that has an “AT OR ABOVE” constraint and so ALT CST would appear in Green while DES would appear in blue. So I’m wondering if the imported route has come with altitude constraints for “AT” attached to waypoints all the way until ATC is going to tell you to descend, preventing you from doing a managed descent when you need to. Wouldn’t do this with a simbrief import, hence why never seen in free flight
Edit: No easy fix. You would need to press the CLR button and then press the left softkey beside each waypoint on the flight plan to clear the constraint data
The aircraft remains in ALT CRZ mode when I push the altitude knob. However, I realized that if I pull it and engage open descent mode, the aircraft starts descending as it should, and then I can push it to engage descent mode and DES will be active. Kind of annoying but not something that can’t be worked around.
Agreed on this. The A320 V2 is my favorite aircraft to fly. The only other thing I’d note on the list is this annoying bug that happens when you click on the Ground button the tablet. The function works but it also brings up the window shade.
im on XBox Series S.