Same here, 100% agree. I am annoyed by this bug (or feature or how ever Asobo wants to call it) for a long time already and have no alternative on XSX. How can i upvote this? It says i am out of votes?!
Finally some liveries for the A320 and now the plane climbs like a school bus.
I dont know why this topic is not famous. There no one that fly the A320 on Xbox?
1 Like
Not anymore because the plane is a mess. Power issues, missing constraints, ILS indicators donāt show up. Seriously, this is a default aircraft. Imagine buying MSFS GOTY edition today, and this is your first experience. These bugs cannot wait for SU8. Some were introduced from SU6. Needs to sorted asap.
The plane is unusable. Love the liveries. lol
3 Likes
Iām quit playing. A320 is my favorite. And with every update the plane is literally getting worse and worse.
Shame
1 Like
Did you remove your community addons before doing updates?
I have no issues with the A320neo default.
Donāt have any options like that on Xbox.
4 posts were split to a new topic: A320 not loading in
Any update on this?
If you are using the default A320, it will not climb at higher altitudes because itās managed speed is pre -programmed too high.
The A320 does not have enough power to climb at 320 knots at higher altitudes.
Use selected speed and set 290 knots below approx. FL280, and anywhere from .76 to .78 mach above that level.
It will climb just fine then.
Yea, i usually maintain 288kts and .74 for climb but it takes so long to climb
What altitude are you trying to climb to?
FL380, with very light weight it takes really long to climb to CRZ, i need to disengage A/THR at clb to be able to climb to FL380
1 Like
Iām going to see what I can do in mine.
Been a while since I used it.
I normally go with the FBW.
Thanks for help 
that helps but do not match the climb performance the fbw has
if you keep the right vs for the appropriate altitude it does not hold the right speed
it just lacks the right performance but as you said to survive the only way is to select vs and speed otherwise good luck reaching higher altitudes
1 Like
OK, for the default A320, I flew out of CYHZ heading east, I had a (wow) 100kt tailwind.
I left it in managed until 10,000 and went in selected, as you, to 280kts.
At FL280, I switched to mach at 280 kts, thatās only .712m, but still in autothrottle Climb mode.
I climbed to FL380 in 28 minutes from throttle up on the rwy.
That does seem a bit long, but not overly so, especially considering the tailwind.
Now to try same run for the FBW.
Will be back in a bit.
1 Like
Tailwind has no effect on rate of climb and thus time to top of climb. If you take 3 aircraft, one climbing with a 100 kt headwind, one climbing in zero wind and one with 100 kt tailwind, considering all other conditions being the same, all three aircraft will reach top of climb at exactly the same time. All three aircraft would have the same rate of climb at any point during the climb and would have travelled the same distance through the air as TAS is not affected by wind. The distance travelled over the ground is a different story of course.
2 Likes
I actually knew that, you and I had discussed that about a year or so ago.
I was definitely brain dead when I was typing!
Thanks for the refresher! 
1 Like
Here is the results with the FBW.
I used about the same payload.
FBW was a couple hundred pounds heavier.
I used the same climb methods as the previous (250/280 kts /.72m at 28000)
From throttle up to FL380 was 18 minutes, so the default was 7 minutes longer to reach altitude.
One of the things I noticed was the FBW adjusts N1 for altitude, it was 86% at lower altitudes, whereas it was a bit above 90% above approx, FL300. The default was steady at 88% through the climb.
The only difference was weather.
The old weather server daily outage was in effect when I did the FBW test.
It probably wouldnāt account for much difference though.
1 Like