some segments do not reconnect in the right order, and therefore a few pieces remain isolated. This is a problem of tolerances that are way too high when they arrive to the inner computations. RH-65835
Could you please take a look at Brep.CreateContourCurves as well? It creates 4 or 5 segments sometimes (on edges mostly). what about adding a merge/join built-in in command option?
Does this problem only happen with this geometry or do you many models that exhibit this behavior? I looked into this some, you can see my notes on the YT issue, and I don’t think this is Contour or Section despite the problem manifesting itself there. For example, I was able to make a cut plane in the problem region. I extracted the 3 faces of the brep that seem to have issues and intersected them individually with the same cut plane. In theory, since those surfaces were joined you ought to be able to join the curves from the separate intersections. 2 did, the end points were .009 units apart. The last one didn’t. It’s end was .012 from the other end point.
@dale Thanke Dale @tim Yes, that problem only happens with this Brep, I don’t have any other models. I tried to do same with mesh, but it produces a lot of segments in another particular areas even in Y direction and Diagonal directions. So, how can we overcome of this issue?
If you have access to version 6 you could try contour there. In V6, Contour (and Section) use a different mesh/plane intersector. If it works better then we should log bugs for the mesh/mesh intersector that is used in V7.
In the case of polysurfaces, Contour does use a low level function that is different than intersection. It calls a function that does one face at a time. Intersection does an entire polysurface, I suspect that ultimately it also calls the one face at a time function though too, I just didn’t look.
I know these problems manifest themselves in Contour but they’re deeper than that. Contour just automates the process of making a bunch of cut planes, doing the intersections and joining the results. The key to fixing the problem is taking Contour out of the equation. I know you can’t see the models in the YT issue (the permissions are such that only developers can view them because you sent your initial model as a pm) but I was able to isolate cut planes that exhibited the weird behavior outside of Contour. Doing more of that and reporting them as surface/surface intersection problems or mesh/mesh intersection problems will help.
How did you create the polysurface in the first place? Did you make it entirely in Rhino?
I think I have to install Rhino 6 trial version to test it, yeah good idea!
I didn’t know how is behind of contour, Thanks so much for great explanations.
I can see the YT issue, thanks to @dale, he changed visibility to public view.
The Brep/Polysurfaces is made by our customer and I’m sure they didn’t use Rhino. It was a STEP(stp) file and when I imported it in Rhino, Rhino created 19 Surfaces and then I joined them together to make a polysurfaces/brep.
I should try your last question!
Thank you so much for your efforts!
What we’d actually like to see is the step model that you made the Rhino file from. Can you walk us through the process you took to get to the point of the Rhino file you sent in?
@pascal I have sent it to that email. @tim After opening that STEP file, I have removed that Circle only and those objects that arent inside of the shape. Then joined all 19 surfaces together and saved as 3dm Rhino file.