Turbine Duke beta range behavior & sensitivity
-
With the power levers in ground idle, the props will slowly accelerate to 1200+ RPM and build up a substantial amount of reverse thrust (enough to quickly stop the plane or even make it roll backwards in some situations), but moving the power levers forward even just a tiny bit immediately causes the RPM to drop to ~800 and the props will start producing a decent amount of forward thrust.
Is it supposed to be this sensitive? I find it difficult to control my taxi speed because I have to constantly go back and forth between ground idle and just barely above ground idle. For comparison, in the TBM850, I can quite easily set the power roughly where I need it and then make small adjustments to control my speed.
The first image below shows debug data with the engines at ground idle, and the second image shows data at 1% throttle which is like less than a millimeter of movement on my physical throttle.
-
Black Square modeled the beta range of the propeller lever as automatically engaging at a throttle position of 15 percent, rather than beta/reverse being manually activated by the user via a button. This is more realistic but requires either a physical or virtual detent on your throttle hardware. If you don't have some kind of detent set up with your throttle, you are automatically in full reverse when your throttle is at the idle stop. You have to push up your throttle until you hear a click sound and observe the red LED lights next to both torque gauges extinguish to actually be at ground idle.
A physical or virtual detent allows one to have a range on the throttle that's a null zone buffer between beta and normal ranges so that you can precisely control throttle movement either to idle or into beta. Without a detent system, you have an instant transition from forward thrust position into beta without any kind of buffer zone.
I hope this makes sense.
-
@Ballinger-France said in Turbine Duke beta range behavior & sensitivity:
This is more realistic but requires either a physical or virtual detent on your throttle hardware.
Is there any way to remove the beta range that activates reverse when throttle position is less than 15 percent ?
I have a Thrustmaster HOTAS WARTHOG Throttle.
There is no physical detent on the axis! And when I set the throttle to the minimum position I expect to get IDLE, but I get REVERSE!Trying to adjust throttle axes in FSUIPC did not give any result....
I want to have idle when I set the throttle to minimum! Not reverse!
Is this possible? -
@Randolf said in Turbine Duke beta range behavior & sensitivity:
yes, you can use FSUIPC axis calibration and raise the lower value to match the idle position, then your entire axis will output values between idle and max
I'm trying, but it's not working.
Here's one of my customization options for Throttle1.
https://youtu.be/VN9E1uQWo0AI've tried many options, and never my trottle stops at idle (or much higher or... at max reverse)
And why when I press "SET" in the axis adjustment window and do not adjust anything - the OUT value is always "-4096" and not "-16384" ?
https://youtu.be/DbQN9Hf2vSw -
@SMN204 sorry, you're right, FSUIPC doesn't have an option to set the output range in the GUI, but according to Pete Dowson this can be done by editing the
fsuipc.ini
file.First set up your throttles in the axis calibration with the full range of your hardware as normal, and click no reverse zone on top of the calibration window.
Then open the
fsuipc.ini
file, and find the lines forThrottle1
and 2 under[JoystickCalibration]
, or under the profile-specific calibration, if using aircraft profiles.Then extend the first (lowest) value on that line beyond what your hardware axis would provide. For me a value of -23000 was somewhere in the ballpark to match Duke's idle position with my hardware lever fully backwards, so the line would look something like this (adjust as necessary and repeat for Throttle2):
Throttle1=-23000,-16319,-16319,16384/48
You can edit the file while the axis calibration window is open, then just press the reload button at the bottom of the window and it should fill in the new values.