====== ArmA 2 UAV ======

[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]

**Unmanned Aerial Vehicle (UAV)** module manages movement and access to aerial camera of UAV.

Initialization

Paths

Editor:

Units (F1) > Game Logic > Modules > UAV

Data:

ca\modules\uav

Editor setup

{{ https://pmc.editing.wiki/images/arma2_uav.jpg }}

  - UAV manager - module manager.
  - UAV - unit with parent class UAV. If more UAV's are assigned, first one is selected (and replaced by another one when first is destroyed).
  - Unit with access - all linked units will have access to UAV via action.
  - UAV terminal - all linked empty (nonAI) objects serves as terminals. Units with access gets action once they are near terminals. 

Optional parameters

Set variables to UAV manager with desired values:

   * name = <string>; - name of UAV (displayed in action menu) 

Example: BIS_uav_0 setvariable ["name","RQ-1 Predator"];\\
Default value: empty string 

   * rules = <array>; - Rule which defines which units with have access to UAV. Can be either list of specific units or whole side. 

Example: BIS_uav_0 setvariable ["rules",[west,allied_gue_1]];\\
Default value: units synchronized in editor 

   * areasize = <number>; - Size of terminal area (area in which custom action will be displayed) 

Example: BIS_uav_0 setvariable ["areasize",5];\\
Default value: 10