Donstim

I just thought it was some turbulence when I first encountered it. But it continues all flight, every flight, every altitude. Pretty annoying.

You just need to fly the correct speeds with the correct flap settings. Please view the landing tutorial video.

Can you post some screenshots or even a video? From the description, it sounds like you are activating alpha-floor and getting auto TOGA thrust. What speed and flap setting were you at? Edit: Never mind. I saw and responded to your duplicate posting on the official MSFS site. To be blunt, but not intending to be offensive, you simply don't know how to operate the airplane. I strongly suggest you watch some video tutorials on how to properly operate an A320. It is a complex airplane, and unfortunately MS/Asobo doesn't provide any documentation on how to operate the various default airplane (other than the simple Cessna). Once you learn how and gain experience, it becomes like second nature, but until you learn how, it is not an easy thing to do.

I think that is a common issue that has led many to have this problem. Should be on the a list of FAQs somewhere or something.

What you are describing is the interaction between a faulty FBW envelope protection system implementation with incorrect (too high) stall speeds. You are pretty much hosed at that point unless you apply full TOGA power. There can be a fine line between being at an approach speed that doesn't cause this and one that does. It doesn't help when you are heavier. You might try bumping up the approach speeds progressively by 5 knots until it performs reliably. Be careful with pitch inputs. I've seldom seen this issue myself, but it has occurred a few times. I just fly managed speed with the thrust levers in the CL position, deploying flaps on schedule with a final landing configuration of full landing flaps and gear down. I get established on the glidepath under autopilot control, then disengage the autopilot at around 1000 feet (or lower depending on visibility/winds).

If you're in Nav mode, approach phase activates automatically when flying over the DECEL psuedo-waypoint. You can always change your speed mode to a selected speed if you don't want the managed speed.

It is my understanding that you select position 1 and you put that into the MCDU. For takeoff, it happens to correspond to configuration 1 + F, but depending on airspeed, position 1 can also be just configuration 1. Anyway, you don't put 1+F into the MCDU, you just put 1.

