nearTargets: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
(formatting)
Line 35: Line 35:
*1: _type (perceived, gives only what was recognized)
*1: _type (perceived, gives only what was recognized)
*2: _side (perceived side)
*2: _side (perceived side)
*3: _subjectiveCost (positive for enemies, more positive for more important or more dangerous  
*3: _subjectiveCost (positive for enemies, more positive for more important or more dangerous enemies)
enemies)
*4: _object (object type, can be used to get more information if needed)
*4: _object (object type, can be used to get more information if needed)
*5: _positionAccuracy (assumed accuracy of the perceived position)
*5: _positionAccuracy (assumed accuracy of the perceived position)
   
   
|x1= <code>[[player]] [[nearTargets]] 100;{{cc|Could return something like this: [[[2555.33,2535.33,1.32708],"SoldierEB",EAST,214222,EAST 1-1-A:1],[[2550.39,2482.5,1.32696],"SoldierWB",WEST,0,WEST 1-1-A:2]]}}</code>
|x1= <code>[[player]] [[nearTargets]] 100;{{cc|Could return something like this: <nowiki>[[</nowiki>[2555.33,2535.33,1.32708],"SoldierEB",EAST,214222,EAST 1-1-A:1],<nowiki>[</nowiki>[2550.39,2482.5,1.32696],"SoldierWB",WEST,0,WEST 1-1-A:2]]}}</code>


