BIS fnc findOverwatch: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\[\[Category\:Function Group\: Misc(\|\{\{[a-zA-Z0-9_:]+\}\})?\]\]" to "")
mNo edit summary
Line 5: Line 5:


|1.00|Game version=
|1.00|Game version=
|gr1 = Positions |GROUP1=
____________________________________________________________________________________________
____________________________________________________________________________________________



Revision as of 14:53, 10 October 2020

Hover & click on the images for description

Description

Description:
Selects a position that provides overwatch onto another position.
Execution:
call
Groups:
Positions

Syntax

Syntax:
[target, maxDistance, minDistance, minHeightAbove, searchCentre] call BIS_fnc_findOverwatch
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:
Position - target position if no result were found

Examples

Example 1:
[getPosATL enemyTank, 300, 75, 20, getPosATL player] call BIS_fnc_findOverwatch;

Additional Information

See also:
BIS_fnc_findSafePos

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

Notes

Bottom Section

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.