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. Users are encouraged to review the information below and apply recommended workarounds where available. If you encounter any problems not listed here, please contact the Customer Support team.
Contents
Resolved Issues
Aura
Affected Versions |
Issue |
Workaround |
---|---|---|
1.9+ |
Manually added GCP targets (via the Add Target button) are not used in GCP registration. Only GCP targets automatically detected by Aura are currently used during the registration process. |
|
1.8+ |
Scans exported as E57 cannot be reprocessed through the merge or colorization steps in Aura. |
Export scans as LAZ first, complete all colourisation and merge processes, and then Save As E57. |
1.0+ |
Merging georeferenced or re-projected data Aura does not support merging scans that have been georeferenced or re-projected |
|
Commander
Affected Versions |
Issue |
Workaround |
---|---|---|
1.5.1+ |
When using Freefly Astro or Astro Max, if the FPV feed is enabled via Commander settings while Auterion is being run, 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. |
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. |
This issue can be mitigated by cancelling the RTH action and landing the aircraft manually when appropriate. |
Resolved Issues
This section lists issues that have been resolved in recent releases of Commander, Cortex, and Aura.
For issues resolved prior to Cortex 4.0 and Commander 2.1, please refer to the release notes for each respective product.
Issue |
Resolved in |
---|---|
Aura: 1.10.0 Issue A known bug affects a small number of scans, sometimes causing either distorted point clouds or increased processing times. It’s more likely to occur in scans with a high number of loop closures. In some cases, the output may be unusable, or the increased processing times may impact your workflow. Workaround Reprocess the scan: The issue may not recur on subsequent attempts, and reprocessing can often produce a better result. If you experience unusually long processing times or unexpected point cloud results in Aura 1.10, please raise a support ticket so we can assist. |
Aura 1.10.1 |