CloudCompare forum

Which graphic card and screen (resolution, technology, etc.) are you working with?

Have you tried to change the projection mode? Are the coordinates of the points too large maybe? (in which case the points may not appear where they really are in space...).

I'm a bit puzzled by the fact that you seem to work with a (Delaunay?) mesh instead of the point cloud... Is there any reason for that?

With the Cross section tool, you have to 'extract' the slice (= create a new entity). This will duplicate the data, so that's safe. And then you can run the process on this excerpt. But that has to be done explicitly each time. Then remove the subset cloud if you don't use it anymore. (also, unrelat...

Or maybe that's a super smart protection to prevent people from creating their own installer of Cloudcompare and infringing the GPL license ;) Just kidding. The only other culprit I see is the Visual Studio 2019 Installation framework you used. I don't know anything about it, but I guess an installe...

It's just that it's a 'utility' function and not a real algorithm/process. You could call it 3 or 5 times with different SF names, and that would make a super long 'composite' name...

Hi,

Maybe it would be better to ask this question on the project's github page (as an issue). I'm not sure Paul (the maintainer of the CloudCompy project)ever comes on this forum.

Unless you also get this error when running the standard version of CloudCompare of course ;)

At minimum, I've increased the timestamp resolution of the output files in this version: https://www.cloudcompare.org/release/Cl ... up_x64.exe

So if you have a single polyline, you can simply highlight its 'vertices' and save it as an ASCII cloud. With this format, you'll get all the associated pieces of information (if any), and a choice to output a header or even the number of points. Otherwise, I don't know any other simple 'common' for...

I've just looked at the code, and I don't see any 'auto-save' call associated to this option. So you have to manually call -SAVE_CLOUDS. But by default a timestamp is added to the original filename. Therefore, the only way to overwrite the original file is either to voluntarily disable the timestamp...

Hi, I finally found the time to look at your data. First, that's probably a detail, but since the radius of the hole is around 0.75 units, I think the distance of 0.7 units for the central part of the bottom of the hole is not inconsistent: hole_diameter.JPG But anyway, you are correct, the RMS of t...