10.4 Error Message Reference

SLAM optimization failed (insufficient effective points)

Cause

The SLAM solver could not converge on a stable trajectory. Caused by long featureless paths, insufficient loop closures, or high walking speed in repetitive geometry.

Resolution

• Switch the Mode dropdown from Standard to Robust and reprocess. The Mode dropdown is on the Project Settings panel of the Project Processing dialog. This is the first and correct response to this error.
• If Robust succeeds, review the trajectory in the preview and verify output quality before delivery.
• If Robust also fails, review the processing report, which identifies the location and likely cause of the drift.
• If processing still fails, the data from the drifted portion cannot be recovered and the area must be rescanned.

Trajectory drift detected

Cause

SLAM optimization completed, but the solver detected accumulated drift exceeding the acceptable threshold across the trajectory.

Resolution

• Reprocess with the Mode dropdown set to Robust. This resolves many drift cases outright.
• Review the processing report to identify where the drift began. That location tells you what to change in field technique, and whether the clean portion covers what the deliverable actually needs.
• If the drifted segment contains critical coverage, the area must be rescanned. There is no processing workaround for a fundamentally broken trajectory.
• Escalate Before committing to a return visit, send us the processing report and poses.csv from the project folder. Salvaging part of a trajectory may be possible depending on the release, and it is worth one exchange to check.

RTK data invalid or unusable

Cause

The RTK track recorded with the scan does not meet validation criteria. Common causes are insufficient satellite count, Float status at scan start, excessive antenna tilt, and RTK loss during overlap zones.

Resolution

• Confirm LixelGO showed more than 10 satellites and a Fixed status before the scan began.
• After achieving Fixed, walk at least 33 ft (10 m) before beginning the scan route. RTK data captured during the initial fix period is often insufficient for processing.
• Confirm the antenna stayed within 20 degrees of vertical throughout. Exceeding this invalidates the fix record even when the LED appeared green.
• Confirm no continuous unfixed section exceeded 328 ft (100 m) on the L2 Pro. XGRIDS publishes no separate K2 figure.
• If field conditions were correct and the error persists, process as pure SLAM and apply GCPs in post-processing as a recovery path.

HBC file parse failed

Cause

The project file from the device cannot be parsed. The two confirmed causes are an incomplete data transfer and a mismatch between device firmware and the LixelStudio release.

Resolution

• Verify the copy is complete. Use a hash-verification tool to confirm source and destination files are identical before processing.
• Never power off the scanner immediately after stopping a recording. Wait for the save to complete. Powering off during save corrupts the file and the data is not recoverable.
• Confirm LixelStudio and the device firmware are from matching lineages. Running an older LixelStudio release against newer firmware produces parse failures.
• Escalate If the file is confirmed corrupt and no backup exists, the scan must be repeated. Get in touch if the corruption looks like a firmware issue rather than a transfer issue, since that is worth reporting upstream.

Activation code already used or invalid

Cause

The code entered has already been consumed or cannot be verified by the activation server. Each device serial number is entitled to a fixed number of permanent activation codes.

Resolution

• Confirm the computer is online and the system clock is synchronized. Force a Windows time sync if in doubt.
• Verify the code has not already been used. Each serial number is entitled to 3 permanent activation codes, and used codes cannot be reactivated.
• Escalate Do not enter a second code. If the code is confirmed unused and the error persists after fixing connectivity and time sync, contact us. A second code will not resolve the underlying issue and consumes an entitlement permanently.

OpenGL initialization failed

Cause

LixelStudio could not initialize the OpenGL graphics context. Caused by missing or outdated runtime libraries, incompatible GPU drivers, or Windows security settings blocking initialization.

Resolution

• Update the Visual C++ Redistributable libraries from Microsoft.
• Update the NVIDIA graphics driver. LixelStudio does not support AMD graphics cards. If the workstation uses AMD, that is the root cause and there is no workaround.
• Open the LixelStudio installation directory and run contextinfo.exe to verify the OpenGL version is 4.0 or higher. Below 4.0, the GPU or driver does not meet the minimum.
• If those three do not resolve it, disable Core Isolation in Windows Security (virtualization-based security) and relaunch.

Out of memory or filter crashed

Cause

Processing exceeded available system memory or workspace disk capacity. May appear as a filter crash, an out-of-memory error, or a silent processing termination.

Resolution

• Check the memory figure first. XGRIDS publishes 64 GB at both configuration tiers, Minimum and Recommended alike. A 32 GB workstation is below specification regardless of how strong the CPU and GPU are, and this error is the usual way that shows up.
• Close all other applications before processing. Memory spikes are not always visible in the foreground.
• Do not save or process from the C: drive. Use a dedicated high-speed SSD on a separate drive letter.
• Verify the target drive has enough free space for intermediate files. A near-full drive causes filter crashes that look like memory failures.
• Match scan length to available memory. Reconstruction memory climbs at roughly 2 GB per minute of scan, which puts about 30 minutes at the practical ceiling on 64 GB and about 60 minutes on 128 GB. Longer captures should be split and rejoined with Map Fusion rather than run as one scene.

Installation failed or application will not launch

Cause

The installer was blocked or quarantined by real-time antivirus protection, or the installation did not complete.

Resolution

• Temporarily disable real-time antivirus protection, then reinstall or repair the installation.
• Add the LCC Studio installation directory to the antivirus exclusion list before re-enabling protection.
• Verify the installation by running a test reconstruction on a known-good dataset.

Project file corrupted or incomplete

Cause