For the A320, you need to enter ZFW in kilograms. To find your ZFW in MSFS, zero out the fuel as mentioned above, Then your takeoff weight is your ZFW. If it is 110,000 lbs for example, then you need to enter 49.9 (followed by a "/" and the ZFW CG. Now, here's the catch, There is a bug in the flybywiresim mod, that you need to enter three digits to the left of the decimal point for ZFW, so for 49.9, you need to enter 049.9. They were working on fixing this, and it may have been fixed by now.

Where did you get that from? I've had direct responses within days that bugs I've identified have been acknowledged and added to their internal bug and issue tracker. If your Zendesk aren't any more complete than most forum posts, that could explain why your reports don't go anywhere.

Did you try the flight plan that Armchair Pilot flew (starting cold and dark and including the approach procedure)? When I get a chance I'll try the flight plan you posted. For my earlier flight, although I specified ILS 25-Z for the approach, somehow the VOR-DME 25L got substituted somehow. I had to change it on arrival and flew in heading select mode until capturing the localizer. When your autopilot reverts to NAV mode, I wonder what waypoint it is guiding to? Have you tried cycling the LOC/APPR modes or the autopilot? Edit: Okay, I did exactly your flight plan. (Wondering why you chose low altitude airways instead of high altitude airways?) Everything worked fine, so I don't have anything new to report. The only difference is that I am using the latest Navigraph beta navdata (current cycle, rev 6) and the latest A320 mod just updated before doing this flight.

I did not do anything with my Community folder other than to check and see what the status of the various mods were post-patch before trying to use any of them. The Community folder itself should not be affected by base game updates.

Were your screenshots of the EBBR approach done with the mod installed? If so, they show that you have not captured either the localizer or the glideslope, as the FMA indications for those on the PFD are blue, not green. The FMA says you are still in NAV lateral and ALT* vertical mode. Also, make sure you use the latest developer mod version, not the stable one. Get the installer here:https://github.com/Externoak/A32NX-installer/releases/tag/v0.4.1 I had no problems flying the approach. I thought it might be a navdata issue, so I uninstalled my Navigraph beta navdata, but the default nav data did just fine. I don't know why yours didn't capture, but make sure you capture the localizer first from below the glideslope, then arm APPR. I would add a screenshot of my approach, but the "insert image from URL" doesn't seem to like my GooglePhotos link. Here it is anyway https://photos.app.goo.gl/Hv6isEvgVcuFT7M36

My landing technique is very similar. Keep the autothrust engaged and in managed speed mode during flap extension and allow the airplane to set you up nicely if on an ILS approach by keeping the autopilot on until around 1000 feet or so. If not on the ILS and under manual control (but with autothrust still engaged in managed speed mode) use pitch angle to establish the correct descent rate. At around 20-30 feet (depending on descent rate), flare with a small pitch increase, followed by moving the thrust levers to the idle position. Someone mentioned trim -- don't even try to trim; trim is adjusted automatically, so any inputs you make are going to be overridden and probably mess things up.

The flight director doesn't work right. Don't try to follow it. It mainly follows you in this sime, rather than you following it. Instead, after liftoff, smoothly, but fairly quickly increase pitch up to 15-18 degrees to maintain V2+10 (not V2). Then lower the pitch angle to increase speed for thrust reduction and flap retraction. Engage the autopilot and be ready to overshoot the 250 kt speed restriction before it finally settles down.

What do you mean by "the FBW logic is up and down?" I'm sure not flying it like an ultralight and not having it "flit around," but maybe I haven't seen big wind gusts like you have? I will agree there is a mass/inertia issue in that you can accelerate and decelerate much too quickly in flight. This is one airplane you can come in hot and high and have no problems landing - no need for stable approach criteria! I guess as a GA pilot, you just couldn't resist the trim wheel! Just don't even think about it! I realize that there have been plenty of autopilot issues reported (and not just on this airplane and nothing to do with the mod), but I haven't experienced them. No need to introduce it gradually, and it can be engaged 5 seconds after liftoff (no lower than 100 feet AGL) in real life. What are the serious control issues and fundamental aerodynamics errors? Most of the aerodynamic coefficients are in the flight model.cfg file and can be readily changed. The hard part is pinpointing exactly what a particular problem is caused by (for example, is it a thrust or drag issue) and then finding the right variable to change it in just the right way.

+10 for this. I don't really understand this whole thing about describing an issue you are having in a forum post, get people to vote on it (which might include advertising and marketing it), and then having Asobo only list those issues and bugs in what looks like a priority list. In the meantime, they have a Zendesk system where reports are supposed to be detailed enough for developers to recreate the issue, but these issues do not get widely publicized and itemized in a priority list. Yet, I have to think (and hope) that it is the Zendesk reports that are the primary ones used to actually identify bug/fixes and set priorities.

lol! Read the post literally directly above yours...

I've only flown the 787 a couple of times, but completed the flights just fine. I didn't find it "completely useless and unflyable" at all. The only major issue I had was that my Flight Sim Yoke needed to be re-calibrated for dead zone. It must have been sending commands when centered that overrode autopilot control. When I switched to my Thrustmaster X HOTAS that problem went away.

There is a "master" version (used to be called developer's version) that is constantly being updated. It may be unstable and contain bugs as it is still under QA testing, but it is far ahead of the so-called stable version. You can download it here: https://github.com/flybywiresim/a32nx Just click on the green "Code" button and download the zip file. (Or, just click on this link: https://github.com/flybywiresim/a32nx/releases/download/vmaster/A32NX-master.zip).) Extract all files, open the \a32nx-master folder and copy just the A32NX folder to your MSFS community folder. But before doing this, delete the current A32NX folder from your MSFS Community folder. Or, there is a new installer at this link: https://github.com/Externoak/A32NX-installer/releases/download/0.1/A32NX_Downloader.zip that should do all of the above for you automatically. I haven't tried it yet myself.

Live weather. Based on the stability of the approaches, I would have to say that I don't think there was much crosswind in any of those approaches. I should have paid more attention, but since I wasn't having to correct for it, I really didn't even look at the wind direction. I spend a lot of time on the team's Discord server, staying current with what they are doing and contributing where I can. See https://github.com/flybywiresim/a32nx/pull/1029, and if you want more background, https://github.com/flybywiresim/a32nx/issues/1034#issuecomment-702604116 and https://github.com/flybywiresim/a32nx/issues/1014. The post I was responding to regarding it potentially being due to the mod was one that said they had unexpected behavior as soon as they started putting flaps down (and other posts about unrealistic pitch attitude in the flare, not the specific wing drop issue you are talking about. Nowhere did I claim your issue may be caused by the mod, so there is nothing to debunk.

Note that he said he'd heard of the issue, but had never experienced it before. I'm kind of in the same boat- have maybe experienced it once or twice out of many landings. Most of those landing have been ulta stable with only slight control inputs needed to maintain path. He also said that he had a bit of crosswind. I wonder if that is one of the factors involved? MSFS seems to accentuate the small perturbations due to wind.

Do you have the A320 mod installed? The stable version of that mod can cause issues with flaps down because they reduced the lift coefficient in flaps down configurations. If this is your issue, delete the mod and install the latest master (not stable) version. If this isn't your issue,make sure you don't have something else bound to whatever input you are making to extend flaps, make sure your controller is calibrated and has appropriate dead zones, if necessary, and cross your fingers!

The mod had lowered the lift coefficient with flaps down. This change has been reverted in the latest master version due to its poor low speed performance. Try the new master version, not the stable version.

I use live and multiplayer traffic and have never had the issue. I have ai aircraft models set to "generic," which is supposed to help. Many of the people I've corresponded with that have this issue are using Xbox controllers. Setting a deadzone of 5 to 10% has resolved the issue for them. I did have the issue during the beta phase, but it resulted from having two controllers installed and active. The one I was not using was apparently sending some spurious signals or "fighting" with the one I was using. As soon as I disconnected one of the controllers, the issue resolved itself. So, i think that at least for some of the people having this issue, it is a controller issue, and not just Xbox controllers.

No issues. 16 GB of RAM. Have already helped a couple of people who use Xbox controllers and report "broken" autopilots" in all airplanes. Setting a 10% deadzone fixed it for them. Not all issues are CTDs.