Troubleshooting

The build says an input is missing

Build Map requires Height and Material. Trace both wires to valid outputs. A node farther upstream may itself have a missing required input.

The preview is blank or uniform

Preview the upstream node, check that numeric ranges are not collapsed, and use Autolevel temporarily. Verify a mask is painted and that Clamp, Threshold, or Range bounds are not excluding the whole field.

The terrain is too steep or too flat

Heightfields are normalized. Change Maximum height relative to Width/Depth, or use Adjust, Curve Remap, Math, and Autolevel. Degree-based Slope updates when physical proportions change.

Materials are missing or abrupt

Confirm a Material output reaches Build Map. Inspect band ordering and range bounds. Increase softness, break-up, or dither where supported. Materials remain discrete even with softened boundaries.

Stored Heightmap reports missing data

The referenced ServerStorage.AtlasStudioHeightmaps/<sourceName> entry is absent or invalid. Restore that folder from the source place or backup. The graph JSON does not contain its binary samples.

An imported map does not appear

Confirm the project GUID folder is directly beneath ServerStorage.AtlasStudioProjects, then restart Studio or reload the plugin. Do not insert it beneath Index or inside another project.

Studio slows down

Lower preview resolution, temporarily bypass expensive erosion/analysis chains, and use smaller test bounds. Final build density is unaffected by preview resolution.

Undo behaves unexpectedly

Complete the active drag or paint stroke before undoing. Switching maps replaces the document and clears graph history. Avoid manually editing Atlas storage while the plugin is open.