DJI Terra Reconstruction Errors: Troubleshooting Guide

This practical guide covers DJI Terra reconstruction errors, insufficient VRAM, insufficient memory, missing images, file problems and inaccurate outputs. It combines references to DJI documentation with an original diagnostic workflow you can follow on your own workstation.

Prepared by the Drone Emotions team. Official documentation checked on 7 October 2026. Error wording, reporting tools and processing requirements can differ between releases; follow the instructions for your installed version and sensor.

What to check first when DJI Terra reconstruction fails

Before restarting, create a short record of the failure. This helps distinguish a reproducible issue from an interruption and makes any later support request more useful.

• Processing stage: importing, aerotriangulation, reconstruction, point cloud processing or export.
• Failure details: exact message, code if shown, time and whether it repeats.
• Environment: Terra version, license edition, GPU and driver, RAM and storage locations.
• Dataset: sensor, image count or LiDAR folders, collection date and selected outputs.

The table below is a starting point, not a diagnosis. Its symptom descriptions are summaries; use the actual message and the current DJI reconstruction exception guide to interpret a specific code.

DJI Terra insufficient VRAM: check GPU memory

VRAM is the graphics card’s memory; RAM is the computer’s system memory. Adding system RAM does not increase the GPU’s dedicated VRAM.

DJI’s dedicated VRAM troubleshooting article recommends checking the graphics card, updating its driver, restarting Terra or Windows and testing a new mission with fewer photographs. It cites at least 4 GB VRAM, while recommending more capacity because other applications can consume some of it. This threshold is not a guarantee for every reconstruction workload.

1. Record the GPU model and dedicated memory capacity.
2. Close unnecessary applications using the GPU before retrying.
3. Check that Terra uses the supported NVIDIA GPU, particularly on a laptop with integrated graphics.
4. Follow DJI’s driver guidance for your release and restart when required.
5. Use a smaller, overlapping dataset to see whether the failure follows workload size.

A “GPU not detected” issue deserves a driver and device check before a memory upgrade. See DJI’s insufficient VRAM guidance and our system requirements and workstation guide.

DJI Terra insufficient memory: examine available RAM

The installed RAM figure is only part of the picture. Check how much memory is available while the failing stage runs, including memory used by other applications.

Record resource usage in Windows Task Manager. Compare a failed large mission with a smaller test using the same processing settings. If the smaller mission succeeds and the larger one exhausts memory, capacity becomes a reasonable explanation to investigate.

A diagnostic subset should contain adjacent images with usable overlap. Randomly removing photographs can create a matching problem that hides the original resource issue.

Do not assume that limiting the output area reduces every earlier processing stage. Assess the workload at the stage that actually fails. Avoid treating an image-count-per-GB estimate as a universal guarantee: resolution, task and release also matter.

DJI lists memory shortage among the possible causes of missing calibrated images in its aerotriangulation troubleshooting article. Confirm the cause before purchasing additional hardware.

Disk, cache and file access errors

Check the drives used for source data, project storage, cache and final exports. A large output drive does not help if another required location is full or inaccessible.

• Space: inspect free space during processing, allowing for intermediate files.
• Paths: confirm that the original files have not been moved or renamed since import.
• Access: check that your Windows account can read inputs and write to project locations.
• Connections: check removable drives and network locations for interruptions.

As a diagnostic test, use a complete local copy and a short project path in a location you can write to. Keep the original mission intact. If the local test succeeds, investigate what differs in the original storage arrangement.

For cluster processing, include shared storage and worker storage in the investigation. Follow DJI’s release-specific recovery instructions before removing project cache; preserve source data and project records.

Aerotriangulation fails or some photographs are missing

Aerotriangulation estimates camera relationships from shared image features. Inspect full-resolution photographs rather than relying only on thumbnails or the apparent completeness of the flight route.

Look for blur, extreme exposure, missing files, weak texture and inadequate overlap around the area that fails. Repeated patterns, moving objects and reflections can make matching difficult. A nominal overlap setting does not establish that buildings and changing terrain were captured adequately.

Compare imported and calibrated image counts in the report, then locate excluded images spatially. A gap concentrated around one feature suggests a different investigation from a failure spread across the entire mission.

Check any imported camera parameters and positioning data as well. Avoid inventing camera values to force alignment. Our DJI Terra quality report guide helps interpret the processing evidence.

If missing coverage is the cause, higher reconstruction quality cannot create observations that were never captured. Use a controlled test to determine whether supplementary acquisition is needed.

Reconstruction completes, but coordinates or elevations are wrong

A completed mission can still produce an unsuitable deliverable. Treat a systematic horizontal shift, an elevation offset and a locally distorted model as different symptoms.

Check the coordinate systems assigned to image positioning, GCPs and outputs. Verify units, coordinate order, elevation reference and point marking. DJI identifies inconsistent control and positioning information as a possible cause of output errors.

