setPos: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " <dl class="command_description"> <dt><dt>" to " <dl class="command_description"> <dt><dt>") |
Lou Montana (talk | contribs) m (Text replacement - "]]<dd class="note">" to "]]</dt> <dd class="note">") |
||
Line 42: | Line 42: | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on 6 Feb, 2011</dd> | <dd class="notedate">Posted on 6 Feb, 2011</dd> | ||
<dt class="note">[[User:Hduregger|Hduregger]]<dd class="note"> | <dt class="note">[[User:Hduregger|Hduregger]]</dt> | ||
<dd class="note"> | |||
Calling [[setPos]] on an object can cause the object's orientation to change. This depends on the terrain and/or objects below the object. This was tested by calling [[setPos]] on a test object with the position of a helicopter ([[modelToWorld]] with some offset). When flying over land the orientation of the test object would rapidly change depending on the slope of the ground and objects beneath it. | Calling [[setPos]] on an object can cause the object's orientation to change. This depends on the terrain and/or objects below the object. This was tested by calling [[setPos]] on a test object with the position of a helicopter ([[modelToWorld]] with some offset). When flying over land the orientation of the test object would rapidly change depending on the slope of the ground and objects beneath it. | ||
Comment applicable to Ver '''1.96''' and '''earlier''':<br> | Comment applicable to Ver '''1.96''' and '''earlier''':<br> | ||
Line 53: | Line 54: | ||
<dt><dt> | <dt><dt> | ||
<dd class="notedate">Posted on 23 Nov, 2011</dd> | <dd class="notedate">Posted on 23 Nov, 2011</dd> | ||
<dt class="note">[[User:Tankbuster|Tankbuster]]<dd class="note"> | <dt class="note">[[User:Tankbuster|Tankbuster]]</dt> | ||
<dd class="note"> | |||
You can use [[getPos]] and [[setPos]] on triggers. | You can use [[getPos]] and [[setPos]] on triggers. | ||
</dl> | </dl> |
Revision as of 18:33, 12 June 2021
Description
- Description:
- Description needed
- Multiplayer:
- ArmA 1.00 - 1.06: This command has local effect, but some simulation types do synchronise their changes over the network whilst others do not. The only known object types that currently, don't synchronise their positions over the net, are statics (simulation = "house"). Since ArmA 1.08 and later the command is global for every object again.
- Groups:
- Positions
Syntax
- Syntax:
- Syntax needed
- Parameters:
- object: Object
- pos: Array - position in format PositionAGL or Position2D
- Return Value:
- Nothing
Examples
- Example 1:
player setPos [getPos player select 0, getPos player select 1, (getPos player select 2) +10]; //the same as above using modelToWorld: player setPos (player modelToWorld [0,0,10]); //the same as above using vectorAdd: player setPos (getPos player vectorAdd [0,0,10]);
- Example 2:
_obj setPos [getPos _obj select 0, getPos _obj select 1, -5];
- Example 3:
player setPos (getPos _obj);
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 6 Feb, 2011
- Hduregger
-
Calling setPos on an object can cause the object's orientation to change. This depends on the terrain and/or objects below the object. This was tested by calling setPos on a test object with the position of a helicopter (modelToWorld with some offset). When flying over land the orientation of the test object would rapidly change depending on the slope of the ground and objects beneath it.
Comment applicable to Ver 1.96 and earlier:
obj1 setPos [x,y,z] Will place most objects z metres above ground level (negative numbers for underground). But if obj1 is a trigger then it will be placed z metres above sea level. This can be very useful if you want to check a unit's height above sea level but it can be a problem if you want to move a trigger to create an explosion or a sound. To move a trigger to a location at ground level:triggername setPos [x,y,0]; triggername setPos [x,y,abs(getPos triggername select 2)];
Note for Armed Assault: Using setPos for a trigger will work in exactly the same way that setPos works for other objects - namely that setPos [x,y,z] will place the trigger z metres above ground level. SetPos for static objects like a ammo crate do not work in MP. - Posted on 23 Nov, 2011
- Tankbuster
- You can use getPos and setPos on triggers.