CloudCompare forum

Greetings. I find myself doing the exact same steps in CC - like 100 times a month. I'd love to have a batch or script. It'd save hours and hours of time. But it seems like the CMD line version doesn't support many features at this point? Any help or ideas would be great. This is what I do: 1) Impor...

Thanks, I'll give that a try.

Just wanted to follow up on this feature. It works as stated and is amazingly useful... but it takes a VERY long time with larger scans. scans in the <40mb range compute quickly scans in the 100mb range can take much longer. 30 minutes. An hour. I've left some larger scans to compute overnight and i...

It works!

Terrific, what a useful feature.

Thanks for implementing!

I didn't know about that feature. Here are the sensor parameters for that same scan:

Cool! I had a chance to try it for a minute. It kind of works. Looks like the 'sensor' position CC is generating isn't getting put in quite the right spot. The scanner head data listed in the e57 exported from FARO scene: <translation type="Structure"> <x type="Float">-9.36669992...

I meant for the purpose of normals generation.

Isn't that how the "use sensors whenever possible" feature works in the Computer Normals dialog?

Each point's normal vector is just pointing at the sensor xyz location, and doesn't require any orientation data. Right?

Hi, wondering if you still have plans to have CC read in the following metadata from the e57 and create a sensor from it: <translation type="Structure"> <x type="Float">1.45285997999999994e+00</x> <y type="Float">-6.60723456999999903e-01</y> <z type="Float">3....

Let me know if I can provide you with any other data or information.

I feel a bit guilty regarding how time consuming debugging this FARO sdk stuff is for Daniel. But who knows when you post one bug that it's going to unravel into a complex mess? The FARO Scene > CC > Meshlab is a fantastic workflow for getting VERY good colored/textured meshes. I don't know what I w...