CloudCompare forum

I’ve run into similar color inconsistencies in CloudCompare when importing data from different sources. A lot of the time it ends up being related to normalization/scalar field ranges or RGB values being interpreted differently during export/import.
It can help to inspect a few actual color values ...

You might also want to check the point cloud scale and coordinate precision before processing. I’ve seen some strange alignment and rendering behavior in CloudCompare when the coordinates are very large or come from mixed sources. Recentering the cloud or using global shift sometimes fixes it ...

The PCP export can definitely be a bit of a headache when the orientation doesn't line up perfectly with the physical site. I've found that doing a quick real-world check helps troubleshoot those 'flipped' axes before I even start the export. I usually just pull up https://123compass.org/ on my ...

I feel your pain on the large-scale data! Have you considered subsampling a version of the cloud (using 'Space' or 'Random' subsampling) specifically for the annotation task? If you have fewer points, the 'drift' when zoomed out might be less of an issue because the software has fewer candidates to ...

I’ve seen this happen with Inno Setup before if an older installation was partially left behind or if there’s a mismatch during an overwrite. If anyone else runs into this, manually renaming the file or updating the registry path is a quick fix, but it's good to know it might just be a local fluke.

I’ve run into that same 'third-party library' error before with LAS 1.4. It’s definitely a bit of a headache! I found that sometimes clearing out any 'Extra Bytes' or custom scalar fields before exporting helps the LAZ compressor handle it better.

Even if the error message is hard to improve, having this thread as a reference is great. It definitely saves time for those of us trying to figure out if it's a software bug or just a hardware limitation.

The 'Translate/Rotate' tool can be a bit tricky if you're new to the workflow. If the cloud keeps jumping back to its original spot, try using Edit > Apply Transformation and manually paste the matrix from your console. It feels a bit 'manual,' but it’s the most foolproof way to make sure CC writes ...

This is such a tricky UI quirk. It makes sense that CC only merges what's 'selected,' but the fact that it deletes the unselected children in the stable version is a bit brutal. Until the fix/warning is added, I'm definitely going to be double-checking my DB tree expansion before every merge.