A320 Xbox

[Azlog]

Have to start by saying the new A320 NEO is really quite something. Looks and sounds great and I can’t wait for the full release. Have done a few flights in it on the Xbox series X and have noticed the following:

1. Can’t hear ATC voices
2. Transponder code stays showing 7000
3. No transitions for arrivals at any airport tried so far
4. Strange departure route (EGPH departure GRICE3C 24 took me for a tour of Scotland before heading to GRICE)
5. Can’t enter in ILS or VOR codes into MCDU Radio Nav page
6. EDDN runway 28 had no ILS glide slope or DME
7. Controls feel sluggish during rotation but then super sensitive once the wheels leave the ground like it’s trying to go into space 
8. Controls feel very sluggish on approach with the flare being almost impossible to initiate but as soon as the wheels touch down the nose goes shooting up
9. Hydraulic pump “barks” missing when engines start and stop

[Azlog]

I might be overthinking this, but is the aircraft going into ground mode too quickly after touchdown as a reason for number 8? It would explain why the nose suddenly goes up in the air if elevator deflection matches side stick deflection in ground mode as I’m having to pull back pretty far to get it to flare

 

[Deleted Account]

Heya!

1) You'll have to turn on the radio in the pedestal.

2) What exactly do you mean by this? I can change the code no problem.

3) They maybe are located under the APR VIA section

4) Thanks, will take a look at this one

5) You'll need to enter the Identifier and not the frequency

6) The frequency probably didnt autotune

9) It is there, but you won't be able to hear it from the cockpit, as in real life.

[Azlog]

41 minutes ago, Nico - Gumby said:

Heya!

1) You'll have to turn on the radio in the pedestal.

2) What exactly do you mean by this? I can change the code no problem.

3) They maybe are located under the APR VIA section

4) Thanks, will take a look at this one

5) You'll need to enter the Identifier and not the frequency

6) The frequency probably didnt autotune

9) It is there, but you won't be able to hear it from the cockpit, as in real life.

1) the vhf1 was muted (in) so pulling it out and increasing the volume fixed this 

2) pressing CLR made the code disappear and allowed code to be entered

3) see attached screenshots. No via listed to select. May waypoint missing as this is part of the transition. Works perfectly in the A310

5) understood - that worked

9) ok. Found it strange as so prominent in the sound mix in default A20N and LVFR builds

 

[Azlog]

I just spotted the APPR VIA button on my screenshot. Will try pressing it later to see if that gives me transitions

[Azlog]

23 hours ago, Nico - Gumby said:

Heya!

1) You'll have to turn on the radio in the pedestal.

2) What exactly do you mean by this? I can change the code no problem.

3) They maybe are located under the APR VIA section

4) Thanks, will take a look at this one

5) You'll need to enter the Identifier and not the frequency

6) The frequency probably didnt autotune

9) It is there, but you won't be able to hear it from the cockpit, as in real life.

Ok I’m happy with all of my points now minus the occasional strange departure route. Getting used to how it flies by being careful to only pull back a little at rotation so the faint crosshair reaches the green bar and leave it there. Then on landing, I think I was almost pre-empting the retard call out due to other Airbus builds floating down the runway if you didn’t get the power off quickly. This was causing too much energy loss and having to pull too hard to flare. Quite why it suddenly went so dramatically nose up when the wheels touched down is maybe something that still needs looked at but I didn’t have such a problem with the last landing I did