setMarkerPolyline: Difference between revisions

Revision as of 00:09, 7 February 2021

-wrong parameter ("arma3dev") defined!-[[:Category:Introduced with arma3dev version 2.01|2.01]]

GEGlobal

Hover & click on the images for description

Description

Description:: Sets a polyline marker's path.
ⓘ
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:: marker setMarkerPolyline path
Parameters:: marker: String
: path: Array - [x1, y1, x2, y2, ... xn, yn]
⚠
Be aware that this command expects an array with a minimum array size of 4 elements and that the array count always needs to be dividable by 4 and return a whole number.
Return Value:: Nothing

Examples

Example 1:: Changes "marker_1" into a polyline and draws a sine curve on your position"marker_1" setMarkerShape "polyline"; private _return = [] ; for "_i" from 0 to 100 step 0.1 do { _return pushBack (_i + getPos player#0); _return pushBack ((sin (_i*10))*10 + getPos player#1); } ; "marker_1" setMarkerPolyline _return;

Additional Information

See also:: markerPolyline setMarkerPolylineLocal

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

[[Category:Introduced with arma3dev version 2.01]][[ Category: arma3dev: New Scripting Commands | SETMARKERPOLYLINE]][[ Category: arma3dev: Scripting Commands | SETMARKERPOLYLINE]]

@@ Line 10: / Line 10: @@
 |descr= Sets a polyline marker's path.
-{{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).}}
+{{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).}}
 |pr= |Problems=