Solved Need Help: Controlling Throttle With Keystrokes
Hi all. Thanks for any help you may have.
My Warthog throttle bricked some months ago and I’ve had to fly with keyboard throttle controls since then (‘Throttle Step Up’ / ‘Throttle Step Down’ and ‘Throttle Forward’ / ‘Throttle Back’). The problem is that the step up/down commands seem to adjust about 2-3 times more than I’d expect a “step” to be. (The forward/back commands are giant, but I only use those for takeoff.)
Does anyone know of a way to configure the amount (PPM) per key press with these commands? I’ve RTFM’d and searched the forum, but have found nothing, so I suspect this feature doesn’t exist…
Also, does anyone else have experience using keyboard throttle control and have any advice? For example, it seems that making two or three steps up and then one less back gives a sort of fine-tuning to the final setting, but its terribly hit or miss.
@Slothrop Concur, I reported this back in 4.35 time.
All I can offer is, I noticed if you bind mousewheel to throttle axis, the increments are much smaller.
This isn’t officially supported, and the UI to select it can be a little finicky. And it’s backward direction to what one might expect… and ofc now you have to find a different way to zoom in fov. And if you accidentally middle-click the mousewheel it will snap throttle to 50% position. In addition to resetting your fov.
Other options… using something like vJoy / Gremlin to define a virtual axis, then map a pair of keys to increment/decrement that virtual axis.
@Slothrop might be a long shot but use an XBox controller as a throttle?
@Atlas that works, but you have to keep hand on it full time – the axes snap back to 50% when you release them!
Maybe there’s some vJoy / Gremlin app to simulate a throttle axis, based on incremental thumbstick or trigger inputs? Not sure.
@airtex2019, @Atlas - Thank you both for the help. I’ve managed to get comfortable with the key controls except for landings. Managing a proper descent speed and AOA is way more difficult without a throttle.
@spooky - I don’t consider the problem solved. It’s still a problem, but a new throttle will solve it for me. Even so, I’d be interested to hear others experiences with this…
It would be a nice upgrade in a future version to add a configuration option to specify fuel flow, in PPM, per key press. Won’t be used often, of course, but would be a lifesaver for those like me, stuck with a keyboard controller for a while.
Also they seem a little random / non-deterministic. It would be nice if each click was a predictable, fixed % of throttle-range … not tied to the millisecond-timing of the keypress.
(Very low priority issue … but maybe also very low effort to fix?)