setPos: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - "<code>([^<]*)\[\[([a-zA-Z][a-zA-Z0-9_]+)\]\]([^<]*)<\/code>" to "<code>$1$2$3</code>") |
Lou Montana (talk | contribs) m (Text replacement - "<sqf>([^↵][^\/]*↵[^\/]*)<\/sqf>" to "<sqf> $1 </sqf>") |
||
| (17 intermediate revisions by the same user not shown) | |||
| Line 29: | Line 29: | ||
|descr= Sets object position to format [[Position#PositionAGLS|PositionAGLS]] (over surface). The Z value is used to calculate the nearest surface below the provided position. If the surface is close, it uses the Z position of the surface. Otherwise, Z value becomes the offset from that surface. | |descr= Sets object position to format [[Position#PositionAGLS|PositionAGLS]] (over surface). The Z value is used to calculate the nearest surface below the provided position. If the surface is close, it uses the Z position of the surface. Otherwise, Z value becomes the offset from that surface. | ||
{{Feature| important | It is recommended to '''avoid''' this command when placing objects above other objects, due to the unpredictable behavior described above.}} | {{Feature| important | It is recommended to '''avoid''' this command when placing objects above other objects, due to the unpredictable behavior described above.}} | ||
|mp= {{Feature|arma1|{{Name|arma1|short}} 1.00 to 1.06: this command has local effect, but some simulation types do synchronise their changes over the network whilst others do not.<br> | |mp= {{Feature|arma1|{{Name|arma1|short}} 1.00 to 1.06: this command has local effect, but some simulation types do synchronise their changes over the network whilst others do not.<br> | ||
So far, the only known simulation type that doesn't synchronise its position over the net is "static" ({{hl|c= simulation{{=}}"house"}}).}} | So far, the only known simulation type that doesn't synchronise its position over the net is "static" ({{hl|c= simulation{{=}}"house"}}).}} | ||
| Line 40: | Line 41: | ||
|r1= [[Nothing]] | |r1= [[Nothing]] | ||
|x1= < | |x1= <sqf> | ||
player setPos [getPos player select 0, getPos player select 1, (getPos player select 2) +10]; | |||
// the same as above using | // the same as above using set (OFP:R v1.75) | ||
player [ | _pos = getPos player; | ||
_pos set [2, _pos select 2 + 10]; | |||
player setPos _pos; | |||
// the same as above using | // the same as above using modelToWorld (ArmA v1.00) | ||
player setPos (player modelToWorld [0,0,10]); | |||
|x2= < | // the same as above using vectorAdd (Arma 3 v1.22) | ||
player setPos (getPos player vectorAdd [0,0,10]); | |||
</sqf> | |||
|x2= <sqf>_obj setPos [getPos _obj select 0, getPos _obj select 1, -5];</sqf> | |||
|x3= <sqf>player setPos (getPos _obj);</sqf> | |x3= <sqf>player setPos (getPos _obj);</sqf> | ||
|seealso= | |seealso= [[setPosASL]] [[getPos]] [[setVehiclePosition]] [[Position#setPosAGLS|setPosAGLS]] | ||
}} | }} | ||
{{Note | |||
|user= Hduregger | |||
|timestamp= 20110206202000 | |||
|text= 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''': | Comment applicable to Ver '''1.96''' and '''earlier''': | ||
<sqf>obj1 setPos [x,y,z]</sqf> | |||
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: | 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: | ||
< | <sqf> | ||
triggername setPos [x,y,abs(getPos triggername select 2)];</ | triggername setPos [x,y,0]; | ||
triggername setPos [x,y,abs(getPos triggername select 2)]; | |||
</sqf> | |||
Note for {{Name|arma1|short}}: 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. | Note for {{Name|arma1|short}}: 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 an ammo crate do not work in MP. | [[setPos]] for static objects like an ammo crate do not work in MP. | ||
}} | |||
{{Note | |||
|user= Tankbuster | |||
|timestamp= 20121123130600 | |||
|text= You can use [[getPos]] and [[setPos]] on triggers. | |||
You can use [[getPos]] and [[setPos]] on triggers. | }} | ||
Latest revision as of 11:34, 3 September 2024
Description
- Description:
- Sets object position to format PositionAGLS (over surface). The Z value is used to calculate the nearest surface below the provided position. If the surface is close, it uses the Z position of the surface. Otherwise, Z value becomes the offset from that surface.
- Multiplayer:
ArmA 1.00 to 1.06: this command has local effect, but some simulation types do synchronise their changes over the network whilst others do not.
So far, the only known simulation type that doesn't synchronise its position over the net is "static" (simulation="house").- Groups:
- Positions
Syntax
- Syntax:
- object setPos pos
- Parameters:
- object: Object
- pos: Array - position in format PositionAGL or Position2D, in which case Z will be set to 0
- 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 set (OFP:R v1.75) _pos = getPos player; _pos set [2, _pos select 2 + 10]; player setPos _pos; // the same as above using modelToWorld (ArmA v1.00) player setPos (player modelToWorld [0,0,10]); // the same as above using vectorAdd (Arma 3 v1.22) player setPos (getPos player vectorAdd [0,0,10]);
- Example 2:
- Example 3:
Additional Information
- See also:
- setPosASL getPos setVehiclePosition setPosAGLS
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 Feb 06, 2011 - 20:20 (UTC)
-
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:
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: Note for ArmA: 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 an ammo crate do not work in MP.obj1 setPos [x,y,z]
Categories:
- Scripting Commands
- Introduced with Operation Flashpoint version 1.00
- Operation Flashpoint: New Scripting Commands
- Operation Flashpoint: Scripting Commands
- Operation Flashpoint: Elite: Scripting Commands
- ArmA: Armed Assault: Scripting Commands
- Arma 2: Scripting Commands
- Arma 2: Operation Arrowhead: Scripting Commands
- Take On Helicopters: Scripting Commands
- Arma 3: Scripting Commands
- Command Group: Positions
- Scripting Commands: Global Effect