Idle Cut off question on Throttle
-
The way the idle/cutoff threshold (red line detent setting in the UI) works is intended only to support physical devices that register DX axis values that register change all the way from fully off (all the way back) and full afterburner.
This was really done to support the cockpit building crowd. In their case, the easiest mechanization of the actual throttle arm is to put a pot on the arm to measure full throw of the arm from one end of the throttle handle guide rail to the other. That guide rail has the “tooth” that represents the idle position (forward side of the tooth) but full off is behind (which is to say aft) of the tooth. The fact that you have to physically lift the TQS handle and push it past the tooth/gate with the flight hardware means that there’s no problem setting the idle detent in the UI (red line) above zero point of the throttle travel because you can’t accidentally pull the throttle back past that point…you have to mean it
If you haven’t seen how the actual flight hardware works,
[[I can’t really see why Thrustmaster chose the design they did with making you use button mappings for the idle/cutoff – they made the device more complicated and expensive to manufacture than they needed to in order to achieve this so far as I can tell…and requiring more programming steps to get it working.]]
-
Cougar had axis-only. Warthog cutoff “buttons” are purely software defined. If desired you can get axis motion in the off-idle range with creative calibration. Warthog was designed for DCS. It’s too complicated for Falcon… they don’t care. With TARGET you can do everything you need to do. DCS doesn’t have axis-based events so button event needed to happen in design.
-
Warthog cutoff “buttons” are purely software defined. If desired you can get axis motion in the off-idle range with creative calibration.
Interesting. I did not know either of those things – thanks for cluing me in better. I guess I need to take back the editorial then…my bad