The project file was not fully copied or downloaded before LCC Studio tried to open it. Cloud-storage downloads that appear complete but are still streaming cause this silently.

Resolution

• Verify the project was fully downloaded or copied before opening. Use hash verification to confirm completeness.
• If copying from cloud storage, confirm the download finished before LCC Studio accessed the files. Partial downloads produce this error with no warning.
• If the source data is intact, recopy the full project folder and reprocess.

Reconstruction interrupted, project shows failure status

Cause

LCC Studio was closed, or the machine slept or restarted, while a model was generating. Interrupted projects display a failure status when the application reopens.

Resolution

• Click Continue or Restart to re-queue the job.
• Expect to lose the progress. Closing the application does not save processing progress, and the SLAM phase restarts from the beginning. A long reconstruction closed near the end starts over.
• Reserve free disk space of at least twice the captured project data size before restarting. A run that exhausts the workspace mid-job fails the same way.
• Set Windows Power and Sleep to Never before any long reconstruction.

Reconstruction failed mid-process

Cause

A confirmed cause on Intel 13th and 14th generation desktop CPUs is the published instability advisory. Intel released BIOS microcode updates to address it, and workstations without the update produce inconsistent reconstruction failures under sustained load.

Resolution

• Identify the CPU model and check whether it falls under Intel's advisory for 13th and 14th generation desktop instability.
• If affected and no BIOS update has been applied, have a qualified technician update the system BIOS before attempting further processing.
• After the BIOS update, rerun reconstruction on the same dataset to confirm the issue is resolved.
• Escalate If reconstruction continues to fail after addressing the CPU, submit logs through the in-software feedback tool and contact us.

Login or authentication failed

Cause

The application could not reach XGRIDS authentication servers. Most commonly a corporate firewall blocking outbound traffic, or a VPN routing traffic in a way that breaks the handshake.

Resolution

• Ask your network administrator to allow all https://*.xgrids.com domains outbound on port 443.
• If wildcard rules are not permitted, the minimum required domain is https://api-gw.xgrids.com on port 443.
• To distinguish a firewall problem from a backend outage, try logging in through a browser at https://developer.xgrids.com/#/login. If that also fails, the issue may be temporary and on the XGRIDS side.
• If no corporate firewall is in use, check for an active VPN. VPN routing can block the authentication handshake.

GPU not detected

Cause

LCC Studio could not identify a CUDA-capable NVIDIA GPU. The driver may not be installed, two discrete GPUs may be confusing auto-selection, or the GPU is not supported.

Resolution

• Confirm the GPU is NVIDIA. Open Command Prompt and run nvidia-smi. If it returns driver and GPU information, the driver is installed correctly. If it fails, the driver needs reinstalling.
• If the system has two discrete GPUs, disable the secondary in Device Manager. LCC Studio does not support multi-GPU operation and may fail to select the correct one automatically.
• An integrated GPU (Intel HD, UHD, or Iris Xe) does not need disabling. LCC Studio assigns processing to the NVIDIA GPU automatically when an integrated GPU is also present.
• If nvidia-smi fails, have an IT professional reinstall the NVIDIA driver cleanly. NVIDIA recommends removing the existing driver with DDU first.

System crash or blue screen during reconstruction

Cause

Workstation hardware failed under reconstruction load. Causes can be thermal, memory, or driver-related.

Resolution

• Check Windows Event Viewer for the blue screen error code at the timestamp of the failure. The code identifies whether the cause is thermal, memory, or driver.
• Monitor GPU and CPU temperatures during reconstruction. If they exceed thermal limits, improve case airflow or clean cooling components.
• Close all other applications before running reconstruction to reduce competing load.
• Escalate If the error persists on a well-cooled system, have an IT professional evaluate the hardware. Contact us if it looks software-related rather than hardware.

Region restricted (error 316aa)

Cause

The device's region of purchase does not match the region of attempted use, or the app's regional version does not match the device. XGRIDS enforces region-specific activation.

Resolution

• Escalate If the device was purchased in mainland China and is being used internationally, or the reverse, the restriction requires resolution through the XGRIDS regional sales manager. Contact us to start that process and do not attempt further activation steps until it is lifted.
• If the device region matches its location, confirm you are running the correct regional version of the app. A mainland China device paired with the international build is a mismatch.
• After the restriction is resolved, install the correct regional app, sign in with the original activation account, and reconnect.
• If a VPN is active on the phone, disable it and retry. The app reads the apparent location mismatch and blocks activation.

On the PortalCam, a related but separate setting is Device Region in app settings, which resolves connection failures after the device has moved between regions. That is a connectivity fix, not an activation one. See 7.5 Connection Troubleshooting.

LIO drift warning (active scan)

Cause

The SLAM solver detected accumulated drift during the active scan and is warning that data quality is degrading in real time.

Resolution

• Stop the segment. Note where you were when the warning appeared, since that location is what needs rescanning.
• Process the segment with the Mode dropdown set to Robust.
• Review the processing report to confirm how much of the trajectory is usable before deciding whether the area needs recapture.
• Before rescanning, address the cause: slower walking speed, more frequent loop closures, or control points in featureless zones.

Account binding conflict

Cause

The app account is no longer recognized as the device's bound activation account, or the session has expired.

Resolution

• Sign out and sign back in. An expired session is the most common cause and resolves immediately.
• If the device recently had a 316aa restriction resolved, sign in with the original account that first activated it. A different account will not be recognized.
• Escalate Device binding cannot be cleared by the user. Clearing a binding also clears the activation and warranty record, and that cannot be undone. Contact us before pursuing this route so we can confirm it is genuinely necessary.