Bug with mesh split

If you are allergic to bug trackers, you can post here any remarks, issues and potential bugs you encounter
Post Reply
deepminder
Posts: 11
Joined: Mon Feb 22, 2016 6:53 am

Bug with mesh split

Post by deepminder »

Hi Daniel,

I have discovered one bug in CC during work with meshes.
This is the mesh I work with. It has scalar field.
Image
I try to split it into two parts, depending on the scalar value. Got this:
Image
But the area between meshes is deleted:
Image
As a result, the area of initial full mesh is not equal to the sum of splitted meshes.
Is there a possibility to fix it?

Thanks in advance!
daniel
Site Admin
Posts: 7330
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: Bug with mesh split

Post by daniel »

Oh, this is not a bug, but more a 'feature' ;)

Triangles are discarded whenever at least one of their vertex scalar value is out of the range. And as when we 'split' we simply apply one range and the other, the triangles one the border are always removed!

But I agree we should find a way to be smarter :D
Daniel, CloudCompare admin
deepminder
Posts: 11
Joined: Mon Feb 22, 2016 6:53 am

Re: Bug with mesh split

Post by deepminder »

Is there a possibility to save scalar value in the triangle and not in the vertex?
daniel
Site Admin
Posts: 7330
Joined: Wed Oct 13, 2010 7:34 am
Location: Grenoble, France
Contact:

Re: Bug with mesh split

Post by daniel »

Well CloudCompare is a point cloud software, and therefore it considers meshes as a point cloud with connectivity (not as sets of triangles ;).

But for this particular segmentation issue, the fix is easy (we just need to find the time to apply it ;).
Daniel, CloudCompare admin
Post Reply