CloudCompare forum

Hum, I guess you'll have to indeed try to add a first pass to find the rough alignment. Something like what you suggest would work but it can be very time consuming (i.e. rotating the cloud every 5 degrees and trying to perform the alignment, and then keeping the best result). Or you can dabble with ...

Which version are you using?

The way the red X, green Y and blue Z appear on the left side of the label is weird. And also, how and when was the 'coord Z' scalar field generated? Does it really match the coordinates in the current cloud position?

Last, even if I agree it's a different problem ...

There's no way to select a point based on its index at the moment. But you can generate the 'point index' scalar field (Edit > Scalar fields > Add point indexes SF'), and then user the scalar field min/max displayed values, or the ''Edit > Scalar field > Filter by value' to isolate this point.

Can you share the link to the plugin code? (ideally it should be in a dedicated repository that we could add as a submodule).

And don't hesitate to move this discussion to github (it will be easier).

So for the second request, you already have the 'a' or 'v' shortcut (see 'Edit > Toggle (recursive)' menu).

For the other one, it might not be easy to have a 'memory' of the previous selection, but at least an option 'hide all others' would make sense.

I think it's because of the Python plugin (that loads the Python environment). If you don't use it, you can probably uninstall and re-install CC without it.

Good point, I've added something to the 'Rasterize' tool wiki ( https://www.cloudcompare.org/doc/wiki/index.php/Rasterize#Hillshade_/_X-ray ).

(I also fixed the nice typo on the line pointed by your link to the code :-D).

And the good thing about the automatic saturation is that it's only the ...

CloudCompare does not rely on that many third party software packages, and definitely not the most widespread.

More importantly, as stated in the article: " The infections spanned JavaScript, TypeScript and Python repositories ". We don't use any of these in the CloudCompare application itself ...

Well, we don't support Oculus headsets anymore, but we did in the past, so it's technically feasible (you may want to refer to the commit where it was removed: https://github.com/CloudCompare/CloudCompare/commit/2d13bb9e5ed5c60cc02f993bb3559d779155d557 ).

If you manage to make it work again with ...

The Cross section options may not have been all transferred to the command line.

Can you share with us the command line you tried?

And if you send me some data (admin@cloudcompare.org), I can try to add the right option.