FAQ

1. Watermark and AppKey

Cause: Starting from SDK v0.5.0, a watermark is displayed in the lower-left corner by default.

Solution: Contact the sales team to obtain an AppKey, then set the appKey parameter in LCCRender.load() to remove the watermark.

2. SDK Integration Error in Babel Projects

Cause: The SDK uses modern browser syntax. Babel may compile it into older syntax, potentially causing runtime errors or compilation failures.

Solution:

1. Configure Babel to exclude the SDK files from compilation.
2. Or include the SDK file via a <script> tag to bypass compilation:

<script src="./sdk.js"></script>

After including it, use LCC.LCCRender to load.

3. LCC Model Not Visible in Three.js Engine

Follow these troubleshooting steps:

1. Check the browser console for error messages (e.g., file not found).
2. Verify that the files in dataPath are accessible and downloadable.
3. Check whether the camera's far plane value is large enough — the model may be outside the camera frustum.
4. Verify that LCCRender.update() is being called in the render loop.

If none of the above resolves the issue, feel free to contact technical support or ask in the forum.

4. 3D Tile Model Occluded by LCC Model in CesiumJS

Cause: By default, the LCC model writes to the depth buffer and the depth test function is set to always pass (ALWAYS). In the Pass.CESIUM_3D_TILE render queue, if 3D Tiles are loaded before the LCC model, they will be overwritten by the LCC model's depth.

Solution:

• Load the 3D Tile model inside the success callback of LCCRender.load().
• Or, after both are loaded, call lccObject.lowerToBottom() to move the LCC model's rendering order to the front.

5. CesiumJS Legacy Version Support

Cause: Cesium v1.102 and later default to WebGL2, while earlier versions default to WebGL1. The Web SDK does not support WebGL1, so WebGL2 must be forced.

Solution: Force WebGL2 to be enabled. The minimum supported version is Cesium v1.67.

const viewer = new Cesium.Viewer("cesiumContainer", {
    orderIndependentTranslucency: false, // Disable order-independent translucency
    useDefaultRenderLoop: true,
    resolutionScale: window.devicePixelRatio,
    contextOptions: {
        webgl2: true, // Force WebGL 2.0
        requestWebgl2: true
    }
});

6. Viewer is Laggy Despite Good Hardware

Cause: On computers with multiple GPUs (e.g., Intel integrated GPU + NVIDIA dedicated GPU), Windows may default to the integrated GPU, resulting in rendering lag.

Solution:

1. Set the computer's power mode to "High Performance".
2. In the NVIDIA Control Panel, set the browser to use the dedicated GPU.
3. In Windows Settings → Display → Graphics, set the browser to use the "High performance" GPU.

Restart the browser after completing the settings to ensure the new configuration takes effect.

7. Rendering is Laggy Despite Adequate Hardware

3DGS rendering has high resource demands. Close resource-intensive applications such as 3D editors, LCC reconstruction tasks, HD video playback, high-speed downloads, and video streaming to free up the necessary computing resources.

8. Same Laptop Shows Inconsistent Performance

If you experience inconsistent performance (sometimes smooth, sometimes laggy) when navigating scenes on the same laptop at different times, the cause is most likely related to whether an external power source is connected. When running on battery power, the laptop employs power-saving strategies that reduce CPU and GPU performance, which may cause lag. It is recommended to use an external power source when browsing 3DGS scenes.