:orphan: .. **************************************************************************** .. CUI .. .. The Advanced Framework for Simulation, Integration, and Modeling (AFSIM) .. .. The use, dissemination or disclosure of data in this file is subject to .. limitation or restriction. See accompanying README and LICENSE for details. .. **************************************************************************** WSF_P6DOF_EXPLICIT_WEAPON ------------------------- .. model:: weapon WSF_P6DOF_EXPLICIT_WEAPON **Script Class**: :class:`WsfWeapon` .. parsed-literal:: weapon :model:`WSF_P6DOF_EXPLICIT_WEAPON` ... :ref:`Platform_Part_Commands` ... ... :ref:`Articulated_Part_Commands` ... ... :model:`WSF_EXPLICIT_WEAPON` Commands ... add_subobject_ ... end_weapon Overview ======== :model:`WSF_P6DOF_EXPLICIT_WEAPON` is derived from :model:`WSF_EXPLICIT_WEAPON` and represents a :command:`weapon` that is modeled as an independent platform when it is fired. The purpose of :model:`WSF_P6DOF_EXPLICIT_WEAPON` is to allow a platform equipped with a :model:`WSF_P6DOF_MOVER` to launch/jettison its P6DOF subobjects as weapons. This means that the mover will have been modeling any aerodynamic, propulsion, and/or mass effects from the subobject (such as weight and drag) prior to launch, and will then cease doing so as the subobject is launched/fired. This means a realistic reduction in performance due to carrying weapons is properly modeled by the :model:`WSF_P6DOF_MOVER`. In addition, the relative location and orientation of the weapon relative to the parent vehicle is automatically specified within the definition of the :command:`p6dof_object_type`. Since the subobject will have its own independent platform when it is fired, it is an explicit weapon. Any separation velocity and/or angular rates are specified in the parent P6DOF object. .. block:: WSF_P6DOF_EXPLICIT_WEAPON Commands ======== .. command:: add_subobject Specifies the base name of a subobject on the :model:`WSF_P6DOF_MOVER` that will be launched/fired. Each individual subobject supported by the weapon (launcher) requires its own add_subobject command line. Each subobject must have a unique name. The subobject weapons will be launched in the order they are listed. Note that the launched platform type associated with the subobject is specified using the definition contained in the :ref:`P6DOF platform mappings`. **Default:** No default. Must be specified. Ignored Commands ================ The following commands are ignored and if used, will result in a warning: * :command:`launched_platform_type` * :command:`quantity` * :command:`maximum_quantity` * :command:`reload_increment` * :command:`reload_inventory` * :command:`reload_time` * :command:`inhibit_while_reloading` * :command:`launch_delta_v` * :command:`ignore_launch_platform_velocity`