Map Fusion Processing | XGRIDS Pro Guide
XGRIDS Pro Guide™ / Module 5: Project Scale

5.4 Map Fusion Processing

Creating the fusion project in LixelStudio, configuring each segment, running the job, and evaluating the result.

Hardware Requirements

Map Fusion is more computationally demanding than single-scan processing. Verifying hardware before starting a long fusion job prevents a failure at hour 30 of a 65-hour run.

Component
Minimum
Recommended for Fusion
CPU
i7 11th generation, 6-core minimum
AMD Ryzen 9 9950X or equivalent 16-core processor
RAM
LixelStudio: 32 GB minimum (short scans only), 64 GB supports approximately 30 min. LCC Studio: 64 GB minimum — 32 GB will fail.
96 to 128 GB DDR5 for total scan durations at or above 150 minutes in either application
GPU
NVIDIA RTX 3060 12 GB minimum. AMD is not supported.
NVIDIA RTX 3090; RTX 4090 or 4090D for optimal performance
Storage
Free space equal to 2 to 3 times the raw project size
NVMe SSD. SATA SSDs increase processing time by 15 to 25%.
OS
Windows 10 or 11 only
Windows 11 with latest NVIDIA driver (520.0 or later)

Processing time estimates are real. At Medium Quality settings on recommended hardware, expect approximately 20 minutes of compute time per minute of scan data. A 200-minute project is approximately 65 hours of processing. Set Windows power settings to never sleep before starting. Close all non-essential applications. Do not use the machine for other work during processing.

Project Setup

Setting up a fusion project correctly at the start prevents configuration errors that require restarting the entire job.

1

Transfer All Segment Data to the Processing Machine

Copy all segment folders from the scanner to a dedicated project folder on an NVMe SSD. Keep each segment in its own folder, named according to your planned naming convention. Verify all files transferred completely before beginning processing.

2

Open LixelStudio and Create a New Project

Select Map Fusion as the project type. Do not create a Single Scene project and attempt to add multiple segments. The project type must be set at creation. Single Scene and Map Fusion are separate processing pipelines.

3

Import Segments in Sequence

Add each segment in collection order. The sequence matters for control point matching, the algorithm processes connections between adjacent segments based on the order they are loaded. Import Segment 1 first, then 2, then 3, in the order they were scanned.

4

Upload Panoramic Video Files for L2 Pro Segments

If your segments were scanned with the L2 Pro panoramic camera, upload the matching panoramic video file for each segment at this stage. K1 and L2 Pro without panoramic camera will skip this step automatically.

5

Verify the Estimated RAM Usage

LixelStudio displays estimated RAM usage before processing begins. If the estimate approaches or exceeds your installed RAM, enable Low-Memory Mode or reduce the number of segments per fusion job. Running without sufficient RAM causes a failure mid-processing, not at the start.

Configuration

The configuration settings for a fusion job control how the algorithm handles SLAM optimization, RTK data, and the alignment computation. The defaults are appropriate for most projects. The settings below are the ones you need to understand when the defaults are not the right choice.

Quality Setting

Fast, Standard, and Slow settings control algorithm depth and iteration count. Standard is the recommended starting point for fusion projects. If the first attempt at Standard fails or produces misalignment, switch to Slow before troubleshooting collection. If RAM is the constraint, Medium Quality (Standard) reduces memory consumption relative to Slow at a modest accuracy trade. For large projects at or above 150 minutes total, use Medium Quality to avoid processing failures on machines with 96 GB or less of RAM.

SLAM Mode

Three options are available. None produces the highest accuracy and should be used when collection technique was sound and there are no known drift problems. Robust is the default balanced setting, it handles moderate drift and degraded environments better than None at a slight accuracy trade. Narrow Scene is for tunnels and mine galleries specifically; it should not be applied to standard indoor projects.

Loop Closure

Enable Loop Closure when the scan route within any segment included intentional loop paths back to the initialization area. Loop Closure distributes accumulated error across the whole trajectory rather than allowing it to concentrate at the end of the route. If the route was mostly linear with limited loop opportunities, Loop Closure has less effect and can be left at default.

