Originally posted by wetrat
I have some knowledge of programming, and flap deployment speed for each notch of flaps is most likely a variable. That is to say, if "x" was the first notch of flaps in a K4, then "x = 170". If I'm correct in this, then it doesn't seem like too arduous a task to fix this problem.
With my (non)knowledge, I would assume it would be the same simple fix too. So, you get the nice buzzing sound and the graphics change at 170mph. But, the part I don't know and wouldn't dare speculate on is how many
other changes you would need in the code that actually describe the flight model.
Right now we have a set of programming that describes how the plane handles. So, flying at 160 in a 109 means certain things at certain pitch, roll, yaw, throttle, etc. If you change the flap deployment so that flaps are available at 160, you now may have to code a
different set of characteristics for a 109 with one notch of flap at all angles of pitch, roll, throttle, etc. Now do the same thing at 155 with one notch, or 150 with one notch AND two notches, etc. And that would be without stick input. How many tens or hundreds of different stick inputs could there be, all with a different outcome at each different speed when there either IS or ISN'T a notch of flaps extended? Suddenly, it doesn't seem like quite so simple a change to me.
Like I said, I don't pretend to know anything about that level of programming and I could be way over-complicating it. But on the other hand, if it was as simple as changing "x=120" to "x=170", then I have to believe it would have been fixed a LONG time ago given it is an
admitted problem.