setMarkerPos: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "v1\.93\.[0-9]{6}" to "v1.94")
No edit summary
 
(40 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{RV|type=command
{{RV|type=command


| ofp
|game1= ofp
|version1= 1.00


|1.00
|game2= ofpe
|version2= 1.00


|gr1 = Markers
|game3= arma1
|version3= 1.00


|eff= global
|game4= arma2
|version4= 1.00


| Moves the marker. If position is given in 3D format, <tt>z</tt> coordinate is stored with the marker and will be used when marker is passed to commands like [[createVehicle]], [[createUnit]], [[createAgent]], [[createMine]], [[setVehiclePosition]] for example. When [[Object]] is used for position, [[PositionWorld]] of the object is used.
|game5= arma2oa
{{Feature|Informative|'''Multiplayer optimisation:''' Global marker commands always broadcast the ''entire'' marker state over the network. As such, the number of network messages exchanged when creating or editing a marker can be reduced by performing all but the last operation using local marker commands, then using a global marker command for the last change (and subsequent global broadcast of all changes applied to the marker).}}
|version5= 1.50


| markerName '''setMarkerPos''' pos
|game6= tkoh
|version6= 1.00


|p1= markerName: [[String]]
|game7= arma3
|p2= pos: [[Array]] - format [[Position2D]], [[PositionAGL]] or [[Object]] (since Arma 3 v1.94)
|version7= 0.50


| [[Nothing]]
|gr1= Markers
 
|x1= <code>"MarkerOne" '''setMarkerPos''' [[getMarkerPos]] "MarkerTwo"</code>


|seealso= [[setMarkerPosLocal]], [[setMarkerBrush]], [[setMarkerColor]], [[setMarkerDir]], [[createMarker]], [[setMarkerShape]], [[setMarkerSize]], [[setMarkerText]], [[setMarkerType]], [[setMarkerAlpha]]
|eff= global
 
|descr= Moves the marker. If position is given in 3D format, {{hl|z}} coordinate is stored with the marker and will be used when marker is passed to commands like [[createVehicle]], [[createUnit]], [[createAgent]], [[createMine]], [[setVehiclePosition]] for example. In case of an object, the object's model [0,0,0] is used.
{{Feature|informative|
'''Multiplayer optimisation:''' Global marker commands always broadcast the ''entire'' marker state over the network.
As such, the number of network messages exchanged when creating or editing a marker can be reduced by performing all but the last operation using local marker commands, then using a global marker command for the last change (and subsequent global broadcast of all changes applied to the marker).
}}
}}


<dl class="command_description">
|s1= markerName [[setMarkerPos]] position
<!-- Note Section BEGIN -->


<dt class="note">[[User:Pulverizer|Pulverizer]]</dt>
|p1= markerName: [[String]]
<dd class="note">Effect is local in OFP.


<dd class="notedate">Posted on August 7, 2009 - 02:03 (CEST)</dd>
|p2= position: [[Array]] format [[Position#Introduction|Position2D]] or [[Position#PositionAGL|PositionAGL]] or {{GVI|arma3|1.94|size= 0.75}} [[Object]]. In case of an object, the object's model [0,0,0] is used.
<dt class="note">[[User:Dr Eyeball|Dr Eyeball]]</dt>
|r1= [[Nothing]]
<dd class="note">The marker position can actually be set in 3D. This has a benefit for respawn markers, when placed at the correct altitude ASL on the LHD, the correct altitude will be used for respawn. There is no particular benefit for regular markers since [[markerPos]] will still return 0 for the altitude array element. <!-- Tip obtained from Xeno -->


<!-- Note Section END -->
|x1= <sqf>"MarkerOne" setMarkerPos getMarkerPos "MarkerTwo";</sqf>
</dl>


|seealso= [[setMarkerPosLocal]] [[setMarkerBrush]] [[setMarkerColor]] [[setMarkerDir]] [[createMarker]] [[setMarkerShape]] [[setMarkerSize]] [[setMarkerText]] [[setMarkerType]] [[setMarkerAlpha]]
}}
{{Note
|user= Pulverizer
|timestamp= 20070323234700
|text= Effect is local in OFP.
|game= ofp
}}


{{GameCategory|arma1|Scripting Commands}}
{{Note
{{GameCategory|arma2|Scripting Commands}}
|user= Dr Eyeball
{{GameCategory|arma3|Scripting Commands}}
|timestamp= 20090807020300
{{GameCategory|tkoh|Scripting Commands}}
|text= The marker position can actually be set in 3D. This has a benefit for respawn markers, when placed at the correct altitude ASL on the LHD, the correct altitude will be used for respawn.
There is no particular benefit for regular markers since [[markerPos]] will still return 0 for the altitude array element. // Tip obtained from Xeno
}}

Latest revision as of 11:56, 1 November 2024

Hover & click on the images for description

Description

Description:
Moves the marker. If position is given in 3D format, z coordinate is stored with the marker and will be used when marker is passed to commands like createVehicle, createUnit, createAgent, createMine, setVehiclePosition for example. In case of an object, the object's model [0,0,0] is used.
Multiplayer optimisation: Global marker commands always broadcast the entire marker state over the network. As such, the number of network messages exchanged when creating or editing a marker can be reduced by performing all but the last operation using local marker commands, then using a global marker command for the last change (and subsequent global broadcast of all changes applied to the marker).
Groups:
Markers

Syntax

Syntax:
markerName setMarkerPos position
Parameters:
markerName: String
position: Array format Position2D or PositionAGL or Arma 3 logo black.png1.94 Object. In case of an object, the object's model [0,0,0] is used.
Return Value:
Nothing

Examples

Example 1:
"MarkerOne" setMarkerPos getMarkerPos "MarkerTwo";

Additional Information

See also:
setMarkerPosLocal setMarkerBrush setMarkerColor setMarkerDir createMarker setMarkerShape setMarkerSize setMarkerText setMarkerType setMarkerAlpha

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
Pulverizer - c
Posted on Mar 23, 2007 - 23:47 (UTC)

Effect is local in OFP.

Dr Eyeball - c
Posted on Aug 07, 2009 - 02:03 (UTC)
The marker position can actually be set in 3D. This has a benefit for respawn markers, when placed at the correct altitude ASL on the LHD, the correct altitude will be used for respawn. There is no particular benefit for regular markers since markerPos will still return 0 for the altitude array element. // Tip obtained from Xeno