User Tools

Site Tools

Trace:
aircraft:tmd

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 [2019/07/07 17:24] – [DynamicObjects] jhaircraft:tmd [2019/07/20 18:51] – [GraphicObjects] jh
Line 49: Line 49:
   * [[aircraft:tmd:actuators   |Actuators]]   * [[aircraft:tmd:actuators   |Actuators]]
   * [[aircraft:tmd:propulsion  |Propulsion]]   * [[aircraft:tmd:propulsion  |Propulsion]]
 +  * [[aircraft:tmd:instruments |Instrumentation]]
   * [[aircraft:tmd:inputs      |Inputs (buttons, switches and knobs, flight controls, digital inputs)]]   * [[aircraft:tmd:inputs      |Inputs (buttons, switches and knobs, flight controls, digital inputs)]]
 +  * [[aircraft:tmd:logic       |Math and Logic Circuits]]
   * [[aircraft:tmd:events      |Event Based Programming]]   * [[aircraft:tmd:events      |Event Based Programming]]
   * [[aircraft:tmd:electrical  |Electrical Systems]]   * [[aircraft:tmd:electrical  |Electrical Systems]]
   * [[aircraft:tmd:fuel        |Fuel Systems]]   * [[aircraft:tmd:fuel        |Fuel Systems]]
   * [[aircraft:tmd:hydraulic   |Hydraulic Systems]]   * [[aircraft:tmd:hydraulic   |Hydraulic Systems]]
-  * [[aircraft:tmd:instruments |Instrumentation]] 
   * [[aircraft:tmd:autopilot   |Autopilot and Flight Management]]   * [[aircraft:tmd:autopilot   |Autopilot and Flight Management]]
  
Line 77: Line 78:
  
 The rendering engine itself can't directly access the user's control inputs or simulate the position of slow moving actuators; this is what the physics engine does. Every animation, therefore, needs to get their inputs from the dynamics section where all the physical movements or delays can be simulated. To send a value from the dynamics section to the graphics section the dynamics section needs to define an 'output' object as described above and the graphics section needs to have a [[aircraft:tmd:graphics_input|graphics_input]] object whose InputID matches the 'Name' property of the output followed by the text '.Output'. The rendering engine itself can't directly access the user's control inputs or simulate the position of slow moving actuators; this is what the physics engine does. Every animation, therefore, needs to get their inputs from the dynamics section where all the physical movements or delays can be simulated. To send a value from the dynamics section to the graphics section the dynamics section needs to define an 'output' object as described above and the graphics section needs to have a [[aircraft:tmd:graphics_input|graphics_input]] object whose InputID matches the 'Name' property of the output followed by the text '.Output'.
 +
 +Collection of the pages relevant to the GraphicObjects section:
 +  * [[aircraft:tmd:inputs              |Animation of buttons, switches and knobs]]
 +  * [[aircraft:tmd:rigidbodygraphics   |Rigidbodygraphics, transformations and bendingbodygraphics]]
 +  * [[aircraft:tmd:lighting            |Interieur lighting and external lights]]
 +  * [[aircraft:tmd:displays            |Numerical Displays, LCDs, flight displays, HUDs]]
 +  * [[aircraft:tmd:humangraphics       |Human character]]
 +
  
 ==== SoundObjects ==== ==== SoundObjects ====
Line 84: Line 93:
 Similar to the graphics section a [[aircraft:tmd:soundinput|soundinput]] object will read the value of a dynamics [[aircraft:tmd:output|output]] object and provide its value for the entire sound section. Similar to the graphics section a [[aircraft:tmd:soundinput|soundinput]] object will read the value of a dynamics [[aircraft:tmd:output|output]] object and provide its value for the entire sound section.
  
 +Most relevant pages
 +  * [[aircraft:tmd:inputs      |Button, switch and knob sounds triggered in DynamicObjects]]
 +  * [[aircraft:tmd:sound       |Sound input, mixing, mapping, fading, etc.]]
  
 ===== Object unique names ===== ===== Object unique names =====
aircraft/tmd.txt · Last modified: 2022/07/19 21:14 by jh