|seealso= [[reveal]], [[knowsAbout]], [[findNearestEnemy]], [[nearestBuilding]], [[nearestObject]], [[nearestObjects]], [[nearObjects]], [[nearestLocation]], [[nearEntities]], [[nearSupplies]], [[nearestLocationWithDubbing]], [[nearObjectsReady]], [[nearRoads]], [[forgetTarget]]
|seealso= [[reveal]], [[knowsAbout]], [[findNearestEnemy]], [[nearestBuilding]], [[nearestObject]], [[nearestObjects]], [[nearObjects]], [[nearestLocation]], [[nearEntities]], [[nearSupplies]], [[nearestLocationWithDubbing]], [[nearObjectsReady]], [[nearRoads]], [[forgetTarget]]
}}
}}
<dl class="command_description">
<dd class="notedate">Posted on Febuary 17, 2011</dd>
<dt class="note">[[User:Curry|Curry]]</dt>
<dd class="note">A subjective cost greater than 0 does not necessarily mean the target is an enemy unit. <b>Any</b> unit, that have yet to be identified by the unit, have a small positive cost in the range 0 to 1.
<dd class="notedate">Posted on January 15, 2012</dd>
<dt class="note">[[User:kju|kju]]</dt>
<dd class="note">The quality/detail level of the info depends on the [[knowsAbout]] value of the sourceUnit about the targetUnit:
* For infantry:
** ] 0  , 1.5 [ - side unknown, some position offset, identified as SoldierWB
** [ 1.5, 1.6 [ - side identified, subjective cost set
** [ 1.6, 2  [ - type identified better (USMC_Soldier_Base)
** [ 2  , 3.6 [ - type identified precisely (USMC_Soldier)
** [ 3.6, 4  ] - position identified precisely
The values seems closely linked to the accuracy value of the given targetUnit class and its parents up in the config tree:
* 0 class CAManBase: Man
* 1.6 class SoldierWB: CAManBase
* 2 class USMC_Soldier_Base: SoldierWB
* 3.9 class USMC_Soldier: USMC_Soldier_Base
* For tanks:
** ] 0  , 0.03 [ - side unknown, some position offset, identified as LandVehicle
** [ 0.03, 0.13 [ - type identified better (Tank)
** [ 0.13, 0.3  [ - type identified better (M1A1)
** [ 0.3 , 1.5  [ - side identified, subjective cost set
** [ 1.5 , 3.6  [ - side identified precisely (CIV), subjective cost adjusted
** [ 3.6 , 4    ] - position identified precisely
The values seems closely linked to the accuracy value of the given targetUnit class and its parents up in the config tree:
* 0 class All
* class AllVehicles: All
**  0.0005 class Land: AllVehicles
**  0.02 class LandVehicle: Land
**  0.12 class Tank: LandVehicle
**  0.25 class M1A1: Tank
<dd class="notedate">Posted on January 17, 2012</dd>
<dt class="note">[[User:kju|kju]]</dt>
<dd class="note">
* When an unit dies, it is nearTargets array gets emptied after some seconds.
* When an unit dies, its reference will get removed from other units nearTargets' arrays immediately.
* A target will be removed from the array after about 360 seconds without contact.
<dd class="notedate">Posted on January 21, 2012</dd>
<dt class="note">[[User:kju|kju]]</dt>
<dd class="note">Position accuracy seems to be a radius in meters from the perceived position.
</dl>

Revision as of 14:54, 31 March 2021

Logo A1 black.png1.07Logo A2.png1.00A2 OA Logo.png1.51tkoh logo small.png1.00Arma 3 logo black.png0.50
Hover & click on the images for description

Description

Description:
Returns a list of targets within the defined range. "Targets" are not restricted to enemy units.
Groups:
Object Detection

Syntax

Syntax:
unit nearTargets range
Parameters:
unit: Object
range: Number
Return Value:
Array - Array of arrays in format:
  • 0: _position (perceived, includes judgment and memory errors)
  • 1: _type (perceived, gives only what was recognized)
  • 2: _side (perceived side)
  • 3: _subjectiveCost (positive for enemies, more positive for more important or more dangerous enemies)
  • 4: _object (object type, can be used to get more information if needed)
  • 5: _positionAccuracy (assumed accuracy of the perceived position)

Examples

Example 1:
player nearTargets 100;// Could return something like this: [[[2555.33,2535.33,1.32708],"SoldierEB",EAST,214222,EAST 1-1-A:1],[[2550.39,2482.5,1.32696],"SoldierWB",WEST,0,WEST 1-1-A:2]]

Additional Information

See also:
revealknowsAboutfindNearestEnemynearestBuildingnearestObjectnearestObjectsnearObjectsnearestLocationnearEntitiesnearSuppliesnearestLocationWithDubbingnearObjectsReadynearRoadsforgetTarget

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 Febuary 17, 2011
Curry
A subjective cost greater than 0 does not necessarily mean the target is an enemy unit. Any unit, that have yet to be identified by the unit, have a small positive cost in the range 0 to 1.
Posted on January 15, 2012
kju
The quality/detail level of the info depends on the knowsAbout value of the sourceUnit about the targetUnit:
  • For infantry:
    • ] 0 , 1.5 [ - side unknown, some position offset, identified as SoldierWB
    • [ 1.5, 1.6 [ - side identified, subjective cost set
    • [ 1.6, 2 [ - type identified better (USMC_Soldier_Base)
    • [ 2 , 3.6 [ - type identified precisely (USMC_Soldier)
    • [ 3.6, 4 ] - position identified precisely
The values seems closely linked to the accuracy value of the given targetUnit class and its parents up in the config tree:
  • 0 class CAManBase: Man
  • 1.6 class SoldierWB: CAManBase
  • 2 class USMC_Soldier_Base: SoldierWB
  • 3.9 class USMC_Soldier: USMC_Soldier_Base
  • For tanks:
    • ] 0 , 0.03 [ - side unknown, some position offset, identified as LandVehicle
    • [ 0.03, 0.13 [ - type identified better (Tank)
    • [ 0.13, 0.3 [ - type identified better (M1A1)
    • [ 0.3 , 1.5 [ - side identified, subjective cost set
    • [ 1.5 , 3.6 [ - side identified precisely (CIV), subjective cost adjusted
    • [ 3.6 , 4 ] - position identified precisely
The values seems closely linked to the accuracy value of the given targetUnit class and its parents up in the config tree:
  • 0 class All
  • class AllVehicles: All
    • 0.0005 class Land: AllVehicles
    • 0.02 class LandVehicle: Land
    • 0.12 class Tank: LandVehicle
    • 0.25 class M1A1: Tank
Posted on January 17, 2012
kju
  • When an unit dies, it is nearTargets array gets emptied after some seconds.
  • When an unit dies, its reference will get removed from other units nearTargets' arrays immediately.
  • A target will be removed from the array after about 360 seconds without contact.
Posted on January 21, 2012
kju
Position accuracy seems to be a radius in meters from the perceived position.
Retrieved from "https://community.bistudio.com/wiki?title=nearTargets&oldid=252028"