XGRIDS Pro Guide™ / Module 10: Resources

Platform Compatibility

Every export format, every supported platform, and every downstream software tool that works with XGRIDS output. Use this page to confirm a deliverable format before quoting a project.

Two Pipelines, Different Output Universes

LixelStudio outputs point clouds. LCC Studio outputs 3D Gaussian Splat models. These are fundamentally different data types that go to fundamentally different downstream platforms. A client asking for "the scan in Revit" could mean either, and the answer depends entirely on which pipeline you used and what they plan to do with it in Revit.

Point clouds from LixelStudio integrate directly into the existing AEC software stack: Revit, AutoCAD, Navisworks, Leica Cyclone, and any software that reads E57, LAS/LAZ, or RCP. Gaussian Splat models from LCC Studio go to a newer parallel universe of visualization, XR, and game engine platforms, plus the LCC for BIM plugin for Revit specifically. They do not substitute for point clouds in traditional AEC workflows.

Device-to-pipeline reminder: L2 Pro and K1 feed both pipelines from the same raw scan. K2 feeds LixelStudio fully and LCC Studio in Single Model reconstruction or Spatial Recognition (90-minute single-scene cap). K2 is excluded from LCC Studio Map Fusion. PortalCam feeds LCC Studio only and does not produce point clouds.

LixelStudio Export Formats

LixelStudio exports colored, georeferenced point clouds. All formats carry intensity, color (RGB), and trajectory data. Coordinate system and georeference are applied during processing, so the export format does not change the accuracy of the data, only the software compatibility.

LAS / LAZ

Industry standard point cloud format. LAZ is the losslessly compressed version of LAS. Both carry full RGB color, intensity, GPS time, and coordinate data. The most widely accepted format for GIS and survey delivery.

  • ArcGIS, QGIS, Global Mapper
  • CloudCompare, Leica Cyclone
  • Autodesk Recap (import via LAS)
  • Virtually all point cloud viewers and processing tools

E57 (Structured)

ASTM-standardized format designed for 3D imaging data exchange. LixelStudio exports structured E57 that preserves scan position metadata alongside point data. The preferred format for BIM import workflows where scan-world origin matters.

  • Autodesk Revit (via Recap)
  • Autodesk Navisworks
  • Autodesk AutoCAD
  • FARO Scene, Leica Cyclone, Trimble RealWorks
  • Bentley iTwin, Hexagon HxDR

RCP / RCS

Autodesk Recap Project format. Native Autodesk point cloud format that loads directly into Revit as an attached point cloud, AutoCAD, Civil 3D, and Navisworks without conversion. The fastest path to the Autodesk AEC pipeline.

  • Autodesk Revit (direct attach)
  • Autodesk AutoCAD / Civil 3D
  • Autodesk Navisworks
  • Autodesk Recap Photo / Pro

OBJ (with texture)

Textured mesh export from LixelStudio. Geometry with color baked in as a texture map. Not a point cloud format. Used when a lightweight polygon mesh deliverable is required rather than full point density. Compatible with most 3D tools and game engines.

  • Autodesk 3ds Max, Maya, Blender
  • Unreal Engine, Unity
  • SketchUp, Rhino
  • Most 3D visualization software

Revit workflow note. Revit does not natively open LAS or E57 directly. The recommended path is to import into Autodesk Recap first, then attach the Recap project (.rcp) to Revit. Exporting directly to RCP from LixelStudio skips the Recap conversion step. For the freshest compatibility, verify the Recap version matches the Revit version before beginning a large project.

LCC Studio Export Formats

LCC Studio outputs 3D Gaussian Splat models. The format you choose determines file size, downstream software compatibility, and what visual fidelity is preserved. Choose before processing: the Portability setting during reconstruction affects which formats are available at export.

LCC

XGRIDS proprietary compressed format. 70 to 90% smaller than PLY while preserving full model quality. Required format for the LCC for BIM Revit plugin and XGRIDS developer SDKs. The default format for any workflow staying within the XGRIDS ecosystem.

  • LCC Studio (native)
  • LCC for BIM plugin (Revit)
  • Unreal Engine (via XGRIDS SDK)
  • Unity (via XGRIDS SDK)
  • XGRIDS cloud publish and share link

PLY

Open standard 3DGS format. The most broadly compatible format for third-party Gaussian Splat tools. Larger file size than LCC (typically 5 to 10 times larger). Use when delivering to a client or platform that does not support LCC natively.

  • Supersplat, Volinga, Gauzilla Pro, Nubigon (editing tools)
  • Unreal Engine (community 3DGS plugins)
  • Unity (community 3DGS plugins)
  • VOLUMA, QuarkXR, Splatter.app, Arrival Space (display platforms)
  • Any open-source 3DGS viewer

USDZ

USD-based container format that preserves Gaussian ellipsoid data for the NVIDIA Omniverse ecosystem. Opens natively in the USD ecosystem.

USDZ export requires three conditions to be met simultaneously: scanner firmware version 3.0 or later, single-scene reconstruction type, and Portability disabled. If any condition is not met, the USDZ option remains grayed out.

  • NVIDIA Omniverse
  • USD-compatible pipelines

3D Tiles

