i am using projected curves on an object how can it fail?
the only thing i can think it doesnt handle converted mesh files. ive tried converting in modo to rhino. importing an obj and converting to rhino via tsplines and it always fail
1 Like
Please upload the geometry here, somebody will take a look.
Are you sure the curve is at least as long as the geometry in the current CPlane?
A curve must be on a surface to split a surface using Split. This is different than the Trim command which will use the projection of a curve onto a surface.
The curve must also be continuous, and begin and end at surface edges.
i extended the lines outside just so i can select them easier. it might possibly be an issue splitting polysurfaces especially when converted from a mesh object
Just for the record, this is not the case… Split will also Project or Pull a curve onto a surface following the same rules as Trim (on surfaces)
"When trimming a surface with a curve in a plan parallel view like the default Top, Front, and Right view, the cutting curve is projected on the surface in the view direction.
When trimming a surface with a planar curve in an angled parallel or a perspective view like the default Perspective view, the cutting curve is projected on the surface in a direction perpendicular to the curve plane.
When trimming a surface with a 3-D curve in an angled parallel or a perspective view, the cutting curve is pulled on the surface by closest points."
-Pascal
2 Likes
@pascal Thanks for the correction.
1 Like
A solution in many of these cases (i have found) is to use the “Rebuild edges” function on the thing you want to split. In my cases it did not affect the curve but the split function worked perfectly after i did it.
Best regards.
I had some luck copying the object and trying the split on that one.
Estimated collegues Rhino sometimes fails miserably in finding the interections between surfaces, in truly simple geometries I have been using Rhino for over a decade now and I do not have the smallest doubt about it, the developers team for sure have known this for a long time
Nope. Without you posting a file with a problem that we can reproduce, there’s nothing for us to fix.
you need the rhino file I suppose instead of just a picture
I have encountered the issue some times, it does not happen always off course, but it refuses to trim the pink sf or to find the intersection between the two surfaces
1 Like
this is the file which contains the two surfaces which Rhino fails to intersect
rhino fail intersect example.3dm (1.2 MB)
If the developers team wanted a good example here you have one
Hi,
I see this issue in Rhino 5. It works as it should in the latest Rhino 6 that I’m running.
1 Like
Unfortunately, not all customers can afford to change to the newest version of Rhino everytime a new one is released, I can understand the difficulties involved in making such a wonderful piece of software, but having said that … the Euros I paid for the Rhino 5 … all and everyone of them worked flawlessly …
It’s not that they are released all that often… Been 6 years since V5 came out. Jus sayin’…
1K/6 years = 167 bucks or 194 Euros or so a year. Gotta be one of the best deals going.
Regards,
Terry.
Nope, 0.5K/6 years (upgrade price)… 83$/€ per year…