nearTargets: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}")
m (Some wiki formatting)
 
(31 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{RV|type=command
{{RV|type=command


|arma1
|game1= arma1
|version1= 1.07


|1.07
|game2= arma2
|version2= 1.00
 
|game3= arma2oa
|version3= 1.50
 
|game4= tkoh
|version4= 1.00
 
|game5= arma3
|version5= 0.50


|gr1= Object Detection
|gr1= Object Detection


| Returns a list of targets within the defined range. "Targets" are not restricted to enemy units.
|descr= Returns a list of targets within the defined range. "Targets" are not restricted to enemy units.


| unit '''nearTargets''' range
|s1= unit [[nearTargets]] range


|p1= unit: [[Object]]
|p1= unit: [[Object]]
|p2= range: [[Number]]
|p2= range: [[Number]]


| [[Array]] - nested; consisting of:
|r1= [[Array]] of [[Array]]s in format [position, type, side, subjectiveCost, object, positionAccuracy]:
*0: Position (perceived, includes judgment and memory errors),
* position: [[Array]] format [[Position#Position3D|Position3D]] - perceived position including judgment and memory errors
*1: Type (perceived, gives only what was recognized),
* type: [[String]] - perceived, gives only what was recognized
*2: Side (perceived side),
* side: [[Side]] - perceived side
*3: Subjective Cost (positive for enemies, more positive for more important or more dangerous  
* subjectiveCost: [[Number]] - positive for enemies, more positive for more important or more dangerous enemies
enemies),
* object: [[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)
* positionAccuracy: [[Number]] - assumed accuracy of the perceived position
*5: (since build 5209:) position accuracy (assumed accuracy of the perceived position)


'''for each recognized target'''
|x1= <sqf>
player nearTargets 100;
// can return e.g
/*
[
[[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]
]
*/
</sqf>


 
|seealso= [[targets]] [[targetsQuery]] [[targetsAggregate]] [[targetKnowledge]] [[knowsAbout]] [[reveal]] [[forgetTarget]] [[setTargetAge]] [[getHideFrom]] [[findNearestEnemy]] [[nearestBuilding]] [[nearestObject]] [[nearestObjects]] [[nearObjects]] [[nearestLocation]] [[nearEntities]] [[nearSupplies]] [[nearestLocationWithDubbing]] [[nearObjectsReady]] [[nearRoads]] [[nearestMines]]
|x1= <code>[[player]] [[nearTargets]] 100;</code>could return something like this: <br>
}}
<nowiki>[[[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]]</nowiki>


|seealso= [[reveal]], [[knowsAbout]], [[findNearestEnemy]], [[nearestBuilding]], [[nearestObject]], [[nearestObjects]], [[nearObjects]], [[nearestLocation]], [[nearEntities]], [[nearSupplies]], [[nearestLocationWithDubbing]], [[nearObjectsReady]], [[nearRoads]], [[forgetTarget]]
{{Note
|user= mrcurry
|timestamp= 20110217160000
|text= 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.
}}
}}


<dl class="command_description">
{{Note
<!-- Note Section BEGIN -->
|user= .kju
|timestamp= 20120115174500
|text= The quality/detail level of the info depends on the [[knowsAbout]] value of the sourceUnit about the targetUnit:


<dd class="notedate">Posted on Febuary 17, 2011</dd>
* For infantry:
<dt class="note">[[User:Curry|Curry]]</dt>
** ] 0  , 1.5 [ - side unknown, some position offset, identified as SoldierWB
<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.
** [ 1.5, 1.6 [ - side identified, subjective cost set
 
** [ 1.6, 2  [ - type identified better (USMC_Soldier_Base)
<dd class="notedate">Posted on January 15, 2012</dd>
** [ 2  , 3.6 [ - type identified precisely (USMC_Soldier)
<dt class="note">[[User:kju|kju]]</dt>
** [ 3.6, 4  ] - position identified precisely
<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:
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
* 0 class CAManBase : Man
1.6 class SoldierWB: CAManBase
* 1.6 class SoldierWB : CAManBase
2 class USMC_Soldier_Base: SoldierWB
* 2 class USMC_Soldier_Base : SoldierWB
3.9 class USMC_Soldier: USMC_Soldier_Base
* 3.9 class USMC_Soldier : USMC_Soldier_Base


For tanks:
* For tanks:
] 0  , 0.03 [ - side unknown, some position offset, identified as LandVehicle
** ] 0  , 0.03 [ - side unknown, some position offset, identified as LandVehicle
[ 0.03, 0.13 [ - type identified better (Tank)
** [ 0.03, 0.13 [ - type identified better (Tank)
[ 0.13, 0.3  [ - type identified better (M1A1)
** [ 0.13, 0.3  [ - type identified better (M1A1)
[ 0.3 , 1.5  [ - side identified, subjective cost set
** [ 0.3 , 1.5  [ - side identified, subjective cost set
[ 1.5 , 3.6  [ - side identified precisely (CIV), subjective cost adjusted
** [ 1.5 , 3.6  [ - side identified precisely (CIV), subjective cost adjusted
[ 3.6 , 4    ] - position identified precisely
** [ 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:
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
* 0 class All
class AllVehicles: All
* class AllVehicles : All
  0.0005 class Land: AllVehicles
** 0.0005 class Land : AllVehicles
  0.02 class LandVehicle: Land
** 0.02 class LandVehicle : Land
  0.12 class Tank: LandVehicle
** 0.12 class Tank : LandVehicle
  0.25 class M1A1: Tank
** 0.25 class M1A1 : Tank
}}


<dd class="notedate">Posted on January 17, 2012</dd>
{{Note
<dt class="note">[[User:kju|kju]]</dt>
|user= .kju
<dd class="note">When an unit dies, it is nearTargets array gets emptied after some seconds.
|timestamp= 20120117161400
<dd class="note">When an unit dies, its reference will get removed from other units nearTargets' arrays immediately.
|text= <nowiki/>
<dd class="note">A target will be removed from the array after about 360 seconds without contact.
* 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>
{{Note
<dt class="note">[[User:kju|kju]]</dt>
|user= .kju
<dd class="note">Position accuracy seems to be a radius in meters from the perceived position.
|timestamp= 20120121200000
 
|text= Position accuracy seems to be a radius in meters from the perceived position.
<!-- Note Section END -->
}}
</dl>
 
 
{{GameCategory|arma1|Scripting Commands}}
{{GameCategory|arma2|Scripting Commands}}
{{GameCategory|arma3|Scripting Commands}}
{{GameCategory|tkoh|Scripting Commands}}

Latest revision as of 12:50, 12 March 2024

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 of Arrays in format [position, type, side, subjectiveCost, object, positionAccuracy]:
  • position: Array format Position3D - perceived position including judgment and memory errors
  • type: String - perceived, gives only what was recognized
  • side: Side - perceived side
  • subjectiveCost: Number - positive for enemies, more positive for more important or more dangerous enemies
  • object: Object object type, can be used to get more information if needed
  • positionAccuracy: Number - assumed accuracy of the perceived position

Examples

Example 1:
player nearTargets 100; // can return e.g /* [ [[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:
targets targetsQuery targetsAggregate targetKnowledge knowsAbout reveal forgetTarget setTargetAge getHideFrom findNearestEnemy nearestBuilding nearestObject nearestObjects nearObjects nearestLocation nearEntities nearSupplies nearestLocationWithDubbing nearObjectsReady nearRoads nearestMines

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
mrcurry - c
Posted on Feb 17, 2011 - 16:00 (UTC)
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.
.kju - c
Posted on Jan 15, 2012 - 17:45 (UTC)
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
.kju - c
Posted on Jan 17, 2012 - 16:14 (UTC)
  • 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.
.kju - c
Posted on Jan 21, 2012 - 20:00 (UTC)
Position accuracy seems to be a radius in meters from the perceived position.