Stamping the Right Landscape When You Have Several in One Level (UE5)

In Unreal with multiple landscapes, which landscape does an edit affect?

The moment your level holds more than one landscape actor, every terrain tool faces an ambiguous question: when you drop a stamp at a given spot, which landscape is it meant to modify? This bites hardest in two setups - a World Partition world deliberately split into several landscape actors, and a level where two landscapes overlap in plan view because one is a sub-region or island sitting inside the bounds of another.

Get the binding wrong and the symptom is confusing rather than obvious. You place a mountain stamp expecting the foreground terrain to rise, and instead a landscape behind it deforms, or nothing visible happens because the stamp resolved to a tile you are not even looking at. Nothing errors; the edit just lands somewhere you did not intend. Landstamp Pro handles this with an explicit resolution rule rather than leaving it to chance, and this tutorial covers how a stamp picks its landscape, when that automatic choice is unreliable, and how to override it.

Auto-target: the XY footprint rule, nearest as fallback

By default a Landstamp actor resolves its landscape automatically, and the rule is geometric and predictable: the stamp binds to the landscape whose XY footprint contains the actor's position. It looks straight down, finds the landscape it stands over in plan view, and edits that one - which is exactly what you want in the common case, because the landscape you place a stamp over is almost always the one you mean to deform.

When the stamp is not directly over any landscape's footprint - it sits in a gap, off a tile edge, or in dead space between two World Partition landscapes - the rule falls back to the nearest landscape instead of doing nothing. That keeps placement forgiving. This behaviour is controlled by the bAutoTargetLandscape flag on the actor, which is on by default, so most of the time you do not think about targeting at all.

The rule only becomes a liability when two landscapes overlap in XY. If a smaller island landscape sits inside the footprint of a larger continental one, a stamp in that shared area is contained by both, and the tie-break may pick the one you were not thinking about - so an edit meant for the island lands on the continent beneath it. The tell is a preview that deforms terrain at a different height than expected. When that happens, stop relying on the guess and name the landscape outright.

Forcing an explicit target landscape

To pin a stamp to one landscape, select the Landstamp actor and, in its details panel, turn off bAutoTargetLandscape. That disables the contains-in-XY-else-nearest resolution so the stamp no longer tries to guess.

With auto-target off, set the TargetLandscape property to the landscape you want. TargetLandscape is a soft object reference to an ALandscape (a TSoftObjectPtr<ALandscape>), so you point it straight at the specific landscape actor in your level, and from then on the stamp edits that landscape and only that landscape regardless of which footprint it sits inside.

A practical workflow for overlapping terrain: place the stamp roughly where you want it while auto-target is still on, then turn auto-target off and set TargetLandscape to lock the binding before you commit. Use PreviewStamp (a CallInEditor function on the actor) to confirm it is deforming the intended landscape, ApplyToLandscape to commit, and ClearPreview to discard. Because every Landstamp edit is a non-destructive Landscape Patch, you can re-point TargetLandscape and re-apply later - nothing is baked permanently into the terrain.

Resolving the binding from Blueprint or an editor script

If you place stamps from an editor utility widget, a Blueprint, or a batch tool, you can drive the same resolution logic directly instead of inspecting properties by hand, because the Landstamp actor exposes its targeting as callable functions.

Call ResolveTargetLandscape to get the landscape the stamp will actually use under its current settings - the auto-resolved one when auto-target is on, or your TargetLandscape when it is off. Call it before a batch apply to log the binding so a misfire shows up in your output rather than as a surprise in the viewport. FindLandscapeBelow is the lower-level helper that does the geometric lookup of what sits beneath the actor; in a placement script you can call it to check a candidate position and, if it is wrong, set TargetLandscape explicitly before applying. Both are BlueprintCallable, so the whole decision can be made and audited in code.

The principle holds whether you work by hand or by script: let auto-target handle the simple cases, and the moment landscapes overlap, resolve and pin the binding explicitly. Next, open the included demo map to see stamps placed across terrain, then try the override on a level of your own where two landscapes share footprint - place a stamp, confirm with ResolveTargetLandscape which one it bound to, and switch to an explicit TargetLandscape if it guessed wrong.

How a stamp resolves its landscape

The binding depends on the bAutoTargetLandscape flag and on whether your landscapes overlap in plan view.

FAQ