--- title: "Known Issues and Limitations" slug: "known-issues-and-limitations" updated: 2026-08-24T05:26:38Z published: 2026-08-24T05:26:38Z canonical: "knowledge.emesent.com/known-issues-and-limitations" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.emesent.com/articles/llms.txt > Use this file to discover all available pages before exploring further. # Known Issues and Limitations This page outlines the currently known issues and limitations affecting the latest versions of Aura, Commander, and Cortex. While regular updates aim to improve stability and functionality, some issues may still impact specific workflows or hardware configurations. Review the information below and apply recommended workarounds where available. To report a problem not listed here, contact the [Client Support team](https://emesent.com/customer-support/). ## Aura | Affected versions | Issue | Workaround | | --- | --- | --- | | 1.8+ | Scans exported as **E57** cannot be reprocessed through the **merge** or **colorization** steps in Aura. | Export scans as **LAZ** first, complete all colorization and merge processes, then **Save As E57**. | | 1.0+ | Scans processed using **Drone RTK** do not generate an RTK accuracy report. | This is a known limitation. No workaround is currently available. | | 1.0+ | Aura does not support merging data georeferenced with **GCP** or **Drone RTK**. | Set georeferencing to **None** during merge. Georeferencing is not retained in the output. Complete merging and colorization in **LAZ**, then export as **E57** as the final step. | | 1.0+ | Aura cannot load or save individual point clouds that exceed 2.1 billion points. | Split the dataset into smaller sections using Aura's **Point Cloud Selection** tools before saving or reloading. Alternatively, process scans in parts and merge after reducing size. | | 1.0+ | Emesent scanners require external offload storage formatted as **exFAT**, which treats uppercase and lowercase letters as identical. Offloading multiple scans with names that differ only in case (for example, `scan_01` and `Scan_01`) merges them into a single folder, causing the dataset to not process correctly in Aura. | Use a unique name for each dataset, and do not rely on letter case alone to tell two datasets apart. Before offloading from a scanner, check the destination drive for an existing folder whose name matches the new dataset except for case, and rename one of them if found. Alternatively, offload to an empty folder or a different drive. | | 1.0+ | Aura cannot access a dataset when its full folder path exceeds the maximum path length supported by Windows (260 characters by default). Datasets stored across several levels of nested folders, or in folders with long names, are the most likely to exceed the limit. Aura reports an error and the dataset does not load or process. | Shorten the path by moving the dataset closer to the root of the drive (for example, `D:\Scans\`), reducing the number of nested folders, or shortening long folder names. Avoid storing datasets in deeply nested locations such as user profile or cloud-sync folders. | | 2.0+ | Closing the initial instance of Aura while processing jobs across other Aura instances can cause a processing failure. | Keep all instances of Aura open when processing data across multiple instances. | | 2.0+ | The machine going to sleep can cause a processing failure. | Configure the machine not to go to sleep when processing data. | | 2.2 | After moving the folder that holds the GX1 scan files, colorization may fail and report that scan metadata cannot be found. | When Aura prompts for the source video files during colorization, browse to the folder where the original `.mp4` videos are stored. | | 2.2 | Automatic people masking finds most people within around 4 meters of the scanner when they are facing the camera. People who are further away, turned away, or whose faces are not clearly visible are more likely to be missed. | Where complete masking is needed (for example, in published deliverables), review the scan and apply manual masking to anyone the automatic pass missed. | | 2.2 | Taking a screenshot from a scan in Aura 2.2 takes longer than in Aura 2.1. Screenshots still produce correctly. | No action needed. Further screenshot performance improvements are planned for a future release. | | 2.0+ | A license seat cannot be checked out, and Aura reports an error similar to: `Failed to repair license: Error: Error updating license: The customized vendor library (haspvlib.vendorID.*) cannot be located` This occurs when the Sentinel licensing runtime used by Aura does not install correctly. Other applications that use Sentinel licensing, such as **FARO License Manager**, can prevent the runtime from installing if they are installed or running on the same machine. An error may also have appeared during the Aura installation. | Reinstall Aura in the following order: 1. Uninstall Aura. 2. Uninstall the other application that uses Sentinel licensing. 3. Install Aura. 4. Reinstall the other application. Close **FARO License Manager** before installing Aura. If it does not close normally, end the process in **Task Manager**. If the error persists after reinstalling, contact [**Client Support**.](https://www.emesent.com/client-support/) | | 2.0+ | **Orthographic** view is not suitable for taking measurements. Point, line, and angle measurements made while in orthographic mode may not be accurate. | Switch to **Perspective** view before taking any measurements. | ## Commander | Affected versions | Issue | Workaround | | --- | --- | --- | | 1.5.1+ | When using **Freefly Astro** or **Astro Max**, if the **FPV feed** is enabled in Commander settings while **Auterion** is running, the FPV feed might stutter. For that reason, when Commander detects a Freefly Astro or Astro Max, the FPV feed is hidden by default and the point cloud is displayed in the Main View. | The **FPV feed** can be manually enabled in **Commander settings** when **Auterion** is closed. | | 1.2+ | Transferring scans via **Wi-Fi** using the **Commander Web UI** is currently not supported. | If Wi-Fi transfer is required, connect to the device's **Web UI** by entering **hover.map** in a web browser while connected to the device's Wi-Fi. Alternatively, transfer scans via USB. | | 1.2+ | When offloading a scan via Wi-Fi on **Hovermap**, the scan does not appear in the Downloads folder or any expected location. | Access `hover.map` using a browser (for example, **Chrome**) on the same device and download the scan directly from there. | ## Cortex | Affected versions | Issue | Workaround | | --- | --- | --- | | 3.2.1+ | Changes to the performance of the **Return to Home (RTH)** function in Cortex may result in Hovermap not taking the most direct route home, causing the failsafe to trigger earlier than expected. This issue occurs predominantly in open spaces. | Mitigate this issue by cancelling the RTH action and landing the aircraft manually when appropriate. | | 4.1.0+ | After shutdown via long-press of the power button, the heatsink fan may continue running briefly or restart momentarily before fully powering down. This behavior does not impact system functionality or operational capability. **Observable symptoms** - Fan continues running for up to 30 to 60 seconds after long-press power-off. - Fan may briefly power off, then restart momentarily before final shutdown. | Contact **Client Support** so occurrences can be tracked and appropriate guidance provided. If immediate fan shutdown is required: 1. Ensure the scan is complete and the unit has returned to the blue breathing LED state. 2. Physically disconnect the battery, or 3. Unplug the Fischer power cable from the Hovermap. |