DOCUMENTATION · UPDATED 21 OCTOBER 2026

Troubleshooting

OpenTopography rejected the API key or dataset access

Check the key, provider account, chosen dataset entitlement and quota. Save the corrected connection and retry. Provider access is independent of your plugin license. Try another authorized elevation source to isolate the problem.

OSM coverage is incomplete

Generation can stop rather than silently omit requested mapped features. Retry Generate to reuse available cached elevation/imagery, try a smaller area, or retry when the provider recovers. If you intentionally want terrain only, disable mapped feature requirements and mapped land cover. This changes the requested output; it is not a repair to missing OSM data.

GIS import failed: feature limit exceeded

Reduce the area or adjust Max Vector Features under Features > Map data & regional downloads > Geographic datasets & road settings > OpenStreetMap. New settings use 50,000 supported features; older presets may retain 20,000. The adjustable limit is bounded at 200,000, with a separate raw-record ceiling. Increasing it increases memory/time and does not bypass every safety limit. Oversized imports are not silently truncated.

Automatic analysis failed

Expand the diagnostic message and inspect the project log. Verify that the complete matching plugin package, especially Tools and Resources, is installed. A missing analysis dependency, provider failure and invalid input require different fixes. Reinstall the complete package in a backed-up project if files are missing; do not copy a DLL alone.

Landscape exists but mapped features are absent

Confirm those features were enabled for that import and inspect the import report. Check whether data was available, filtered, outside bounds or excluded by budgets. A road visible in satellite imagery may have no corresponding OSM feature. Do not report a terrain-only result as a successful mapped-feature import.

Preview looks different from the level

The reduced Surface preview omits final-world features and does not capture the editor viewport. Check analysis freshness, selected landscape, paint-application setting and Apply Surface. Inspect full materials, satellite imagery and foliage in the actual level.

Roads float or deform badly

Check terrain spacing relative to road width, road terrain behaviour, mesh alignment and whether the road was rebuilt after terrain changes. Inspect bridges/tunnels separately. Increasing Nanite detail does not repair a coarse sculpting grid.

A water plane covers the land

Read the generated landscape's saved sea level. Align the plane to that level, or use the supported generated-region alignment operation after loading the affected region. Actor Z=0 and sea-level Z=0 are not interchangeable assumptions.

Expand selected does nothing

Confirm missing cells are selected, an existing generated region is targeted, required actors are loaded, and data sources can supply neighboring bounds. Local heightmaps need adjacent data. Expand the status message for provider or input errors.

Missing modules, white controls or stale UI

Verify the installed plugin version and matching engine build. Keep one plugin installation, close Unreal before updating, and install the complete package. Capture the affected control and log if the issue persists; do not delete project Content as a UI repair.

Collect a useful report

Include plugin version, exact Unreal build, OS, reproduction steps, area/coordinates if shareable, resolution, source/dataset, enabled features, expected versus actual result and the complete error text. Attach a relevant excerpt from Saved/Logs and the import report. Redact API keys, credentials and private project information.