Known Issues and Limitations

2.0+

Subsequent Windows users on the same machine are not supported with concurrent user licensing.

No workaround. Intended function.

2.0+

Resizing windows can cause an Aura crash.

No current workaround. Avoid resizing Aura windows.

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.5.1+

When using Freefly Astro or Astro Max, enabling the FPV feed via Commander settings while Auterion is running may cause the FPV feed to stutter. 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.

Manually enable the FPV feed in Commander settings when Auterion is closed.

1.2+

When offloading a scan via WiFi 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.

2.2

During authentication, Commander may be terminated by the operating system if a password manager launches as a separate application. This occurs because Auth0 authentication opens the default browser, placing Commander in the background where it may be killed to free system resources.

Use a password manager that operates within the system keyboard, or enter credentials manually during login.

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.

Cancel the RTH action and land 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.

Aura 1.10.0

A known bug affects a small number of scans, sometimes causing distorted point clouds or increased processing times. This is more likely in scans with a high number of loop closures. In some cases, output may be unusable or processing times significantly increased.

Workaround: Reprocess the scan. The issue may not recur on subsequent attempts, and reprocessing often produces a usable result.

If processing times are unusually long or point cloud results are unexpected, raise a support ticket for assistance.

Aura 1.10.1

Cortex 4.1.1

If power is disconnected during an active scan, Hovermap may enter a scan loop failure state preventing scans from starting or stopping normally.

Symptoms:

• Scan fails to start.

• LiDAR does not rotate.

• Green LED flashes when attempting to start a scan.

• Small duplicate scan files appear (less than 5 KB each).

Resolution: Update to Cortex 4.1.2 or later.

After updating, additional small or empty scan files may still be present on the Hovermap or offloaded. These files were created during scan loop failure conditions and do not contain usable scan data, but may occupy storage space and clutter the scan list or offloaded data. Clean up these files using the method below.

Clean-up (recommended):

1. Transfer all scan files to a PC.

2. Sort files by size.

3. Keep larger scan files.

4. Delete small or empty files (less than 5 KB each).

Files can be managed using Commander; however, large numbers of duplicate files may make clean-up impractical within Commander.

Cortex 4.1.2