BoeingSpeedbird

4 months in and this is still an issue. Surely, this can be solved?

What’s the difference between the A320n V2 private charter and passenger version? Not sure which one to select in free flight and not clearly obvious as to the difference(s).

For some reason there is a sudden and huge increase in engine noise (through headphones) after take off (5-10sec), which means I have to quickly reduce the volume on the headphones as it is excruciating. Seems like a bug as it is disproportionate to pre- and during take off volume levels and a sudden step-increase.

Sorted in.10 beta update.

First time flying a321. During cruise the nose is bobbing / rocking constantly up and down and the trim wheel is constantly moving. If I disengage autopilot, the problem goes away. But this is not usual behaviour. Nothing like this in the a320.

If only we’d known this months ago! Great find.

7-months now and still broken. Appreciate this is MSFS, but somewhat ruining my experience of flying in the Inibuilds A320nV2.

You just need to cross-check. This is the same as Edinburgh where the populated ILS in MCDU is incorrect and need to put in correct details from Simbrief.

And another month further on and still no resolution to this. I can’t be the only one who finds this quite ridiculous and unacceptable.

Have you inserted your simbrief id into the MCDU also, which you need to do?

Have you selected the first call button, pulled out the first knob and turned it to full?

These lights haven’t been working for months. Need to wait for MS to push a sim update at some future time.

I think the fuelling and boarding need to complete before you can calculate performance data. This is the difference between instant and realistic, I think.

Yes, thanks. It’s totally frustrating that the lighting issues were fixed several months ago, but are not being pushed by MS/Asobo for us to be back enjoying this aircraft.

My solution (or this might be normal procedure?) is to not select the activate approach phase on MCDU if intending to use selected speeds through flaps 1-2. I suspect if you activate approach phase on MCDU before selecting ‘selected’ speeds through flaps 1-2 that the ‘selected’ speeds disarm the prior activation phase on MCDU, which you can’t reactivate later. So, what works is this: selected speeds and flaps 1-2; gear down; activate approach phase MCDU; then command speeds to follow flaps 3-full automatically.

Do you have a flight plan loaded and nav green in the FMA and flight directors on?

Am I missing a volume control or does the cabin call button make no sound? Also, what is the function of the loud speaker volume dial beside the avionics brightness dials?

I only ask as there are some videos of approach mode being activated but not approach phase.

Did you activate approach phase in MCDU and make sure flight plan is sequenced?

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.

Using selected speed and flaps to initiate initial approach, then with gear down and selecting flap 3 I’ll then go back to managed speed to reduce workload (this is what I’ve seen in videos). However, flaps 3 and 4 don’t ever reduce speed to Vapp speed as shown in MCDU, so unless I go back to selected speed I’ll come in too fast. What am I doing wrong? Is this something to do with the timing of when you activate approach phase on the MCDU - if activate and then go selected (for flaps 1&2), can you then not get back into approach phase on MCDU to coordinate speeds and automatically manage speeds for flaps 3&4?

When the FMA commands Thrust Climb are you moving the throttles into Climb detent?

Sorry - didn’t read that bit.

Toggle GPU in the EFB?

Can happen if FD isn’t selected.