SLAM Crash: "The movement distance is insufficient" in Lidar360MLS 8.1.0 (Ligrip H300) - Machine Specific Issue

[Polina Kuklina]

I am encountering a persistent issue while processing data from a Ligrip H300 system in Lidar360MLS software (version 8.1.0). The SLAM processing crashes with the error: "The movement distance is insufficient" followed by "Slam crashed".

The puzzling part is that the exact same dataset processes successfully without any errors on a different computer using the same software version.
This suggests the problem is specific to my machine's configuration. Has anyone faced a similar issue, or could you point me in the right direction to troubleshoot this?

Here is what I can share about my setup:
Software: Lidar360MLS 8.1.0
Hardware Scanner: Ligrip H300
OS: Windows 10 Pro (64-bit)
CPU: Intel Core i7-14700
GPU: NVIDIA GeForce RTX 4070
RAM: 64 GB

Things I have already checked/tried:
Reinstalled Lidar360MLS cleanly.
Verified that the project paths are not too long and contain no special characters.
Made sure all Windows updates are installed.

Any advice or insights would be greatly appreciated!
Thank you in advance.

[Sebastien Garceau]

Hello,

Juste some ideas based on personal experience...
Is the raw data on a local drive (i.e. not on cloud storage or external storage) ?
Are your component drivers up to date ?

Good luck