aircraft:tmd:inputs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| aircraft:tmd:inputs [2019/07/07 17:06] – jh | aircraft:tmd:inputs [2022/07/19 21:02] (current) – 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: | The keyboard, joystick or clickspot activated by the mouse, VR hands or touch inputs generate a message from the [[aircraft: | ||
| Line 17: | Line 15: | ||
| > It is important to get the combination of control message '' | > It is important to get the combination of control message '' | ||
| - | === Naming Convention === | + | ==== Naming Convention |
| **Copy & Paste** | **Copy & Paste** | ||
| Line 24: | Line 22: | ||
| E.g. you don't need to come up with different names for the graphics section than for the physics. Just re-use the same one everywhere. Much easier. | E.g. you don't need to come up with different names for the graphics section than for the physics. Just re-use the same one everywhere. Much easier. | ||
| - | E.g. In the GraphicObjects section you can **re-use the same name for the graphic object**, e.g. the hingedbodygraphics LandingLightSwitch can use the AngleID | + | E.g. In the GraphicObjects section you can **re-use the same name for the graphic object**, e.g. the hingedbodygraphics LandingLightSwitch can use the InputID |
| **...Knob, ...Switch** | **...Knob, ...Switch** | ||
| In the [[aircraft: | In the [[aircraft: | ||
| - | |||
| - | **Controls** | ||
| - | |||
| - | In the [[aircraft: | ||
| - | |||
| - | In the [[aircraft: | ||
| **Pilot/ | **Pilot/ | ||
| Line 41: | Line 33: | ||
| When there are more than two devices or the device is located in the center, accessible to both pilots, or when they are usually named this way you can also use a numbering (e.g. RPM1, RMP2, NAV1, NAV2) or left and right (LeftCDU, CenterCDU, RightCDU). The name should be helpful when you search and replace it. For example you can setup the left CDU keys first and then just copy the entire section and then rename all " | When there are more than two devices or the device is located in the center, accessible to both pilots, or when they are usually named this way you can also use a numbering (e.g. RPM1, RMP2, NAV1, NAV2) or left and right (LeftCDU, CenterCDU, RightCDU). The name should be helpful when you search and replace it. For example you can setup the left CDU keys first and then just copy the entire section and then rename all " | ||
| + | |||
| + | |||
| + | **Controls** | ||
| + | |||
| + | In the [[aircraft: | ||
| + | |||
| + | In the [[aircraft: | ||
| **Sound** | **Sound** | ||
| Line 47: | Line 46: | ||
| ---- | ---- | ||
| + | |||
| + | ===== Buttons, Switches, Knobs and Levers ===== | ||
| ==== Button ==== | ==== Button ==== | ||
| Line 78: | Line 79: | ||
| > | > | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 106: | Line 107: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| - | < | + | |
| > | > | ||
| </ | </ | ||
| - | '' | + | '' |
| - | In the example the button moves by 0.001 meter or 1 mm. To increase the amount of translation change | + | In the example the button moves by 0.001 meter or 1 mm. To increase the amount of translation change |
| - | + | ||
| - | > This may be changed in the future to be less confusing. | + | |
| === SoundObjects === | === SoundObjects === | ||
| Line 206: | Line 204: | ||
| > | > | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 235: | Line 233: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| > | > | ||
| </ | </ | ||
| Line 276: | Line 274: | ||
| The typical chain consists of '' | The typical chain consists of '' | ||
| - | The setup is similar to the toggle switch only with minor differences like the use of '' | + | The setup is similar to the toggle switch only with minor differences like the use of '' |
| === ControlObjects === | === ControlObjects === | ||
| Line 328: | Line 326: | ||
| > | > | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 361: | Line 359: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| > | > | ||
| </ | </ | ||
| Line 430: | Line 428: | ||
| > | > | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 463: | Line 461: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| > | > | ||
| </ | </ | ||
| Line 527: | Line 525: | ||
| > | > | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 552: | Line 550: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| > | > | ||
| </ | </ | ||
| Line 611: | Line 609: | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 643: | Line 641: | ||
| < | < | ||
| < | < | ||
| - | < | + | < |
| - | < | + | < |
| > | > | ||
| </ | </ | ||
| ---- | ---- | ||
| + | |||
| + | ==== Lever2 - Dual Lever === | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| ==== Rocker Button and Switch ==== | ==== Rocker Button and Switch ==== | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 662: | Line 674: | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 669: | Line 681: | ||
| > | > | ||
| </ | </ | ||
| + | |||
| + | ===== Flight Controls ===== | ||
| + | |||
| + | ==== input_default ==== | ||
| + | |||
| + | The input_default is used for all non-discrete (floating point) inputs. | ||
| + | |||
| + | Typically these are found for light dimmers, trim inputs, etc. which are typically operated with a joystick or with a cockpit dimmer or trim-wheel, etc. but button inputs are also possible with this generic input. | ||
| + | |||
| + | The '' | ||
| + | |||
| + | '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_control ==== | ||
| + | |||
| + | The input_control behaves much like the input_default but it allows for multiple input devices at the same time. E.g. you could be holding the yoke with your VR hands, then put them down and use your physical yoke instead. The input_control handles these cases and allows a soft transition between multiple devices or even the operation of multiple devices at the same time. | ||
| + | |||
| + | > Usually the input_control is only used for the elevator and aileron. | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ===== Other Inputs ===== | ||
| + | |||
| + | ==== input_binary ==== | ||
| + | |||
| + | The input_binary either outputs 1.0 (true) or 0.0 (false). With messages from the controls it can either be toggled (qualifier '' | ||
| + | |||
| + | Using [[aircraft: | ||
| + | |||
| + | < | ||
| + | < | ||
| + | > | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_discrete ==== | ||
| + | |||
| + | There are several types of inputs that are represented by an input_discrete, | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | The '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | The input_discrete has an output to the tmd only ('' | ||
| + | |||
| + | ==== input_discrete_cyclic ==== | ||
| + | |||
| + | The input_discrete_cyclic works exactly like the '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_discrete_momentary ==== | ||
| + | |||
| + | Again very similar to the '' | ||
| + | |||
| + | > Used for the magneto switch and starter or a hold-to-test switch. | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | |||
| + | ==== input_cyclic ==== | ||
| + | |||
| + | The input_cyclic is an input that loops back around to the beginning when it reaches the end of the '' | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_pair ==== | ||
| + | |||
| + | This is the typical frequency input that can be found in all kinds of aircraft. The frequency input has two values at the same time, an active and a standby value. The standby value is adjustable and can be set without having an immediate impact. Then the frequency is transferred (swapped) to the active frequency and the previously active frequency is now the standby frequency. | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | For optional automatic frequency tuning (autotuning): | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_event ==== | ||
| + | |||
| + | Receives messages and then fires events with the received message value. | ||
| + | |||
| + | * '' | ||
| + | * '' | ||
| + | * All events in the '' | ||
| + | |||
| + | The use of the '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
| + | ==== input_active ==== | ||
| + | |||
| + | Outputs 1.0 to the tmd as long as a lever is grabbed or a button is depressed. | ||
| + | |||
| + | > Typically this is only used to make a light illuminate as long as a button is pressed or to give visual feedback that a control is grabbed. Don't use this for every single button in combination with an event_edge, this should be done with the '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | > | ||
| + | </ | ||
| + | |||
aircraft/tmd/inputs.1562511988.txt.gz · Last modified: 2019/07/07 17:06 by jh