brep.MergeCoplanarFaces out of tolerance

Rhino Developer
1

Hi,

I’m running into an issue with brep.MergeCoplanarFaces
The attached black polysurface is slightly kinked, but apparently enough to allow for the 2 faces to be regarded coplanar.

However after merging the faces the trimming edges are out of tolerance:
image

If I brep.Repair the merged brep I do get correct trimming edges, however there is a deviation of the initial surface of 0.459 which exceeds the file tolerance.

image
image.png1015×389 11.9 KB

However , the Command _MergeFace will correctly state :
“Unable to move edges within face tolerance, nothing done”

How do I go about making sure the merger was within tolerance?
Should I check edge deviations myself or am I missing some additional RhinoCommon functionality?
What coplanarity tolerance is used?

Thanks
-Willem

below example file and script

merge_coplanar.3dm (48.2 KB)

import rhinoscriptsyntax as rs
import scriptcontext as sc


obj = rs.GetObject('select brep ro merge coplanars')
if obj:
    brep = rs.coercebrep(obj)
    
    tolerance = sc.doc.ModelAbsoluteTolerance
    
    brep.MergeCoplanarFaces(tolerance)
    id = sc.doc.Objects.AddBrep(brep)
    rs.ObjectColor(id ,  [255,0,0] )
    
    brep.Repair(tolerance)#make sure the edges are correct
    id = sc.doc.Objects.AddBrep(brep)
    rs.ObjectColor(id ,  [20,255,0] )
2

Hi @Willem,

Well, I know the command checks both faces and loop for tolerance. I’m not sure how to help, right now in this, case.

https://mcneel.myjetbrains.com/youtrack/issue/RH-46914

– Dale

1 Like
3

Hi Dale,

Thanks for your answers. At least I’m sure we did not miss something. I might revert to a scripted command untill I’ve implemented my own deviation check.

-Willem

4

Hi @rajaa, Is there any news on this issue:

https://mcneel.myjetbrains.com/youtrack/issue/RH-46914

I ask because I might need to write my own tolerance check if a solution from your side will not be available in the near future.

Thanks Willem

5

@Willem this is close to the top on my list.

6

Great! thanks for the quick reply.

-Willem

7

RH-46914 is fixed in the latest Service Release Candidate

1 Like