createMarker

1.001.001.501.000.50

GEGlobal

Hover & click on the images for description

Description

Description:

Creates a new map marker at the given position. The marker will be created for every connected player as well as all JIP players. The marker name has to be unique; the command will be ignored if a marker with the given name already exists.

⚠

The marker will be visible only once at least markerType has been defined:

_marker = createMarker ["markername", player]; // Not visible yet. _marker setMarkerType "hd_dot"; // Visible.

ⓘ

If the marker position is given in 3D format, the z-coordinate is stored with the marker and will be used when the marker is passed to commands such as createVehicle, createUnit, createAgent, createMine or setVehiclePosition.
When a marker is manually placed in the editor, z is always 0, which means the marker is placed on the ground. But when the player places a marker on the map in game, it is placed at sea level, so the z-coordinate of that marker is -getTerrainHeightASL markerPos "userMarker";.

Multiplayer:

ⓘ

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).

Problems:

setMarkerDrawPriority sorts allMapMarkers from least to most priority. Before 2.18 createMarker/createMarkerLocal did not care about drawing priority and added the created marker to the end of the array, making it top priority. Running setMarkerDrawPriority again sorted this issue.

Groups:

Markers

Syntax

Syntax:

createMarker [name, position, channel, creator]

Parameters:

name: String - the marker's name, used to reference the marker in scripts.

position: Array or Object - Position2D, PositionAGL or Object. In case of an object, the object's boundingCenter is used.

since 2.02

channel: Number - (Optional, default -1) the marker channel - see Channel IDs (for multiplayer)

since 2.02

creator: Object - (Optional, default objNull) the marker creator (for multiplayer)

Return Value:

String - the marker's name or empty string if the marker name is not unique.

Examples

Example 1:

_marker1 = createMarker ["Marker1", position player];

Example 2:

_marker2 = createMarker ["Marker2", player]; // since Arma 3 1.50

Additional Information

See also:

createMarkerLocal deleteMarker BIS_fnc_markerToString BIS_fnc_stringToMarker

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

Soldia - c

Posted on Sep 19, 2015 - 21:02 (UTC)

1.50

createMarker accepts an object as position parameter as well . You could try this with the following code (both SP/MP)

_markerstr = createMarker ["markername", player]; _markerstr setMarkerShape "RECTANGLE"; _markerstr setMarkerSize [100, 100];

X39 - c

Posted on May 28, 2018 - 11:57 (UTC)

In Arma 3, one can create markers which are deletable by the user by prefixing the name with _USER_DEFINED. Example:

createMarker "_USER_DEFINED someMarkerName"

7erra - c

Posted on May 03, 2019 - 15:53 (UTC)

1.92

There is a new function with which you can create a marker with all settings applied in one step: BIS_fnc_stringToMarker and BIS_fnc_stringToMarkerLocal

Tirpitz - c

Posted on Jan 26, 2021 - 22:42 (UTC)

When creating a marker with the name format: "_USER_DEFINED #n1/n2/n3". n1 can be used to set the owner, n2 I think is an incrementing index to ensure markers are unique, to this end also mangle some more characters onto the end of the string, and n3 is the channel ID the marker is in.

_markerName = format ["_USER_DEFINED #%1/%2/%3" , clientOwner,_index, _ChannelID]; _marker = createMarkerLocal [_markerName, _pos];

POLPOX - c

Posted on Jul 08, 2023 - 16:03 (UTC)

If you use the letter "/" in the name, it may break the channel visibilities (especially in MP). Possible reason is described above by Tirpitz, the engine may confuse which channel the marker belongs to after the "/".