Hi there,
I’m pretty new to using pointclouds with Rhino, but never had this problem before.
I exported a pointcloud from cloudcompare as an e57 with 394.545 points, imported it into Rhino where it now shows only 393.216 points. And the upper corner is not correct, which must be where I lost those points (I attached pictures of CC and Rhino). I’ve imported pointclouds the same way before and never had this problem. What could be the issue here?
If you are not familiar with Cloud Compare, try clicking on the check boxes in Cloud Compare to see if it shows up. You may need to click on the arrows to expand the list of objects. If it is a separate cloud, you can select multiple clouds and export selected. The cloud(s) must be selected individually, using the checkboxes alone will not work.
If that doesn’t work, can you post the Cloud Compare .BIN file, if it is small enough?
In Cloud Compare everthing looks fine, It should be just one pointcloud and i’ve made sure to export everything I wanted. But when I open the exported e57 in Rhino it doesn’t. I cut the object out of a bigger point cloud, since i cant upload a bin for some reason i’ve attached the exported e57. When I open that in Rhino it looks completely different than it did in cloud compare. as seen in this screenshot. I think something might be going wrong with the import into Rhino.
trial.e57 (14.8 MB)
This is curious, Rhino is definitely throwing points out when it imports this file. However, if you import the e57 back into Cloud Compare and save it as a new e57, that new e57 does read completely into Rhino. The developers should look at this to see why this is happening.
haha thank you for trying it out 
at least i know it’s not me importing it wrong or anything.
Was this scan generated differently from the ones you usually work with?
no it’s all the same. Plus I’ve imported the whole pointcloud into rhino and that wasnt a problem, but with the cut out of just a specific part over cloud compare this keeps happening.
Hi Dale, the e57 is in her second post above
RH-90779 is fixed in Rhino 8 Service Release 27 Release Candidate
