eobet
September 14, 2020, 3:19pm
9
It’s not a mystery. I’m reluctant to mention other threads and other software, but so many problems that exist in Rhino are solved problems in other software packages (yes, yes, why don’t you use them instead I hear you say… I’m hoping that I could use Rhino all the time, and I’m hoping V7, V8 etc will improve instead of standing still).
I’m just curious because I don’t see the probem.
[bild]
trim.3dm (60.3 KB)
Trimming with 3D curves in a perspective viewport shoud, I’ve been told, automatically pull the curves to the surface, and since these curves are either G2 or overlapping, that should work?
EDIT: I’m trying to trim away the top right corner!
EDIT: I can’t even split the surface with a view based projection, so now I’m even more confused.
The most frequently encountered error for me in Rhino is trim operations done in perspective view, which don’t pull the curves towards the surface for one reason or another. Sometimes it’s really obvious (like when it defaults to the cplane and just destroys the surfaces) but sometimes it’s more difficult to spot.
[image]
The above surface for example, has a closed polycurve that I even separately, manually pulled to the surface, and STILL the trim doesn’t do it properly.
I know commands can…
Yes, I have made trim topics before.
Unfortunately, I still don’t fully understand it…
Is there any indication in Rhino which direction the trim happened in or do you just have to know all the hidden rules about trim direction (like planar curves, etc)?
Am I correct in that Trim always trims to World Z, regardless of the current CPlane Z?
Does being in a ortho view always result in a view based trim?
Does two joined curves always result in a pulled curve before trim (and if so, is it a true n…
[image]
Green rail is able to trim. Red curve is not. Why is that?
trim-fail-again.3dm (470.8 KB)
EDIT: Yes, I’m aware there’s 1000 workarounds for this, btw, I just get failed trims so very often that I want to learn how to get to the bottom of them all.
The Project command has a Direction parameter, can take the current view as a parameter.
But the Trim (and Split) command, surprisingly doesn’t expose this parameter, even though it does implicit projection (through CplaneZ it seems, and other times through normal, which feels a bit uncontrolled).
Is there any way to get Trim (or Split) to expose the Direction parameter?
Alternatively, does anyone have a workaround that doesn’t involve changing the construction plane?
I almost never use orthographic views. I’m not an engineer, I’m a designer, and what I design is very three dimensional. Trimming in ortho views work mostly with flat surfaces, and mine tend to curve a lot.