RTK Data Handling

Auto is the default. In Auto mode, LixelStudio applies RTK data where it is valid and ignores it where it is not. Disabled forces the processor to treat all segments as having no RTK. Use Disabled only if RTK data is known to be corrupt or if you intentionally want a relative-coordinates-only output. Do not disable RTK as a troubleshooting step without understanding that doing so removes global coordinates from the entire fused result.

Reference Map Selection

If your fusion project includes segments with different accuracy levels, for example, one segment with excellent RTK and several without, designate the highest-quality segment as the reference map. Other segments align to it. The reference segment should be the one with the most reliable individual SLAM quality and the strongest RTK or control point anchoring.

Processing Phases

Map Fusion processing runs in three sequential phases. Understanding what each phase does helps you interpret progress indicators and diagnose where a failure occurred.

Phase
What Happens
What to Watch For
Individual SLAM Optimization
Each segment is processed independently through SLAM trajectory optimization. Point cloud is generated for each segment separately.
Errors in this phase are segment-level problems: drift, insufficient features, initialization issues. The failed segment must be identified and either reprocessed with different settings or recollected.
Alignment Computation
The algorithm computes the transformation matrices needed to align each segment to its neighbors using RTK data, control point matches, or both.
Control point matching failures appear here. If a point name does not match between segments, the connection fails. RTK validity issues also surface at this stage.
Global Optimization
All segments are simultaneously optimized in the shared coordinate space. Accumulated error is distributed across the full dataset.
This is the most computationally intensive phase and the one most sensitive to RAM availability. If the machine runs out of memory, the failure occurs here.

Do not interrupt processing between phases. LixelStudio writes intermediate data during fusion. Interrupting the process mid-run, even between phases, can corrupt the project file and require restarting from import. Set the machine to never sleep and let the job run to completion without interruption.

Quality Review

After processing completes, review the fused result before exporting. A quality review that takes 15 minutes catches problems that would waste hours of downstream work in Revit or AutoCAD.

Segment Boundary Inspection

Navigate to each segment boundary, the area where two segments join, and inspect the geometry. A well-aligned fusion shows seamless continuation of geometry across the boundary. Misalignment shows as a step, doubling of surfaces, or geometry that does not line up between the two sides of the boundary. If misalignment is visible, the connection at that boundary needs to be investigated before the result is used.

Accuracy Report and RMSE

Review the accuracy report generated after processing. The RMSE values at each control point connection show how closely the algorithm achieved the theoretical alignment. High RMSE at a specific connection indicates a problem with that segment pair's connection data, poor overlap, a control point with inconsistent position between takes, or an RTK validity issue.

Coverage Completeness

Verify that the fused output includes data from all segments and that there are no unexpected gaps at the transition zones. A segment that failed during individual SLAM optimization may be absent from the fused result, the final dataset will be missing the territory that segment was supposed to cover.

Export

The fused result exports from LixelStudio as a single dataset. The format selection follows the same decision logic as single-scan exports.

Format
Best Use
Notes
E57
BIM integration, Revit, AutoCAD, Navisworks
Industry standard. Structured format with embedded coordinate system. For data with absolute coordinates, use pose_no_offset.csv; without absolute coordinates, use pose.csv. Filename must be 20 characters or shorter or export fails.
LAS/LAZ
GIS platforms, general point cloud tools, CloudCompare
LAZ is compressed LAS with no quality loss. Standard choice for most downstream workflows outside Autodesk ecosystem.
RCP/RCS
Autodesk ecosystem: Revit, ReCap Pro, Civil 3D
RCP is a lightweight project file that references RCS scan files. Does not embed raw data. Efficient for large datasets in Autodesk workflows.
PLY
General 3D tools, open-source workflows
Maximum compatibility. Large file size. No native Autodesk support.

Next: managing large datasets after export.

Data Management →

©2026 Alpine Reality Capture LLC  •  XGRIDS Pro Guide™