# Troubleshooting

<details>

<summary>Task waiting</summary>

#### 1. Check whether the engine is started.&#x20;

* If the engine is not started, the status will show **None**. Click **Start Local Engine** to start it.

<figure><img src="/files/9TRimVKfxu2hApi2Ith2" alt=""><figcaption></figcaption></figure>

#### 2. Check whether the **Job Queue Directory** for project and for engine are consistent.

* If the engine is already started, and paths are inconsistent, the status will show **Inconsistent Path.** This means the **Job Queue Directory** for project and for engine do not match.&#x20;

<figure><img src="/files/1TMFg3Z8hDM68mQENXRK" alt=""><figcaption></figcaption></figure>

<div><figure><img src="/files/HA2VfUDVxtUeeg3gWTLx" alt=""><figcaption></figcaption></figure> <figure><img src="/files/zqtP7r1qrXGz4fTr7Lm1" alt=""><figcaption></figcaption></figure></div>

* Change the engine path to match the job queue path for project. You can do this in **Settings** and apply the changes.

<figure><img src="/files/AgFwbt3qLyUjVS0FvfFR" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/i3Ft0GsWugRtp8877Hnw" alt="" width="563"><figcaption></figcaption></figure>

* Or right-click the engine in the engine panel and modify job queue directory for engine.

<figure><img src="/files/83nYJAOxAdcG8XLpUNl5" alt=""><figcaption></figcaption></figure>

#### 3. Check if there's Engine Capability.

* If there is no **Engine Capability** shown in the engine panel, right-click and **Set Engine Capability** and select **Get3D Mapper**.

<figure><img src="/files/44VoBZBFqeVCgDNCGdAT" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/4vmeXQUaNpRdCKTmvH5d" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>Engine path doesn't exist</summary>

1. Check whether **Get3D Engine** is installed. If not, please reinstall **Get3D Mapper**.
2. If **Get3D Engine** is already installed, locate the installation path and manually launch the engine executable.

</details>

<details>

<summary>AT failed</summary>

1. Ensure that an NVIDIA GPU is being used and check whether the CUDA version is higher than 12.5. If not, update the GPU driver to the latest version.
2. If the hardware environment is correct, check whether the data paths are valid. If a data path does not exist or the data is corrupted, this will be indicated in the error message. Corrupted data should be removed. If a path does not exist, use the **Modify Photo Directory** function to check and update the photo paths. Also check whether the paths contain special characters.\
   **Note:** In cluster mode, use IP-based network paths instead of character-based paths.
3. Check whether there is sufficient free space in the cache directory.
4. Check for insufficient CPU or GPU memory.
5. Verify that the camera parameters are correct.
6. Check whether the original pose metadata is correct. The original positions can be viewed in the block’s 3D view.
7. Adjust the AT settings. For different scenarios, refer to the **AT Instruction** for recommended configurations.

</details>

<details>

<summary>Less than 90% in net</summary>

1. If the non-meshed areas are entirely water surfaces, they can be ignored.
2. If the non-meshed areas are entirely vegetation, they can be ignored.
3. If the overlap between meshed and non-meshed areas is low, adjust the parameters by increasing feature density and lowering filtering strength.
4. If lighting conditions vary significantly during data acquisition, feature points may fail to match. Such data is not suitable for processing and should be re-acquired.

</details>

<details>

<summary>3D reconstruction failed</summary>

1. Check whether there are empty tiles.
2. Insufficient system memory or GPU memory.
3. Issues with photo paths or corrupted data, or insufficient disk/storage read permissions.
4. Insufficient cache space.
5. The process was terminated unexpectedly.
6. Delete intermediate files and resubmit the task.
7. The issue may be caused by network instability, resulting in missing intermediate files during processing. Resubmit the tiles.
8. Create a new reconstruction and try a different coordinate system.

</details>

<details>

<summary>Failed in cluster</summary>

1. In a cluster environment, if failures repeatedly occur on a specific node, you can disable the engine on that node and continue processing with the remaining nodes. Check whether the storage and compute nodes can all access each other’s data.
2. For failures in a cluster environment, verify that both storage and compute nodes can mutually read the data. You can also try placing the data and project on a local machine and running the task in standalone mode to see whether it completes successfully.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.get3d.ai/user-help-center/get3d-mapper/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.