Is it possible to change side surface angle like this in Rhino?

Rhino Rhino for Windows
,
1

Is it possible to change side surface angle like this in Rhino?

https://doc.plasticity.xyz/solid/draft-face.en

I would like to maintain G1 between side surfaces during that process.

1 Like
2

You can use the MoveEdge command and move the bottom edge, but you need to have a (closed) polysurface.

2 Likes
3

I will try it. Thanks. It would be nice to have an angle there to put the exact value but I will create some guide curve for that.

1 Like
4

Hello- in simple cases you can Shear the side face to a particular angle - this will not, however, do the automatic resolving of intersections with other faces - this is something that V8’s PushPull could probably be persuaded to do, but it seems with non planar faces or more complicated arrangements things could get tricky pretty fast.
@Joshua_Kennedy - something to think about, perhaps.

-Pascal

1 Like
5

Unfortunately MoveEdge is not a solution on not straight edges (complex curves/edges).

image
image697×374 14.5 KB

I need those tapered sides for moulding. I need to be sure that most of angles are higher then some factory minimal value. Move edge do not have same offset value on all surfaces and it’s dangerous for use in moulding (my case). It`s hard to see those differences on complex shapes.

6

My I ask you politely to ask developers if they could do ExtrudeCrvTapered with a G1 product from G1 curves? I think more people would be happy from that. Tapering is very popular in moulding, carbon parts creation etc. Now G1 curves creates G0 surfaces and there is a massive work to fix that manually…

Thanks in advance.

1 Like
7

Please upload an example of such curves, the surfaces from whom they were derived, the target taper angle, and the pull direction.

1 Like
8

I think what he means by G0 surfaces is surfaces with a million fully multiple knots.
If you take any simple well-behaved single span spline curve and use it as input for ExtrudeCrvTapered the result will be a surface with a gazillion control points and all the surfaces knot spans will be fully multiple. Users have been complaining about this for 25 years.
There are lots of ways to work around the mess that ExtrudeCrvTapered produces.
The users are always expected to be more competent than the developers. The users can fix the mess but the developers can’t.

ExtrudeCrvTapered typically produces a good result if the input curves are tangent lines and arcs. For any other input it usually produces a mess.

1 Like
9
  1. yes I would need nide single span surfaces from a single span curves
  2. you are right that ExtrudeCrvTapered produces G1. My bad. I messsed SBD script product (spb_TaperFromPathOnVerticalFrames.py) and original Rhino command. But I’ve meant that is not usable in real life after that. v7 produces single multi span long surface which could be converted to single span only in v8. V8 produces single span surfaces but much more than needed. As you noticed you will get many small thin surfaces. Much more than you would need (even from G1 curve). Best is when I try to do fillet over that. Checking if long curve is G1 also is problematic. I use tapering script from
    3)Daily I use @sbp script: spb_TaperFromPathOnVerticalFrames.py which produces nicer result from extrudeCrvTapered but product is not fully G1. So I messed up two problems.
    I will prepare example case in near future but for now I work over NDA files and I can`t show it.

But best in both worlds would be having clean single snap output like in Steven (SBP) script but with G1 like current ExtrudeCrvTapered command.

I slept today few hours sorry for messing things up.