Record the survey reference explicitly, including whether heights are ellipsoidal or tied to a specified vertical datum. Use independently checked points to evaluate the result rather than assuming that a plausible visual model is accurate.

Do not change accuracy weights or positioning constraints at random. DJI describes specific cases involving inconsistent elevation systems; apply that guidance only after identifying how your own data were referenced.

Read our accuracy, GCP and RTK guide together with DJI’s output accuracy troubleshooting guidance.

If an orthomosaic or mesh has holes, also inspect acquisition coverage and scene texture. DJI’s reconstruction anomaly FAQ discusses missing regions and display differences in third-party software. Compare the output in Terra and the receiving application before deciding it is a reconstruction failure.

DJI Terra LiDAR processing errors

LiDAR processing requires the appropriate acquisition files, not simply the photographs recorded during the flight. Preserve the complete original folder structure and check your sensor’s documentation.

DJI’s LiDAR error guidance distinguishes missing files, read/write problems and acquisition timing issues. For example, its documented code 8109 concerns a mismatch between base-station and aircraft recording periods; the base-station data need to cover the flight.

Do not substitute an unrelated recording or combine files from separate missions to silence a warning. Compare the copied folders with the originals and establish whether the required data were actually collected.

Calibration procedures differ between sensors. Instructions written specifically for Zenmuse L1 should not be applied automatically to L2 or L3. Consult the relevant payload manual and the official DJI LiDAR processing error guidance. Our supported drones and sensors guide provides additional context.

For a Zenmuse L2 project, review the end-to-end steps in our DJI Terra and Zenmuse L2 workflow guide before isolating the failed processing stage.

Is reconstruction slow, or has it stopped?

Elapsed time alone does not establish failure. Record the processing stage, changes in logs and resource activity. Different stages can use the workstation differently, so a low reading for one component is not conclusive.

DJI’s slow reconstruction guidance discusses CPU, GPU, storage and image workload. It also cautions against assuming that larger hardware specifications always deliver proportionate improvements.

Use a controlled test

1. Keep the failing mission and its settings as your reference.
2. Create a separate mission using a connected subset of the original data.
3. Keep the processing settings comparable.
4. Change one factor, such as storage location or workload size.
5. Record the outcome and resource usage before making another change.

A smaller successful mission narrows the investigation; it does not prove the entire source dataset is sound. Check the full deliverable again after any corrective action.

Before changing Terra versions, consult our versions and release notes guide. Obtain installers from the download page and preserve project backups when testing an update.

Export logs and prepare a useful support request

DJI documents mission log export and the shortcut Ctrl + Alt + L for opening the log folder. The documented Windows location is:

C:\Users\<username>\AppData\Roaming\DJI Terra\log

Use the reporting method available in your release and retain logs covering the failed mission’s time. Check the current exception and reporting guide for the appropriate workflow.

Include these details when contacting support:

• Exact error message, code and time of failure.
• Terra version and license edition.
• Windows version, CPU, RAM, GPU, VRAM and driver version.
• Sensor, dataset size, storage locations and processing settings.
• Steps that reproduce the issue and the results of controlled tests.
• Relevant logs and a screenshot of the message.

For project data, agree an appropriate private transfer method with the support team. Do not post activation codes or client datasets in public comments.

DJI Terra reconstruction troubleshooting FAQ

Why does DJI Terra reconstruction fail?

The failure can involve hardware resources, file access, input quality, positioning information or authorization. The exact message and failing stage help determine which checks are relevant.

Will adding RAM fix insufficient VRAM?

System RAM and dedicated GPU memory are different resources. Investigate graphics memory usage and GPU requirements when the message specifically identifies VRAM.

Should I reinstall Terra immediately?

First preserve the error information and check the indicated cause. Reinstallation does not establish whether source files, available resources or coordinate settings caused the failure. Follow DJI’s recovery instructions when they apply.

Why are some images excluded from aerotriangulation?

Inspect memory usage, overlap, image quality and scene characteristics. Compare imported and calibrated image counts, then examine where the excluded photographs occur.

Does a completed reconstruction guarantee survey accuracy?

Completion shows that processing finished. Validate coordinates, elevations, coverage and independent checkpoints against the project’s acceptance requirements.

Could the error be related to my license?

If the message concerns authorization, check the required feature, license validity and activation status. Use our license guide and installation and activation guide before purchasing a replacement.

Owners of an older Pro license can also consult our DJI Terra Pro and current editions guide to interpret legacy naming.

When should I contact support?

Contact support when a failure repeats after the relevant documented checks, required files appear missing, or you cannot reconcile the output with validated survey data. Provide evidence and test results so the investigation can start efficiently.

Official DJI references

• Reconstruction exception and reporting guide.
• Insufficient VRAM troubleshooting.
• Missing images in aerotriangulation.
• LiDAR processing error guidance.
• DJI Terra downloads, manuals and release documentation.

This independent guide is published by Drone Emotions, the business behind djiterrasoftware.com. It provides a diagnostic starting point; a specific failure may require analysis by DJI support.