Even after the latest Asobo patch it seems to me that when I set flaps to 1 during my descend, the responsivity of this action is way too high. The plane (A32NX CFBW) starts to climb at +/- 2000 ft/min. What can be done here? Should I half the lift_coef_flaps in flightmodel.cfg to 1.2 (it now is 2.4) or even lower to, say, 0.6?

Thanks,
Hans

35 minutes ago, hvw said:

What can be done here?

Slow down, using speed brakes, first... 😉

Then gear down...

Only then, flaps..

Edited March 7, 20215 yr by Bert Pieke

I did, but still the A320 bucks like a Mustang. Gear down later than flaps 1 even flaps 2 🙂  (At vref+50 I set flaps to 1 as I did over years in the 737)

 

Edited March 7, 20215 yr by hvw

" Should I half the lift_coef_flaps in flightmodel.cfg to 1.2 (it now is 2.4) or even lower to, say, 0.6? "

Yes.

And if a plane floats too much instead of sinking, then just move the station loads forward in flight_model.cfg. I've done it so often it takes me only about a minute to do.

Altering flying techniques to fix a poorly modeled plane is sort of like a cheat. Fixing the model is more realistic, because that is what is not correct. By the way for default planes, every update from Asobo will unfix the model (overwrite the flight_model.cfg file). But not 3rd party planes like the FlyByWire.

Fully agree with your thoughts. Even updates to  the FBW A32NX's do overwrite the flight_model.cfg file. So every time an update is being installed, one has to modify the flight_model.cfg file. At the GiHub site I was informed that the issue is known with the team. I guess we'll have to wait till they issue a solution.

https://www.youtube.com/channel/UCAILTiWNai7Y2zsO8ECFxcA/videos

Follow this guy's tutorials. 

13 hours ago, hvw said:

I did, but still the A320 bucks like a Mustang. Gear down later than flaps 1 even flaps 2 🙂  (At vref+50 I set flaps to 1 as I did over years in the 737)

 

not for me, no bucking

Don‘t know about the A320, but for the TBM i doubled the flap extension time in the flightmodel.cfg. They were coming out way to fast imho, which caused a strong pitch moment.

13 hours ago, Fielder said:

" Should I half the lift_coef_flaps in flightmodel.cfg to 1.2 (it now is 2.4) or even lower to, say, 0.6? "

No, I would recommend you not do that. Aside from that not being the root problem, that will affect every flap setting.

13 hours ago, Fielder said:

And if a plane floats too much instead of sinking, then just move the station loads forward in flight_model.cfg. I've done it so often it takes me only about a minute to do.

Again, I would caution against doing this in this case. Moving the station loads simply changes the cg location, which again is not the issue here. If you want to change the cg position, you can simply adjust the values in each station in the MSFS weight and balance window without having to make changes to the cfg file.

As @DAD noted, this does not appear to be an issue for everyone. I know of one particular case that was due to the individual having flaps assigned to an axis on his controller rather than having a button to increase flaps one setting at a time. As a result, he was getting 1+F instead of 1 on approach and this caused his issue with having the airplane briefly climb when he first deployed flaps on approach. Others have been inadvertently been using the legacy flight model.

What I have found is that the autopilot may be too aggressive in using pitch to decelerate to S speed upon selecting CONF 1. The vertical speed may briefly go positive during this deceleration until S speed is reached. This does not happen with the stable or developer versions indicating there may be something within the default FBW system that dampens the autopilot response. This should not be a function of the FBW system, so it will not be addressed in the experimental version until the custom autopilot is finished.

Edited March 8, 20215 yr by Donstim

Thanks for your input, Donstim. I will check my controller settings again. You very well maybe right that I got 1+F. instead of flaps 1. What you describe about the autopilot being too aggressive in using pitch to decelerate exactly describes what happens when I set flaps to 1. The speed when I set flaps 1 was correct, Vref+50, so I was rather unpleasantly surprised when the aircraft pitched up with +/- 2000 ft/min.

I just installed the latest version of the experimental FBW and will perform a flight later today, after having checked my controller settings, to see what happens then. I, for now, will refrain from fiddling with parameters in the flight_model.cfg file.

Thanks,
Hans

The problem still exists. I had a floating 747 the other day trying to land at Murmansk. I had to push the nose down so much in the end the sim deemed I had augered in, but that was the only way to get the word not allowed thing on the tarmac.

The fix worked for me in what I have flown since: 320-no mods, C172, Caravan, no more bucking.

37 minutes ago, desbean said:

The fix worked for me in what I have flown since: 320-no mods, C172, Caravan, no more bucking.

Happy that it works for you, but even after checking, double-checking and super checking all my controller and other settings, the CFWB A32NX still is misbehaving when I set my flaps to 1 at approach. As some others said, this might be strictly CFBW behavior. To find out, I will switch to the FBW 320NX dev mod. Should work fine as others said.

9 hours ago, Donstim said:

What I have found is that the autopilot may be too aggressive in using pitch to decelerate to S speed upon selecting CONF 1. The vertical speed may briefly go positive during this deceleration until S speed is reached. This does not happen with the stable or developer versions indicating there may be something within the default FBW system that dampens the autopilot response. This should not be a function of the FBW system, so it will not be addressed in the experimental version until the custom autopilot is finished.

You were spot on. I just completed a flight with the FBW A32NX Dev Mod and all went well. Thanks very much for your help.