Differences

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

--- aircraft:tmd:inputs [2022/07/19 20:59] – jh
+++ aircraft:tmd:inputs [2022/07/19 21:00] – 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. 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**
@@ Line 107: / Line 107: @@
                 <[string8][GeometryList][ ExampleButton ]>
                 <[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>