User Tools

Site Tools


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
aircraft:tmd:inputs [2022/07/19 20:59] jhaircraft:tmd:inputs [2022/07/19 21:02] (current) jh
Line 22: 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 LandingLightSwitch.Output without problem. This speeds things up when you only need to copy paste. Sometimes you have to do more on the graphics side of things, then you could use the name with a "Graphics" at the end, e.g. "LandingLightSwitchGraphics" but you could also copy-paste the Geometry name, e.g. SwLdgLt... though this is not recommended as it is harder to decipher and generally costs more time because it can't be copy pasted to other places.+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 LandingLightSwitch.Output without problem. This speeds things up when you only need to copy paste. Sometimes you have to do more on the graphics side of things, then you could use the name with a "Graphics" at the end, e.g. "LandingLightSwitchGraphics" but you could also copy-paste the Geometry name, e.g. SwLdgLt... though this is not recommended as it is harder to decipher and generally costs more time because it can't be copy pasted to other places.
  
 **...Knob, ...Switch** **...Knob, ...Switch**
Line 107: Line 107:
                 <[string8][GeometryList][ ExampleButton ]>                 <[string8][GeometryList][ ExampleButton ]>
                 <[tmvector3d][Axis][ 1.0 0.0 0.0 ]>                 <[tmvector3d][Axis][ 1.0 0.0 0.0 ]>
-                <[uint32][AngleID][ExampleButton.Output]> +                <[uint32][InputID][ExampleButton.Output]> 
-                <[float64][Pos0][-0.001]> +                <[float64][Scaling][0.001]>
-                <[float64][Pos1][0.001]>+
             >             >
 </code> </code>
  
-''Pos0'' and ''Pos1'' determine the movement length, how far the button is pressed in. ''Pos0'' represents the value for input a theoretical ''-1.0'' and ''Pos1'' for an input of ''1.0''. The average between these two is the zero position.+''Scaling'' and ''Offset'' determine the movement length, how far the button is pressed in. ''Offset'' represents the zero position and ''Scaling'' defines the displacement.
  
-In the example the button moves by 0.001 meter or 1 mm. To increase the amount of translation change Pos0 and Pos1 to e.g. 0.002 for 2 mm+In the example the button moves by 0.001 meter or 1 mm. To increase the amount of translation change the Scaling parameter to e.g. 0.002 for 2 mm.
- +
-> This may be changed in the future to be less confusing.+
  
 === SoundObjects === === SoundObjects ===
aircraft/tmd/inputs.1658257165.txt.gz · Last modified: 2022/07/19 20:59 by jh