p6dof_object_types

p6dof_object_types … end_p6dof_object_types

p6dof_object_types

   // p6dof_object_type
   p6dof_object_type ... end_p6dof_object_type

   // P6DOF Thrust Producer Types
   jet_engine_type ... end_jet_engine_type
   ramjet_engine_type ... end_ramjet_engine_type
   liquid_propellant_rocket_type ... end_liquid_propellant_rocket_type
   solid_propellant_rocket_type ... end_solid_propellant_rocket_type

   // P6DOF Platform Mappings
   map_p6dof_object_to_platform ... end_map_p6dof_object_to_platform

   // P6DOF Integrators Support
   p6dof_integrators ...

   // P6DOF Environment Support
   p6dof_atmosphere ...
   p6dof_wind ...
   p6dof_terrain ...
   p6dof_gravity ...

end_p6dof_object_types

Overview

A p6dof_object_types block is used to specify various types of P6DOF objects, subobjects, components (such as engines), and environmental infrastructure (such as atmosphere, terrain, gravity, etc.). Once defined, a p6dof_object_type can be used when defining a WSF_P6DOF_MOVER.

Multiple p6dof_object_types blocks may be utilized. Types defined in the p6dof_object_types blocks must be unique. In addition, a type must be defined before it is referenced. As a result, the order in which types are defined is important. Types should be defined in the order in which they are referenced. Thus, if a “F2H_Banshee” P6Dof aircraft uses “Westinghouse_J34” jet engines, the engine type (jet_engine_type) should be defined first, followed by the aircraft (p6dof_object_type).

Commands

See references above.