10.10 LixelStudio Tools
A reference for every setting, mode, and tool in LixelStudio. Use this alongside Module 8 when processing point clouds from the L2 Pro or K1.
Project Processing Settings
The Project Processing dialog is the primary interface for converting raw scan data into a processed point cloud. It opens after importing raw data into a new project. All configuration decisions below must be set before clicking Start. They cannot be changed after processing begins.
Coordinate system defaults to CGCS2000. Confirm the coordinate system before clicking Start. Processing with the wrong coordinate system produces output that cannot be accurately transformed after the fact, requiring a full reprocessing run.
Core Settings
RTK Setting Panel
When the GNSS checkbox is enabled and RTK module is selected, clicking RTK Setting opens a panel showing the validity chart for the RTK data collected during the scan. This chart plots the RTK fix quality against the scan timeline, showing which portions of the scan had Fixed status and which had Float, Single, or no fix.
The RTK valid data count must be greater than 100 to achieve successful coordinate transformation in LixelStudio. If the valid count is below this threshold, process without RTK (uncheck GNSS) or provide GCPs to anchor absolute coordinates. Do not attempt to process with poor RTK data: the result will be a point cloud with incorrect or inconsistent absolute coordinates.
Coloring Options
LixelStudio supports two coloring sources. The correct choice depends on whether an external panoramic camera was used during the scan. Selecting the wrong option results in either no color or misaligned color on the point cloud.
External Camera Requirements
When using external camera coloring, the camera video files must be placed in the external_data subfolder of the project before processing. The external camera must have been started within 5 seconds of the scan start to maintain time synchronization. The recommended Insta360 ONE RS settings for external coloring are: normal video recording, 6K resolution, 24 Hz frame rate, automatic exposure, standard color profile.
Optimize visual point cloud is a third coloring option available when both internal and external camera data exist. It attempts to blend sources for improved quality. This option increases processing time and is not recommended for standard production workflows.
Special SLAM Modes
The Special Mode setting controls how the SLAM solver handles the scan data. The correct mode depends on the scanning environment and how the device was mounted. Using the wrong mode either reduces quality or causes the processing to fail outright.
None
Maximizes mapping accuracy. Assumes a stable device in a clear, feature-rich environment. Will fail if the scan contains intense motion, sensor interference, or poor scene features. Do not use as a first attempt on any scan where conditions were less than ideal.
Robust Mode Default
Balances accuracy and success rate. Handles most real-world environments including indoor spaces with some challenging areas. Recommended for the majority of users and projects. Use this as the starting point on any scan that produces an LIO Drift error with None mode.
Narrow Scene
Optimized for long, linear, feature-constrained environments such as tunnels, mine shafts, and extended corridors. Will fail in regular open-plan environments. Only applicable to tunnels or corridors exceeding approximately 1,600 ft (500 m) in length where standard modes produce unresolvable drift.
Vehicle-Mounted
Configured for scans captured from a moving vehicle where the scanner is fixed in place and the motion profile is continuous and smooth. Not for handheld use. Requires appropriate camera mount type selection in the Coloring section.
Drone
Configured for L2 Pro aerial scans on compatible DJI drone platforms (M350 RTK, M300 RTK). The RTK module must be removed for drone use. Aerial datasets typically show larger absolute errors than handheld projects. Field results suggest several centimeters RMSE compared to 3 cm handheld, but no published XGRIDS specification exists for aerial accuracy. Always validate aerial results against independent check points before using them for design work. Requires the Drone mount type in the Coloring section.
Advanced Processing Options
These settings appear in the Advanced Setting section of the Project Processing dialog. Most are disabled by default. Enable them only when the specific scenario described applies.
Coordinate Transformation
The coordinate transformation panel is accessed via the RTK Setting dialog when GNSS is enabled. It configures the source coordinate system (the system used by the RTK receiver during capture) and the target coordinate system (the delivered output coordinate system).
Default System
LixelStudio defaults to CGCS2000 (China Geodetic Coordinate System 2000) as both the source and target ellipsoid. For projects outside China or projects requiring delivery in a different coordinate system, the source and target must be reconfigured before processing.
Key Configuration Parameters
0 0 0 0 0 0 1 for an identity transform).Point Cloud Editing Tools
LixelStudio's viewer and editor provide tools for reviewing, cleaning, and measuring the processed point cloud before export. The following tools are available in LixelStudio v3.5.
Display and Navigation
Point Cloud Viewer
Orbit, pan, and zoom the processed point cloud in 3D. Render modes include standard color, intensity, and elevation (EL). Use the viewport scale display (added in LS 3.5) for on-screen dimensional reference.
LCC ViewerLS 3.5
Imports and displays LCC format 3DGS models (.lcc) directly within LixelStudio for side-by-side comparison with the point cloud. Enables overlay QC between the two pipeline outputs without switching applications.
Trajectory Display
Overlays the device scan trajectory on the point cloud. Useful for identifying where trajectory drift occurred and which portions of the point cloud may have accuracy issues.
Cloud Map Overlay / Floor SlicingLS 3.5
Slices the point cloud by floor elevation and displays each level as a 2D plan view overlay. Enables focused analysis of individual floors in multi-story projects and enhanced visualization of floor plan geometry.
Profile ViewLS 3.5
Creates a cross-section view through the point cloud from any angle, not just orthogonal. Useful for inspecting wall thickness, MEP routing, and structural geometry in section. Select a cut plane orientation, and the viewer shows only points within a defined slice thickness.
Bounding Box Display
Shows a bounding box around selected point cloud regions. Display logic updated in LS 3.5 to show only when points are selected, reducing visual clutter during general navigation.
Editing and Cleanup
Recommended cleanup sequence before export: Start with Clipping and Cropping to remove the largest unwanted volumes first (areas outside the site boundary, ceiling artifacts, scan start/end noise). Then use the Cloud Map Overlay floor slicing to isolate and inspect each level. Use freehand Clipping to remove irregular geometry boundaries. Run Noise Filtering after spatial cleanup is complete. Apply Resampling last, immediately before export, so it operates on the fully cleaned cloud rather than on intermediate editing states.
Clipping and Cropping
Select and remove point cloud regions using rectangular or freehand selection tools. Use to remove scan noise at scan start/end, remove the scanner operator from the data, crop the deliverable to the site boundary, or clean up ceiling artifacts.
Noise Filtering
Automated filter that identifies and removes statistical outliers from the point cloud. Comprehensive optimization in LS 3.5 significantly reduces noise while preserving edge detail. Run after the initial review of the processed cloud to reduce noise before export.
Plane DrawLS 3.5
Point cloud drawing tool supporting common CAD drawing operations directly on the point cloud viewport. Includes intelligent vector extraction to assist in tracing building geometry from the point cloud. Produces 2D vector linework from the 3D scan data.
Dynamic Object RemovalLS 3.5
Detects and removes dynamic objects (people, vehicles) from vehicle-mounted scan scenarios in post-processing. Available as both a processing-time option (Advanced Settings) and a post-processing editing tool. Results vary with object size, speed, and density.
Measurement
Point-to-Point Distance
Click two points on the point cloud to return the 3D Euclidean distance in meters. Accuracy is subject to point cloud accuracy; treat measurements as approximate to 1 to 2 cm in well-processed scans with RTK. Do not use for contract-level dimensional verification without independent check measurements.
Area Measurement
Define a polygon on a planar surface to calculate area in square meters. Requires a minimum of three coplanar points. Useful for quick room area estimates from the processed point cloud.
Coordinate Readout
Click any point to return its X, Y, Z coordinate in the project coordinate system. On georeferenced scans, these values represent real-world coordinates in the configured target coordinate system. On non-georeferenced scans, values are in the scanner's local reference frame.
Resampling
Point cloud resampling reduces the density of the output cloud by keeping only a representative subset of points at a specified spacing interval. The spacing value determines how many points survive: a tighter interval preserves more detail, a wider interval produces a smaller, more manageable file. For most AEC deliverables, 5 to 10 mm spacing is appropriate for coordination and modeling reference; 1 to 3 mm preserves fine surface detail for high-accuracy dimensional inspection. Resampling is applied before export, not to the internal project data, so the original processed cloud is always intact. A LS 3.5 bug fix resolved an issue where resampling could erroneously delete edge points near feature boundaries.
Merge Tool
The Merge tool combines multiple processed point cloud files into a single output file. This is a post-processing utility, not the same operation as Map Fusion. Map Fusion aligns and combines raw scan segments using shared overlap geometry during the SLAM optimization stage. The Merge tool takes already-processed, already-aligned point clouds and writes them into one file for delivery or downstream use.
Typical use cases include combining separately processed floors of a building into one deliverable, merging independently georeferenced scans of adjacent areas that were not captured as part of a single Map Fusion project, or consolidating multiple exports into a single LAS file for a client handoff.
How to Use
Merge does not re-align point clouds. If the input clouds are in different coordinate systems or have positional offsets, the merged output will contain those offsets. Confirm all input clouds are in the same coordinate system and correctly georeferenced before merging. For clouds that need alignment, use Map Fusion instead.
Export Formats
LixelStudio exports the processed point cloud to four primary formats. The format choice is driven by the downstream software the client or workflow requires. Export settings are configured in the Export panel after processing and review are complete.
LAS to E57 Conversion ToolLS 3.5
A standalone conversion utility added in LS 3.5. Takes a processed LAS format point cloud and merges it with the panoramic photos captured synchronously along the acquisition path, producing an unstructured E57 file compatible with BubbleView-style panoramic viewers and E57-compatible BIM import workflows. This is distinct from the standard E57 export: it combines photographic imagery into the E57 container rather than producing a pure point cloud file.
Licensing and Activation
LixelStudio requires license activation from version 3.0 onward. Each device is identified by a unique serial number (SN) and is entitled to three permanent activation codes. Activation can be performed online or offline.
Loan and demo units do not qualify for license activation. A device SN that was sold in one regional market cannot activate software from a different regional market. If activation fails repeatedly with a valid, unused code, contact XGRIDS Technical Support rather than attempting additional codes. Using a third code when the first two have already failed for a non-obvious reason will exhaust the entitlement without resolving the underlying issue.
©2026 Alpine Reality Capture LLC • XGRIDS Pro Guide™ • Site Disclaimer