reported Control Speed/Sensitivity

[Art-J]

Well, as I mentioned above, the rate at which brake force goes 100% (if assigned to key/button) is much faster than in other warbirds. Makes taxiing by tapping paddle lever on Warthog more difficult than in Spit. Taxiing and stopping the plane on runway actually, without raising the tail and slamming the tailwheel only because I pressed the lever 0.05 second too long ;). If it could be tuned to the same speed as in the Spit... Pretty please with cherry on top!

[scoobie]

Just bought some plums, don't have a cherry, but ED pretty please indeed!

A few random emoticons to draw attention:

Wheel brakes are more or less binary now (in response to a button press). They go from 0 to full within... like 150 ms or so.
Is it possible to simply make a functional copy of what was done in the Spit? In the Spit it works a few times slower.

 

PS. No luck with wheel brakes, @Art-J, I don't know if anything can be done at home. The thing seems to be buried somewhere deeper in the guts of the module The best I can only imagine is possible (hypothetically) is to slow down brakes response to pressing and holding a button, but if you release the button - the brakes will immediately let go, just as they do now. That would be inferior to the Spit and annoying to use. So "ED pretty please" I think is the best way to approach the subject

 

[NineLine]

Ok thanks guys, Trim is already reported, will report brakes and RPM, although brakes might be another issue, but similar.

[NineLine]

Brakes are now reported as well.

[NineLine]

And RPM as well. I will leave this report open in case their are other controls that need tweaking. Thanks all.

[LeCuvier]

I find the "Gunsight Base..." commands too fast as well.

Note This is for use with pushbuttons. If somebody uses a rotary encoder it's probably good. Unfortunately I have only 2 of those. This applies to other settings as well. It would probably be a good idea to have two pairs for these kinds of commands: One for "normal" pushbuttons plus on for rotary encoders.

 

Edited November 13, 2021 by LeCuvier

[P-51 Mustang Pilot]

Just to add to this, I seem to have this rpm increment issue show up/go away between GPU upgrades. But I also pulled and reattached all USB, so it may be related to that. But this appeared first using my 660ti, went away with the 1660ti, then just returned with a 3060ti. I realize someone mentioned this being related to frame rates—maybe the physics aren't but the input/output side is? ¯\_(ツ)_/¯

[P-51 Mustang Pilot]

I'm so happy I found this thread. Of note for Windows 10 users is to copy the file, edit it, then reinsert it into the directory to circumvent the "You Don’t Have Permission to Save in This Location" issue, which authorizing user rights doesn't seem to fix. Also, make sure you go into Folder Options and deselect "Hide extensions for known file types", so that you can remove the hidden .txt file name extension created after changing the file with a text editor, returning it to .lua so the game recognizes it.

I've done this for each of my WW2 aircraft, cept the Spitfire, which I can't seem to locate the propeller value in. Thank you everyone!