User Tools

Site Tools

Trace:
aircraft:tmd:inputs

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
aircraft:tmd:inputs [2019/07/07 17:06] – [Buttons, Switches, Knobs and Levers] jhaircraft:tmd:inputs [2019/07/07 17:11] – [Rocker Button and Switch] jh
Line 1: Line 1:
 ====== TMD Inputs ====== ====== TMD Inputs ======
- 
-===== Buttons, Switches, Knobs and Levers ===== 
  
 Aircraft in the Aerofly FS 2 simulate interactive cockpits where each button, switch, knob, lever, selector, etc. are individual parts. We're now describing how to set up the most common inputs for your own custom aircraft. Aircraft in the Aerofly FS 2 simulate interactive cockpits where each button, switch, knob, lever, selector, etc. are individual parts. We're now describing how to set up the most common inputs for your own custom aircraft.
  
-=== General principle ===+==== General principle ====
  
 The keyboard, joystick or clickspot activated by the mouse, VR hands or touch inputs generate a message from the [[aircraft:controls|controls.tmd]] (**ControlObjects**) that is send to the [[aircraft:tmd|TMD]]. These messages contain the message name string, a message qualifier like step, toggle, move, event, etc. and a value like 1.0 for example or -1.0. The keyboard, joystick or clickspot activated by the mouse, VR hands or touch inputs generate a message from the [[aircraft:controls|controls.tmd]] (**ControlObjects**) that is send to the [[aircraft:tmd|TMD]]. These messages contain the message name string, a message qualifier like step, toggle, move, event, etc. and a value like 1.0 for example or -1.0.
Line 17: Line 15:
 > It is important to get the combination of control message ''Type'', trigger mode of message (e.g. ''OnStep'', ''OnRotate'') as well as the message qualifier (''step'', ''event'', etc.) correctly. Otherwise you might not see the desired results for all input devices if anything happens at all. > It is important to get the combination of control message ''Type'', trigger mode of message (e.g. ''OnStep'', ''OnRotate'') as well as the message qualifier (''step'', ''event'', etc.) correctly. Otherwise you might not see the desired results for all input devices if anything happens at all.
  
-=== Naming Convention ===+==== Naming Convention ====
  
 **Copy & Paste** **Copy & Paste**
Line 48: Line 46:
  
 ---- ----
 +
 +===== Buttons, Switches, Knobs and Levers =====
  
 ==== Button ==== ==== Button ====
Line 650: Line 650:
  
 ---- ----
 +
 +==== Lever2 - Dual Lever ===
 +
 +<code>            <[input_lever2][Throttle1Input][]
 +                <[string8][Input0][Controls.Throttle1]>
 +                <[string8][Input1][Controls.ThrustReverse1]>
 +                <[float64][StepSize0][1.0]>
 +                <[float64][StepSize1][2.2222222]>
 +                <[bool][Input0ClampZero][true]>
 +                <[bool][Input1ClampZero][true]>
 +                <[string8][Range][ -1.0 1.35 ]>
 +                <[string8][Range0][ 0.0 1.0 ]>
 +            >
 +</code>
  
 ==== Rocker Button and Switch ==== ==== Rocker Button and Switch ====
Line 670: Line 684:
             >             >
 </code> </code>
 +
 +===== Digital States =====
 +
 +input_binary, input_discrete, input_discrete_cyclic, input_discrete_momentary, input_event, input_active, input_cyclic, input_pair, input_default, input_scratchpad
 +
 +===== Flight Controls =====
 +
 +input_control
aircraft/tmd/inputs.txt · Last modified: 2022/07/19 21:02 by jh