DayZ:Configuring 2D Map - Revision history

Lou Montana: Text replacement - "aremeter" to "arameter"

2025-12-28T02:08:46Z

Text replacement - "aremeter" to "arameter"

← Older revision		Revision as of 04:08, 28 December 2025
Line 7:		Line 7:

	By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp'').		By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp'').
	Since {{GVI\|dayz\|1.06}}, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these ~~paremeters~~ in your world config:		Since {{GVI\|dayz\|1.06}}, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these parameters in your world config:

	<syntaxhighlight lang="cpp">		<syntaxhighlight lang="cpp">

Lou Montana: Some wiki formatting

2025-05-24T00:34:26Z

Some wiki formatting

Show changes

Lou Montana: Fix hl template issue

2025-05-22T21:26:10Z

Fix hl template issue

← Older revision		Revision as of 23:26, 22 May 2025
Line 1:		Line 1:
	{{TOC\|side}}		{{TOC\|side}}
	~~== Overview ==~~		DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance.
			It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world).
	DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world).

	== Base configuration ==		== Base configuration ==
	By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since ~~update~~ 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config:
			By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp'').
			Since {{GVI\|dayz\|1.06}}, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config:

	<syntaxhighlight lang="c++">		<syntaxhighlight lang="c++">
Line 11:		Line 13:
	{		{
	class CAWorld;		class CAWorld;
	class YourTerrain: CAWorld		class YourTerrain : CAWorld
	{		{
	// map item name (default value is #STR_CfgVehicles_ChernarusMap0)		// map item name (default value is #STR_CfgVehicles_ChernarusMap0)
Line 38:		Line 40:
	Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured:		Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured:

	<syntaxhighlight lang="~~c++~~">		<syntaxhighlight lang="cpp">
	class CfgWorlds		class CfgWorlds
	{		{
	class CAWorld;		class CAWorld;
	class YourTerrain: CAWorld		class YourTerrain : CAWorld
	{		{
	/* .. */		/* .. */
Line 50:		Line 52:
	class location_name		class location_name
	{		{
	name="LocationName";		name = "LocationName";
	position[]={11339.77,14391.05};		position[] = { 11339.77, 14391.05 };
	type="locationtype";		type = "locationtype";
	};		};
	};		};
Line 61:		Line 63:
	</syntaxhighlight>		</syntaxhighlight>

	'''name''' parameter can be also a string from the stringtable database (can be ~~localized~~).		'''name''' parameter can be also a string from the stringtable database (can be localised).
	'''position''' is a 2D position, specified in meters. Please keep in mind that positioning multiple labels close to each other can lead in some not being visible at all.		'''position''' is a 2D position, specified in meters. Please keep in mind that positioning multiple labels close to each other can lead in some not being visible at all.
	Available values for the '''type''' parameter are in the following table:		Available values for the '''type''' parameter are in the following table:

	{\| class="wikitable" style="width:100%;"		<div class="noresize">
			{\| class="wikitable" style="width: 100%;"
	\|-		\|-
	! Name !! Icon !! Notes		! Name !! Icon !! Notes
Line 105:		Line 108:
	\| VegetationVineyard \|\| DZ\gear\navigation\data\map_vineyard_ca \|\| Used for vineyards.		\| VegetationVineyard \|\| DZ\gear\navigation\data\map_vineyard_ca \|\| Used for vineyards.
	\|}		\|}
			</div>

	Changes in this config do not require map to be re-~~binarized~~.		Changes in this config do not require map to be re-binarised.


	== Values ~~for map property~~ ==		== Map Property Values ==

	Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically:		Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map.
			There can be 4 cases basically:

	* hidden from the map		* hidden from the map
	* icon only		* icon only
Line 116:		Line 123:
	* special case (roads, railway)		* special case (roads, railway)
	If you do not specify this property, it is automatically assumed that object will not be visible = default value for this property is map=hide.		If you do not specify this property, it is automatically assumed that object will not be visible = default value for this property is map=hide.

	{\| class="wikitable" style="width:100%;"		<div class="noresize">
			{\| class="wikitable" style="width: 100%"
	\|-		\|-
	! Name !! Icon !! Hides BBox !! Notes		! Name !! Icon !! Hides BBox !! Notes
Line 199:		Line 207:
	\| ruin \|\| dz\gear\navigation\data\map_ruin_ca \|\| no \|\| Not used at the moment, it is recommended to use location type Ruin instead.		\| ruin \|\| dz\gear\navigation\data\map_ruin_ca \|\| no \|\| Not used at the moment, it is recommended to use location type Ruin instead.
	\|}		\|}
			</div>

	Changes of the map property in the models require map to be re-~~binarized~~.		Changes of the map property in the models require map to be re-binarised.


	{{GameCategory\|dayz\|Terrain Editing}}		{{GameCategory\|dayz\|Terrain Editing}}

Lou Montana: Fix hl template issue

2025-05-22T21:22:24Z

Fix hl template issue

Show changes

Lou Montana: Text replacement - "Category:DayZ:Terrain_Editing" to "{{GameCategory|dayz|Terrain Editing}}"

2023-04-24T23:18:25Z

Text replacement - "Category:DayZ:Terrain_Editing" to "{{GameCategory|dayz|Terrain Editing}}"

← Older revision		Revision as of 01:18, 25 April 2023
Line 203:		Line 203:


	~~[[Category:DayZ:Terrain_Editing]]~~		{{GameCategory\|dayz\|Terrain Editing}}

Lou Montana: Fix `usage`

2022-05-27T16:09:51Z Fix <tt> usage Show changes

Lou Montana: Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 " 2021-01-31T18:33:32Z Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 " ← Older revision Revision as of 20:33, 31 January 2021 Line 1: Line 1: [[Category:DayZ:Terrain_Editing]] [[Category:DayZ:Terrain_Editing]] ==Overview== == Overview == DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world). DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world). ==Base configuration== == Base configuration == By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config: By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config: Line 34: Line 34: The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). ==Location labels== == Location labels == Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured: Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured: Line 108: Line 108: Changes in this config do not require map to be re-binarized. Changes in this config do not require map to be re-binarized. ==Values for map property== == Values for map property == Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically: Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically: R3vo: category 2020-12-27T16:02:31Z category ← Older revision Revision as of 18:02, 27 December 2020 Line 1: Line 1: [[Category:DayZ:Editing|Terrain]] [[Category:DayZ:Terrain_Editing]] [[Category:DayZ:Terrain_Editing|Terrain]] ==Overview== ==Overview== Sumrak: edit for 1.06 2019-10-30T10:32:00Z edit for 1.06 ← Older revision Revision as of 12:32, 30 October 2019 Line 7: Line 7: ==Base configuration== ==Base configuration== By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the necessary configuration is included per specific map item (located at ''DZ\gear\navigation\config.cpp''). The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). If you are interested in creating a custom map item (with custom model) and specific 2D map configuration, I recommend you to take a look at the sample included at the end of this page. By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config: <syntaxhighlight lang="c++"> class CfgWorlds { class CAWorld; class YourTerrain: CAWorld { // map item name (default value is #STR_CfgVehicles_ChernarusMap0) mapDisplayNameKey = ""; // map item description (default value is #STR_CfgVehicles_ChernarusMap1) mapDescriptionKey = ""; // closed map item texture (default value is dz\gear\navigation\data\map_chernarus_co.paa) mapTextureClosed = ""; // opened map item texture (check dz\structures\signs\tourist\data\karta_co.paa to see how it should look like) mapTextureOpened = ""; // opened map item legend part (check dz\structures\signs\tourist\data\karta_side_co.paa to see how it should look like) mapTextureLegend = ""; // 2D map overlay map for this world (see dz\gear\navigation\data\usermap for an example - it is basically same like proper satellite texture for the terrain just with different sort of info) userMapPath = ""; }; }; </syntaxhighlight> After configuring this, you can freely use item called ''ChernarusMap'' (do not be confused by its name) on your terrain while using custom textures and text that fits your terrain. The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). ==Location labels== ==Location labels== Line 176: Line 202: Changes of the map property in the models require map to be re-binarized. Changes of the map property in the models require map to be re-binarized. ==Sample== You can take a look at [https://data.bistudio.com/download/dayz/dayz_moddingsamples_r1.zip DayZ Samples package] to see an example of probably the simplest possible implementation of brand new map item (with ability to have a custom texture and model) for a new terrain (look out for ''Test_MapItem'' folder). Sumrak: Created page with "Terrain Terrain ==Overview== DayZ supports generating a 2D map from the terrain data, which means this map is a..." 2019-06-26T15:14:40Z Created page with "Terrain Terrain ==Overview== DayZ supports generating a 2D map from the terrain data, which means this map is a..." New page [[Category:DayZ:Editing|Terrain]] [[Category:DayZ:Terrain_Editing|Terrain]] ==Overview== DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world). ==Base configuration== By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the necessary configuration is included per specific map item (located at ''DZ\gear\navigation\config.cpp''). The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). If you are interested in creating a custom map item (with custom model) and specific 2D map configuration, I recommend you to take a look at the sample included at the end of this page. ==Location labels== Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured: <syntaxhighlight lang="c++"> class CfgWorlds { class CAWorld; class YourTerrain: CAWorld { /* .. */ /* locations definition */ class Names { class location_name { name="LocationName"; position[]={11339.77,14391.05}; type="locationtype"; }; }; /* end of locations definition */ /* .. */ }; }; </syntaxhighlight> '''name''' parameter can be also a string from the stringtable database (can be localized). '''position''' is a 2D position, specified in meters. Please keep in mind that positioning multiple labels close to each other can lead in some not being visible at all. Available values for the '''type''' parameter are in the following table: {| class="wikitable" style="width:100%;" |- ! Name !! Icon !! Notes |- | Capital || none || <tt>Used for biggest settlements.</tt> |- | City || none || <tt>Used for mid-sized settlements.</tt> |- | Village || none || <tt>Used for small settlements.</tt> |- | Local || none || <tt>Used for miscellaneous locations.</tt> |- | Marine || none || <tt>Used for coastal locations (bays) or in-land water bodies.</tt> |- | Ruin || DZ\gear\navigation\data\map_ruin_ca || <tt>Used for castles.</tt> |- | Camp || DZ\gear\navigation\data\map_camp_ca || <tt>Used for summer camps.</tt> |- | Hill || DZ\gear\navigation\data\map_hill_ca || <tt>Used for mountains.</tt> |- | ViewPoint || DZ\gear\navigation\data\map_viewpoint_ca || <tt>Used for places with nice views (without text usually).</tt> |- | RockArea || DZ\gear\navigation\data\map_rock_ca || <tt>Used for larger parts with lot of rocks around.</tt> |- | RailroadStation || DZ\gear\navigation\data\map_station_ca || <tt>Used for rail stations.</tt> |- | IndustrialSite || DZ\gear\navigation\data\map_factory_ca || <tt>Used for large industrial areas.</tt> |- | LocalOffice || DZ\gear\navigation\data\map_govoffice_ca || <tt>Used for local offices (with Public Address System panels).</tt> |- | BorderCrossing || DZ\gear\navigation\data\map_border_cross_ca || <tt>Used for border crossings.</tt> |- | VegetationBroadleaf || DZ\gear\navigation\data\map_broadleaf_ca || <tt>Used for larger forest areas.</tt> |- | VegetationFir || DZ\gear\navigation\data\map_fir_ca || <tt>Used for larger forest areas.</tt> |- | VegetationPalm || DZ\gear\navigation\data\map_palm_ca || <tt>Used for larger forest areas.</tt> |- | VegetationVineyard || DZ\gear\navigation\data\map_vineyard_ca || <tt>Used for vineyards.</tt> |} Changes in this config do not require map to be re-binarized. ==Values for map property== Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically: * hidden from the map * icon only * icon and bounding box * special case (roads, railway) If you do not specify this property, it is automatically assumed that object will not be visible = default value for this property is map=hide. {| class="wikitable" style="width:100%;" |- ! Name !! Icon !! Hides BBox !! Notes |- | track || none || no || <tt>Width of the road included, color defined by the game config (class MapDefaults).</tt> |- | road || none || no || <tt>Width of the road included, color defined by the game config (class MapDefaults).</tt> |- | main road || none || no || <tt>Width of the road included, color defined by the game config (class MapDefaults).</tt> |- | power lines || none || yes || <tt>Color defined by the game config (class MapDefaults).</tt> |- | railway || none || yes || <tt>Color defined by the game config (class MapDefaults).</tt> |- | house || none || no || <tt>Color derived from the geometry LOD.</tt> |- | fence || none || no || <tt>Color derived from the geometry LOD.</tt> |- | wall || none || no || <tt>Color derived from the geometry LOD.</tt> |- | hide || none || yes || <tt>Use to hide object (default value).</tt> |- | bush || dz\gear\navigation\data\map_bush_ca || yes || <tt></tt> |- | small tree || dz\gear\navigation\data\map_smalltree_ca || yes || <tt>Used for small trees (orchards). They do not form forests triangles.</tt> |- | tree || dz\gear\navigation\data\map_tree_ca || yes || <tt>Used for solitary trees. Forest triangles are created (based on ''CfgWorlds'' parameter ''minTreesInForestSquare'').</tt> |- | rock || dz\gear\navigation\data\map_rock_ca || yes || <tt>Used on large rock cliffs. Rock triangles are created (based on ''CfgWorlds'' parameter ''minRocksInRockSquare'').</tt> |- | fuelstation || dz\gear\navigation\data\map_fuelstation_ca || yes || <tt></tt> |- | lighthouse || dz\gear\navigation\data\map_lighthouse_ca || yes || <tt></tt> |- | stack || dz\gear\navigation\data\map_stack_ca || yes || <tt></tt> |- | transmitter || dz\gear\navigation\data\map_transmitter_ca || yes || <tt></tt> |- | watertower || dz\gear\navigation\data\map_watertower_ca || yes || <tt></tt> |- | shipwreck || dz\gear\navigation\data\map_shipwreck_ca || yes || <tt></tt> |- | monument || dz\gear\navigation\data\map_monument_ca || yes || <tt></tt> |- | busstop || dz\gear\navigation\data\map_busstop_ca || yes || <tt></tt> |- | fountain || dz\gear\navigation\data\map_fountain_ca || yes || <tt></tt> |- | waterpump || dz\gear\navigation\data\map_waterpump_ca || yes || <tt></tt> |- | hospital || dz\gear\navigation\data\map_hospital_ca || no || <tt></tt> |- | store || dz\gear\navigation\data\map_store_ca || no || <tt></tt> |- | police || dz\gear\navigation\data\map_police_ca || no || <tt>Police department.</tt> |- | firedep || dz\gear\navigation\data\map_firedep_ca || no || <tt>Fire department.</tt> |- | tsign || dz\gear\navigation\data\map_tsign_ca || yes || <tt>Tourist directional sign.</tt> |- | tshelter || dz\gear\navigation\data\map_tshelter_ca || yes || <tt>Tourist shelter.</tt> |- | tourism || dz\gear\navigation\data\map_tourism_ca || yes || <tt>Usually used on pub-like objects.</tt> |- | cross || dz\gear\navigation\data\map_cross_ca || yes || <tt>Solitary crosses.</tt> |- | chapel || dz\gear\navigation\data\map_chapel_ca || no || <tt>Small churches - chapels.</tt> |- | church || dz\gear\navigation\data\map_church_ca || no || <tt>Big churches.</tt> |- | view-tower || dz\gear\navigation\data\map_viewtower_ca || yes || <tt>Used on small view-towers.</tt> |- | quay || dz\gear\navigation\data\map_quay_ca || yes || <tt>Not used at the moment. Can be used for selected pier objects.</tt> |- | bunker || dz\gear\navigation\data\map_bunker_ca || yes || <tt>Not used at the moment.</tt> |- | fortress || dz\gear\navigation\data\map_fortress_ca || yes || <tt>Not used at the moment.</tt> |- | rocks || dz\gear\navigation\data\map_rock_ca || yes || <tt>Not used at the moment.</tt> |- | ruin || dz\gear\navigation\data\map_ruin_ca || no || <tt>Not used at the moment, it is recommended to use location type Ruin instead.</tt> |} Changes of the map property in the models require map to be re-binarized. ==Sample== You can take a look at [https://data.bistudio.com/download/dayz/dayz_moddingsamples_r1.zip DayZ Samples package] to see an example of probably the simplest possible implementation of brand new map item (with ability to have a custom texture and model) for a new terrain (look out for ''Test_MapItem'' folder).

← Older revision		Revision as of 20:33, 31 January 2021
Line 1:		Line 1:
	[[Category:DayZ:Terrain_Editing]]		[[Category:DayZ:Terrain_Editing]]

	==Overview==		== Overview ==

	DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world).		DayZ supports generating a 2D map from the terrain data, which means this map is always up-to-date and does not require any other maintenance. It supports any terrain (including community made) with the limitation of showing only the map of currently loaded terrain (world).

	==Base configuration==		== Base configuration ==
	By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config:		By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config:

Line 34:		Line 34:
	The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp'').		The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp'').

	==Location labels==		== Location labels ==

	Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured:		Location labels is a feature of a 2D map, which is not tied to any specific map object and is defined within a CfgWorlds entry of a terrain (''class Names''). Following game config example shows how one can be configured:
Line 108:		Line 108:
	Changes in this config do not require map to be re-binarized.		Changes in this config do not require map to be re-binarized.

	==Values for map property==		== Values for map property ==

	Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically:		Each map object (p3d) can contain a named property called '''map''' in geometry LOD. This defines how such object should look like on the 2D map. There can be 4 cases basically:

← Older revision		Revision as of 18:02, 27 December 2020
Line 1:		Line 1:
	~~[[Category:DayZ:Editing\|Terrain]]~~		[[Category:DayZ:Terrain_Editing]]
	[[Category:DayZ:Terrain_Editing~~\|Terrain~~]]

	==Overview==		==Overview==

@@ Line 7: / Line 7: @@
 ==Base configuration==
-By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the necessary configuration is included per specific map item (located at ''DZ\gear\navigation\config.cpp''). The map UI can be also created independently of the map item, but then you will need to override in your mod a ''RscMapControl'' class (located in bin\config.cpp - it is recommended to base off the values that are at ''DZ\gear\navigation\config.cpp''). If you are interested in creating a custom map item (with custom model) and specific 2D map configuration, I recommend you to take a look at the sample included at the end of this page.
+By default, the GUI map layout with ''MapWidgetClass'' is displayed after executing an action on the map item (''ActionUnfoldMap'') and the configuration is included on the map item (located at ''DZ\gear\navigation\config.cpp''). Since update 1.06, map item has been made world independent with an ability to customise its visual look (as an item in 3D world) based on the currently loaded terrain. To configure this map item for your terrain, provide these paremeters in your world config:
 ==Location labels==
@@ Line 176: / Line 202: @@
 Changes of the map property in the models require map to be re-binarized.

DayZ:Configuring 2D Map - Revision history

Lou Montana: Text replacement - "aremeter" to "arameter"

Lou Montana: Some wiki formatting

Lou Montana: Fix hl template issue

Lou Montana: Fix hl template issue

Lou Montana: Text replacement - "Category:DayZ:Terrain_Editing" to "{{GameCategory|dayz|Terrain Editing}}"

Lou Montana: Fix usage

Lou Montana: Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

R3vo: category

Sumrak: edit for 1.06

Sumrak: Created page with "Terrain Terrain ==Overview== DayZ supports generating a 2D map from the terrain data, which means this map is a..."

Lou Montana: Fix `usage`

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "