Maps editing workflow - Revision history

Talad at 21:47, 24 November 2025

2025-11-24T21:47:58Z

← Older revision		Revision as of 21:47, 24 November 2025
Line 1:		Line 1:
			== How Landscape is setup ==
			In the outliner we have a Landscape Object. If you click on it, you see the details it's linked to a MI_Landscape.


			MI_Landscape contains all the parameters including the visibility of rocks , grass, etc...

			The actual meshes are part of "Landscape Grass Type" a special object that can contain a mesh, its density, culling distance, etc...

			M_Landscape has a special node called : "Landscape Grass" of type "Landscape Grass Output". It the detail panel of this node, there are all the "Landscape Grass Type" linked with a name (which is the name of the layer).


	=== Landscape limits ===		=== Landscape limits ===

Talad: /* Landscape limits */

2022-11-27T16:38:02Z

Landscape limits

← Older revision		Revision as of 16:38, 27 November 2022
Line 2:		Line 2:
	=== Landscape limits ===		=== Landscape limits ===
	Vertically our landscape can go from -250 meters up to +250 meters, if you try to go beyond these values you just get flat terrain at the max height and you cant go beyond.		Vertically our landscape can go from -250 meters up to +250 meters, if you try to go beyond these values you just get flat terrain at the max height and you cant go beyond.

			Our maps at the moment have the lowest point to the south of Homestead where it reach -177 meters. Plus we need to consider the Death Ream boundaries, that reach at the moment -199 meters.

			We have set the Kill Z value to -185 meters.

	=== Notes ===		=== Notes ===

Talad at 16:26, 27 November 2022

2022-11-27T16:26:59Z

← Older revision		Revision as of 16:26, 27 November 2022
Line 1:		Line 1:

			=== Landscape limits ===
			Vertically our landscape can go from -250 meters up to +250 meters, if you try to go beyond these values you just get flat terrain at the max height and you cant go beyond.

	=== Notes ===		=== Notes ===

Talad: Created page with " === Notes === * BuiltData files are storing: lightmap textures (created by Build Lighting only) volumetric light probes / samples (created by Build Lighting only) * umap files are storing: ** navigation paths (created by Build Paths) === Map creation flow === You should never upload BuiltData file in SVN. Those will be regenerated when we create the shipping release. If you want to test locally the full game including lights then you need to: * Load all the le..."

2022-05-24T22:04:18Z

Created page with " === Notes === * BuiltData files are storing: ** lightmap textures (created by Build Lighting only) ** volumetric light probes / samples (created by Build Lighting only) * umap files are storing: ** navigation paths (created by Build Paths) === Map creation flow === You should never upload BuiltData file in SVN. Those will be regenerated when we create the shipping release. If you want to test locally the full game including lights then you need to: * Load all the le..."

New page

=== Notes ===

* BuiltData files are storing:
** lightmap textures (created by Build Lighting only)
** volumetric light probes / samples (created by Build Lighting only)
* umap files are storing:
** navigation paths (created by Build Paths)

=== Map creation flow ===
You should never upload BuiltData file in SVN. Those will be regenerated when we create the shipping release.

If you want to test locally the full game including lights then you need to:

* Load all the levels and Build Lighting only, this gives the best result on map borders, but I think you can avoid it

OR

* Load Persistent Level + one or more maps you want relit, and Build Lighting only. In this case the single maps will be ok, but the borders between maps will not

If you want to test locally the full game including NPC movement then you need to:

* Follow Option 1 in [[PSUnreal Navigation Meshes|this page]].