Asobo’s post in recognition of the mistake they made with World Update 3 and the flight dynamics is vague at best, when it describes how to apply their ‘fix’.
Here is said post for the uninitiated:
Seriously. They are the worst instructions. Please can the helpful community here fill in some blanks:
For both Windows and Steam: a list of locations for each flight_model.cfg that we should and can change (the encrypted paid for models cannot even be manually edited, I know)
Elaborate on this confusing statement:
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 ).
For me, the word several is a collection of at least three, not two. Are those two in fact the only couple ‘of possible scalars’ or are there more? In any case… I see some files have entries for both. Do these both need changing or just one?
e.g. X:\FS2020\Official\Steam\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000\flight_model.cfg includes both lines:
lift_coef_flaps = 0.33790
… and later …
lift_scalar = 1.9 ; Scalar coefficient to ponderate global flap lift coef (non dimensioned)
I know the FBW team already compensated for this issue in their mod, so as long as you are using the development or experimental version it doesn’t need adjusting.
Reminder - Aircraft are marked Premium or Deluxe, and thus, Aircraft configuration and other core files are encrypted and not applicable to the flaps workaround. That includes the Baron.
Don’t you think it kind of defeats the point of a flight simulator if you can’t simulate landings?
Plus, you don’t learn to play guitar with out of tune strings - it is actually counter-productive to developing skill and training your ear. I believe this is analogous to this situation too - if you learn to fly with bad physics, you’ll learn to fly badly.
The fact this is not being hot fixed is pathetic and shows how little commitment Asobo has to the Flight Simulator community. They’re just leaving us with a broken simulator for weeks instead of fixing it timely.
Thanks Asobo, totally reminded me why I was hesitant to use FS2020 in the first place.
Maybe they should just have a “press X to land” button. Transports you from 2000 feet to stationary on the runway.
I could forgive them the bug if they’d made the slightest effort to explain the fix in simple clear terms that most people could understand. This would not take long. (Do they employ anyone at all to write documentation ?)
Dont get your panties in a bunch. Just freakin’ land without flaps for a few weeks till they fix it. This is a highly complex simulator. Things have a ripple effect in a complex simulation of the whole freakin world and aircraft and physics modeling. You cant harp on the flaws so much and ignore the progress this sim has made in leaps and bounds, literally in one year since it came out. If you are not happy with it. Stop using it for a few weeks till its fixed. Or stop complaining and get on with it .
… which is why if you change the way the flaps work it’s usually a good idea to be bothered to test whether you can still land a plane or not. I mean, you can’t exactly miss it.
I don’t see why I should ‘stop using it for a few weeks’ because of incompetence on the part of the developers.
You’d accept this with a car would you ? Sorry, you can’t use your car, we put the engine in backwards, tough XXXX, you’ll just have to learn to drive backwards for a few weeks.
And none of your post actually answers the question ; which was, if you need the long version, “how come nobody in Asobo can be bothered to spend half an hour writing a clear description of how to correct this problem ?”
How come there’s this company with “hundreds of developers” to quote one member of the access media that can’t make the same progress that a few amateurs are doing fixing things ?
I even reached out to @Jummivana - the Community Manager who wrote the post describing the workaround - asking for more clarity.
Complete radio silence though.
I can forgive the development mistakes - I am a software developer and have a lot of empathy for this (but how this managed to slip through the test/QA/build process unnoticed is quite alarming, especially for a project this size).
However, I’m not sure there is an excuse for the ■■■■ poor communication. As you said, simply taking 30 mins (if that!) to properly explain/document the workaround is not a lot to ask and would make a world of difference.
Depends. There is a module (which is pretty much identical to editing the files directly), if you’ve installed that you will need to remove it when the hotfix is out RSN (hopefully!)
They might fix it by updating the configuration files (they might not, it could be changed in the model), but they should tell you this when they release the hotfix. It is quite likely that they will simply overwrite the config files.
I just saw this for the first time today. I thought my C208’s landings had seemed a fair amount longer than they used to. Ground effect seemed to last forever. Glad it wasn’t just my imagination.