BIS fnc findOverwatch: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "\[\[[cC]ategory:[fF]unctions\|\{\{uc:[a-z A-Z_]*\}\}\]\]" to "") |
m (Text replacement - "\[\[[cC]ategory:\{\{Name\|arma3\}\}: [fF]unctions\|\{\{uc:[a-z A-Z_]*\}\}\]\]" to "") |
||
Line 30: | Line 30: | ||
<!-- CONTINUE Notes --> | <!-- CONTINUE Notes --> |
Revision as of 02:20, 2 February 2021
Description
- Description:
- Description needed
- Execution:
- call
- Groups:
- Positions
Syntax
- Syntax:
- Syntax needed
- Parameters:
- target: Position3D - not an object
- maxDistance: Number - (Optional, default 500) maximum distance from target in meters
- minDistance: Number - (Optional, default 100) minimum distance from target in meters
- minHeightAbove: Number - (Optional, default 50) minimum height in relation to target in meters
- searchCentre: Position3D - (Optional, default target) position to start looking from, if different from target pos
- Return Value:
- Return value needed
Examples
- Example 1:
[getPosATL enemyTank, 300, 75, 20, getPosATL player] call BIS_fnc_findOverwatch;
Additional Information
- See also:
- See also needed
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
- Posted on October 19, 2018 - 21:40 (UTC)
- Tankbuster
- Note that this function returns a 2D position, that is, an array containing an x and a y value, but no z (no altitude).
- Posted on April 15, 2020 - 13:53 (UTC)
- Tankbuster
- Further note that when this function fails to find an overwatch position and returns the target, the x and y components will be exactly the same, but the z might not be.