thanks for the heads up

In the meantime, a workaround is to go into the flight_model.cfg and divide the flap lift by 2x (there are several possible scalars for that purpose: lift_coef_flaps or lift_scalar).

Any idea where I find the flight model.cfg file?  I'm assuming this is a "per plane" setting...

EDIT:  nvm found it

Edited February 19, 20215 yr by sidfadc

1 minute ago, christb said:

Shouldn't there be an "or" in between lines 2 & 3?

That's my question too.

Seems so according to this:  https://forums.flightsimulator.com/t/flight-dynamics-bug-details/368499.

Looks like either/or.

Edited February 19, 20215 yr by christb

Fair play to them, yes it should'nt of happened. But they've realised the issue, and hopefully address it once and for all in the sim update.

38 minutes ago, sd_flyer said:

At least now we can fix it ourselves! 🙂

As always. Never fixed by the one who should fix it. Seems to be the only possible way.

Cheers, Ed

39 minutes ago, sidfadc said:

In the meantime, a workaround is to go into the flight_model.cfg and divide the flap lift by 2x (there are several possible scalars for that purpose: lift_coef_flaps or lift_scalar)

Interesting - when investigating this setting, I found some mods have the coefficient at a different setting than Asobo, with others having it identical  Which setting do I over-ride?  The mods? Asobo? Both?

The $64k question being of course, will we have to manually change the values back if/when Asobo fix the problem. So far I've only done the A320 (default) which is what I'm flying, but if we're not careful come March we could have a fleet of planes that start to hug the ground...

Ridiculous, so they changed something, forgot to test it and now they tell you, deal with it until next month. That is why I was and I will be saying, their update process has been doing harm more than good. They introduced new ridiculous bugs that is so weird that is even a simple test would see that. I think we as community, we should really demand, a change for their update process, 3 to 4 months updates that is heavily tested with beta test. These monthly updates are hectic and annoying for us and for them .

 

 

Edited February 19, 20215 yr by omarsmak30

2 minutes ago, Elvensmith said:

The $64k question being of course, will we have to manually change the values back if/when Asobo fix the problem. So far I've only done the A320 (default) which is what I'm flying, but if we're not careful come March we could have a fleet of planes that start to hug the ground...

I think just as it was changed now, it will be a wholesale change then, but just in case back up the original and put it somewhere outside the folder.

1 hour ago, Car147 said:

But they've realised the issue

Funny. When I first read you post I read "But they've raised the issue".  First thought was they lowered the issue....  (Their fault.  Flaps.  Ha!) Freudian read?  LOL! 

Edited February 19, 20215 yr by fppilot

Jeez ... I wonder where Asobo's brains are. To let the issue get past testing is one thing (forgivable) but to post such incomplete information for the "fix" is downright slovenly.

1) No information as to the location of this file (or files).

2) Whether this fix needs to be applied to *every* aircraft - or just a few.

3) No mention that add-on aircraft (eg. the FBW A320) are most likely unaffected as they have their own .cfg files.

[sigh]

Edited February 20, 20215 yr by Adamski_NZ

...bah! and no one believed me.

They broke something critical and now they tell you "oops wait till next month". Oh boy their update process really needs a complete rework. With their Q&A team of course 

Applied the fix to the Icon and C172 G1000, tested both with good results. Will do until the next SIM update.

I'm thankful that the ASOBO team are making many things better, but I hope that they are more wary in the future to avoid breaking our sims. This time they added blue taxi lights over many airports.