Hello, I need to work a lot with meshes from 3DScanners and found what I believe to be a serious bug in the ProjectCurveToMesh rhinoscriptsyntax function. [image] Here, trying to project a curve (a simple line below the XY-plane in the Z+ direction) onto a simple grid mesh with a U-shaped hole g…

To try and isolate the problem, I split a simpler mesh MeshToSplit5.stl (11.5 KB) by projecting a small segment onto it. This segment was supposed to disconnect the mesh along it and create new triangles but it should still result in a SINGLE MESH, NOT TWO (as we got here!). [image] From a topol…

Something funny is going on. If you just use the Project command, it will fail. But if you exude the curve into a mesh plane and run MeshIntersect, you will get the result you want. All this using your MeshToSplit1.stl file. I’ve reported this… http://mcneel.myjetbrains.com/youtrack/issue/RH-31360 …

Hi, For a few months now, I have been using the project curve than split pattern instead of a mesh/mesh intersection because I had bad experiences with it and the curve projection way seemed to be more robust. I know the first example uses a line coinciding exactly with some of the mesh edges and …

Hello, Do you have any information about this example where we see the SplitMeshWithCurve giving the wrong number of connected components? Theoretically, this split is suppose to create a single mesh with a kind of duplicated border (one for the upper part of the mesh and one for the lower part) a…

I have had similar problems. I have a batch script that trims an input mesh using an input curve. It works well most of the time however sometimes the result is a thin disjointed mesh consisting of triangles just around the (closed) curve similar to “split component 2” above. Unfortunately this occ…

Here is a relatively involved (and costly) strategy to bypass this problem. 1) Use the CGAL library for the meshing operations where you need robustness. This C++ library can be used freely for academic purpose but buying the modules you need for commercial development will probably cost you a few…

It is unfortunate that one would have to go to such lengths to fix something that should be working out of the box. @dale is this being actively worked on for V6?

I think the part of the bug related to the topology of the split has not been reported to the developers in the RH-31360 Project fails but MeshIntersect works ticket. @dale , could you report it also please? In the automatic process I’m implementing, this part of the problem is as important as the …

Just to comment on the proposed CGAL solution: Finally, I wrote a stand alone applications that would take a .STL and a,b,c,d plane parameters, split the mesh and save the resulting mesh(es) in files. I did not have the time nor the experience to write Python wrapper around the CGAL code. I also …

ProjectCurveToMesh bug on triangle edges

Scripting

brian (Brian Gillespie) July 8, 2020, 12:46am 11

RH-31360 is fixed in the latest WIP

Topic		Replies	Views
Project mesh bug Rhino for Windows python	11	695	July 9, 2018
MeshSplit Bug Example Rhino for Windows	10	2015	February 15, 2016
Project one mesh onto another mesh Grasshopper windows	32	1635	October 8, 2024
Mesh.SplitWithProjectedPolylines Problem Grasshopper Developer windows , mac	8	1129	November 16, 2022
Project to mesh problem Rhino for Windows	1	1207	July 4, 2013

ProjectCurveToMesh bug on triangle edges

Related topics