Tiled format for WebGIS and digital twin web applications. Conforms to OGC 3D Tiles 1.1 standard and loads directly in Cesium 1.131. Requires the model to have absolute coordinates applied (RTK or GCPs during scan).

3D Tiles has a 4 million Gaussian point ceiling. Models reconstructed above this point count cannot be exported as 3D Tiles. If WebGIS delivery via Cesium or ArcGIS is a firm deliverable requirement, set Maximum Gaussian Splats at or below 4 million during reconstruction. This also limits model detail and VRAM requirements. Decide before processing, not after.

  • Cesium (web and native)
  • Esri ArcGIS (integration confirmed as of December 2025)
  • Any OGC 3D Tiles 1.1 compliant WebGIS platform

Mesh Export (OBJ / PLY)

Optional triangular mesh export without textures. Geometry only. Use when a downstream platform requires polygon geometry rather than point or splat data. The mesh is derived from the Gaussian Splat reconstruction and does not carry RGB texture data.

  • Autodesk 3ds Max, Maya, Blender
  • Unreal Engine, Unity (as static mesh)
  • Any OBJ/PLY compatible tool

Collision Mesh

Simplified collision geometry for game engine and XR application use. Exported from the LCC Studio Editor. Used when integrating an LCC model into Unreal Engine or Unity and requiring physics-based collision rather than visual-only splat rendering.

  • Unreal Engine (collision volumes)
  • Unity (physics colliders)
  • XR environments requiring spatial boundaries

Which Format for Which Deliverable

If the client or project requirement is already known, use the table below to confirm the export path before quoting or processing.

Deliverable Requirement
Pipeline
Export Format
Autodesk Revit (BIM modeling from point cloud)
LixelStudio
RCP (direct attach) or E57 via Recap
AutoCAD or Navisworks (point cloud)
LixelStudio
RCP or E57
ArcGIS, QGIS, GIS delivery
LixelStudio
LAZ with georeferenced coordinates
Faro Scene, Leica Cyclone, Trimble RealWorks
LixelStudio
E57 (structured)
Mesh deliverable from point cloud
LixelStudio
OBJ with texture
3DGS visualization or web share (XGRIDS ecosystem)
LCC Studio
LCC
3DGS visualization (third-party broad compatibility)
LCC Studio
PLY
Unreal Engine or Unity
LCC Studio
LCC via XGRIDS SDK, or PLY via community plugins
Cesium or WebGIS digital twin
LCC Studio
3D Tiles (requires absolute coordinates and under 4 million points)
NVIDIA Omniverse
LCC Studio
USDZ (firmware 3.0+, single-scene, Portability off)
XR with physics interaction
LCC Studio
LCC + Collision Mesh
Revit with 3DGS reference (AI-assisted modeling)
LCC Studio
LCC, with LCC for BIM plugin in Revit 2025 or 2026

LCC for BIM Plugin (Autodesk Revit)

The LCC for BIM plugin brings 3D Gaussian Splat models directly into Revit. It does not replace a traditional point-cloud-to-BIM workflow. It adds a second, parallel path that enables AI-assisted element extraction from the 3DGS model using the Spatial Recognition data generated during LCC Studio processing.

What the Plugin Does in Revit

Once installed, the plugin adds an LCC Module to the Revit Add-ins tab. The primary workflow is: import an LCC model via the LCC Project Wizard, view it in the LCC Viewer panel embedded in Revit, then use the Modeling Tools or 2D Canvas to generate Revit elements from the scan data.

The LCC for BIM plugin requires Revit 2025 or 2026. Confirmed in the LCC for BIM User Manual v1.1.0 (October 2025). If the project requires Revit 2024 or earlier, use the LixelStudio point cloud pipeline with an RCP or E57 export instead. There is no workaround for older Revit versions with the LCC plugin.

Third-Party Platform Support

The following platforms and tools have confirmed LCC format compatibility or official partnership status as of December 2025. This list reflects the LCC Ecosystem document from XGRIDS. Check xgrids.com for the current partner list as new integrations are added regularly.

Application Tools

  • Autodesk: LCC for Revit Plugin (Revit 2025/2026)
  • Esri: ArcGIS integration confirmed (announced Nov 2025)
  • NVIDIA: Omniverse integration via USDZ
  • Prevu3D
  • Lightwheel

Display Platforms

  • VOLUMA
  • QuarkXR
  • Splatter.app
  • Arrival Space
  • Teleport
  • Nucleus
  • Bizztech

Editing Tools

  • Supersplat (open-source 3DGS editor, PLY format)
  • Volinga
  • Gauzilla Pro
  • Nubigon

Platform Support

  • Unreal Engine: LCC SDK at developer.xgrids.com
  • Unity: SDK with Quest 3 and Pico XR supported
  • WebGL: Cesium integration via XGRIDS SDK

Developer resources. XGRIDS publishes SDK documentation for Unreal Engine, Unity, and WebGL integration at developer.xgrids.com. This includes the LCC format specification, integration examples for Quest 3 and Pico XR devices, and the Cesium WebGL integration guide.

For the current partner list and ecosystem updates, visit xgrids.com or contact your authorized reseller.

©2026 Alpine Reality Capture LLC  •  XGRIDS Pro Guide™  •  Site Disclaimer