8.1 Understanding the LixelStudio Pipeline
How LixelStudio converts K1 and L2 Pro raw scan data into a georeferenced, colored point cloud through SLAM optimization, coordinate transformation, and color mapping.
What LixelStudio Does
LixelStudio is the point cloud processing software for the K1 and L2 Pro. It takes raw scan data from the device and converts it into a usable, navigable point cloud through a sequence of automated stages. PortalCam data is not processed in LixelStudio. That device uses LCC Studio exclusively.
The output is a georeferenced, optionally colored, three-dimensional point cloud that can be exported into BIM, GIS, and survey workflows. There is no conversion path between LixelStudio output and LCC Studio output. If you need both a point cloud and a 3D Gaussian Splatting model from the same scan, both pipelines must be run separately from the original raw data. Do not run LCC Studio and LixelStudio processing jobs simultaneously on the same machine. Each application consumes significant GPU, RAM, and disk I/O. Process one pipeline to completion before starting the other, or use two separate workstations.
LixelStudio processes K1 and L2 Pro raw data only. If you are working with PortalCam data, close this section and go to Module 9: LCC Studio Processing.
Pipeline Stages
Stage 1: SLAM Optimization
LixelStudio reconstructs the device trajectory and point map from the raw LiDAR and IMU data recorded during the scan. This is the computationally intensive phase that determines the overall accuracy and completeness of the result. The entire scan trajectory is held in RAM during this stage, which is why RAM capacity directly limits the maximum scan duration that can be processed.
SLAM optimization runs with no special mode by default (None mode), which provides the highest accuracy in stable environments with rich features. If processing fails in None mode, particularly with an "LIO trajectory drift" error, enable Robust Mode from Advanced Settings before concluding the data is unrecoverable. Robust Mode improves success rate in partially degraded or high-motion scenes but may reduce accuracy. Narrow Scene Mode is reserved for tunnels, mine shafts, and long corridors, and using it in a standard environment produces a processing failure.
Stage 2: Point Cloud Generation
Once the trajectory is established, LixelStudio generates the dense point cloud from the LiDAR range data along the reconstructed path. Point density settings configured before processing determine the resolution of the output. Higher density produces larger files and requires more processing time.
Stage 3: Coordinate Transformation
If RTK, PPK, or GCP data was collected during the scan, this stage applies that data to place the point cloud in a real-world coordinate system. Without georeferencing, the output exists in an arbitrary local coordinate frame. This stage is automated when valid positioning data is present and correctly imported.
Stage 4: Color Mapping
If camera data is available, LixelStudio maps color from the camera images onto the point cloud geometry. For external Insta360 cameras, the video must be in timelapse format with a minimum duration of 3 minutes. Color mapping requires LixelStudio v2.5.2.1 or later, CUDA 11.6 or later, and an NVIDIA GPU from the 20-series or newer. 10-series and older GPUs cause a coloring crash.
Set Windows Power and Sleep to Never before any processing run. Go to Windows Settings > System > Power & Sleep and set both Screen and Sleep to Never. A single sleep or hibernate event during SLAM optimization corrupts the project file and requires restarting from import.
Workstation Requirements
Save project files to a non-system drive (D: or similar). The LixelStudio installer defaults to the C: drive, and the software itself can run from C: without issues. However, saving project files to C: can cause disk space bottlenecks during processing because Windows system files compete for space on the same drive. The Dealer Troubleshooting Guide also notes that C: drive project locations may lead to memory bottlenecks or file access conflicts.
Processing Time
LixelStudio processing runs at approximately 20 to 30 times the scan duration on recommended hardware. This ratio applies to SLAM optimization on an NVMe SSD workstation. Color mapping adds additional time on top of the point cloud processing. Both the GPU and CPU are utilized during processing.
LixelStudio displays an estimated processing time in a popup window when you start a job. Use this estimate for scheduling. The actual duration varies with scan complexity, environment geometry, and workstation performance, but the estimate provides a reasonable planning baseline.
Plan for overnight runs on projects above 20 minutes. A 30-minute scan on a 128 GB workstation with NVMe SSD will take 10 to 15 hours. Do not schedule processing that requires the machine for other work during the run. Do not run LCC Studio processing simultaneously on the same machine.
Software and Firmware Compatibility
Using the wrong version of LixelStudio produces processing failures that are not always obvious. Verify the correct version before starting any project.
LixelStudio Version Requirements
Firmware-to-Software Compatibility
LixelStudio version must match the device firmware. Mismatches produce processing failures that may not include a clear error message. After any firmware update, verify LixelStudio compatibility before processing new data.
If processing fails after a firmware update, the most likely cause is a LixelStudio version mismatch. Update LixelStudio to match the firmware tier above before re-attempting. This resolves the majority of post-update processing failures.
Common Misconceptions
These are the misunderstandings that cause the most wasted time in the field and in processing. Each one is based on reasonable assumptions that happen to be wrong for this system.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer

