gazeb

Every time I tried to fly the A320 with a flight plan is goes wako shortly into the flight.

This.

That's one of my pet hates, fortunately there's a simple fix if you don't mind editing the engines.cfg file with Notepad.

In the engines.cfg file, copy and paste these two lines over the same two lines at the bottom of the [TURBINEENGINEDATA] section:

 

low_idle_n1 = 12 ; 19.5

low_idle_n2 = 36 ; 58.5

 

This reduces the idle rpm so that some thrust is required to taxi again.

Thanks for this. I've updated the file and it still seems to taxi very easily so I may try reducing further.

Are you using the new a32nx mod, released today?

Thanks. Updated and working again.

One thing I've noticed is since the update it appears the A320 requires virtually no throttle at all to begin taxiing. Even at idle the plane continues moving forwards.

New problem...

Set-up the A320 flight plan at the start screen and then begin the flight. Press Ctrl+E to start the engines....MSFS20 crashes out. I've tried rebooting the PC and restarting but to no avail. What a fiasco this product is turning out to be for me.

After the latest MFS2020 update the auto pilot has started working for me. Not doing anything different so goodness knows what has happened.

However, the FlyByWire plugin appears to have stopped working. Is that expected when there is an upgrade to the base sim?

https://flybywiresim.com/a32nx

I increased the dead zone on my joystick to 10% but am still having the same problem. The flight plan is ignored and the plane crashed! It must be one of:

1) I'm doing something fundamentally wrong. Very possible as I've just switched over from XP11

2) There is a bug in MFS2020 that is affecting my set up

3) My very old Saitek rumble force joystick is the cause of the problem

Looks like I need to investigate further but currently the A320 is completely unusable and broken from my perspective.

Just tried a take off with LOC and FD selected; aircraft turned towards selected flight path then after about a minute, executed a tight right turn that left the aircraft at a 90 degree bank nose down.

Exactly the sort of behaviour I am experiencing. It makes the A320 unusable for me currently and I'm tempted to revert to XPlane 11.

I tried it with FD -- no dice and then with LOC, also no good will try with both selected at takeoff

I've tried with both selected at takeoff and it still doesn't work for me.

Yes, the Airbus needs LOC engaged to follow the flight plan. Are you using the FlyByWire A32NX mod by the way? It's pretty much essential and Asobo are considering building it into a future update: https://flybywiresim.com/a32nx

I'm not using the FlyByWire mod. I'll give it a go and see if that helps.

Edit: I've installed the FlyByWire mod but the A320 still isn't following the flight plan I've loaded. I'll test with different flight plans to see if that is the problem.

You need to engage the Flight Director and Localizer as well as the Autopilot.

Thanks for the reply.

I've got the FD engaged but surely I shouldn't have the Localizer engaged shortly after take off? However, even with Localizer engaged it still doesn't follow the flight plan.

Hi,

I'm running MFS2020 through Steam and install the patches as they become available. I'm having major problems with the A320: It simply won't follow a flight plan that I create from the "World Map". Not sure if it's something I'm doing but I have successfully used the JAR A320 autopilot in XP11 in the past.

So all I do is:

1) Generate the flight plan

2) Take off with auto thrust (to me it seems overpowered) at TOGA

3) Climb, gear up, flaps retract from F1, Thrust to Climb

4) Engage auto pilot in managed mode

After doing the above the A320 begins to bank, lose altitude and finally crashes.

Am I missing something obvious?

Think this makes the decsion for me:

I'll stick to X-Plane 11.5 for now.

Thanks for the replies. On balance I'd say I'm a tad disappointed with the performance of MSFS2020 from what I have read here and seen on videos elsewhere.

FSX was from recollection primarily running on one CPU core with little support from the graphics card.

We have now moved into the multicore CPU world with powerful graphics cards as the norm. I was hoping (and expecting if truth be told) MSFS2020 would be ultra-smooth even in relatively densely populated areas.

To me it is critical to have smooth graphics. From the overall experience there is little worse than stuttering scenery when landing or taking off in a flight sim. I'd sooner have smoother animation and see less out of the cockpit.

Will I buy FS2020 now or wait to see what happens? I'm undecided. The money isn't an issue but I don't want to waste time installing, configuring and learning only to find myself switching back to XPlane 11.5.

Hi,

I used FSX for years and was never particularly happy with the frame rate or flight model. A couple of years ago I switched across to XPlane 11 and despite its limitations found the flying experience to be much better. The frame rate is consistently excellent, the graphics pretty good and the flight model superb.

I now find myself wondering whether I should go back to Microsoft and buy MSF2020. The realistic graphics (at least from the videos I've watched) would be a nice bonus, as would built in air traffic control and routing. However, if the performance in terms of FPS (some of the videos look very jerky) is inferior to XPlane 11 and the flight model worse, then the other benefits would not be persuasive enough for me to make the transition.

So can anyone specifically address the points about frame rates and flight models?

PS: It is NOT my intention for this to be a discussion about which of the two products is better in your opinion - merely a subjective appraisal of the two specific points.

Thanks

Brian