There is possibility under properties/rhino option/general Never repeat these commands:
there are some default commands to not be repeated, some more is nice to add, like '_SetMaximizedViewport Perspective/top/front/right
therefore when you change between viewports and you want to repeat last command f.e. move command, you simply press enter or rightclick.
There are lot of not oftenly used hotkeys I find very handy, like ctrl+alt+s/g/r/w to change between shadow/ghosted/rendered/wireframe view, ctrl+F1/F2/F3/F4 to change between top/fron/right/perspective views
ofc all of those you can change/adjust in properties under keyboard
when you want to zoom with more caution, you can press ctrl+rmb and move your mouse, then you zoom in/out in much smaller steps then when you use scroll wheel
if you use some rendering software (like vray), but you want to show just preview in rendered viewport, you find that reflective materials, like chrome shiny, are not shown properly but only as black color. You can replace this material with simple rhino metal (or custom ofc) material, which is shown properly in rendered view without actual rendering
My original intention was to post the GIF animation here for direct viewing, but the file size seems to be far beyond what the forum would accept for uploading.
I already posted this “hack” in another thread, but it won’t hurt if I repeat it here, too.
Usually, Rhino will not let you extend a 3-sided surface where the 2 side edges share a common control point at the tip. To make it work, simply split the desired edge. This basically fools Rhino that the surface is 4-sided. Then the “Extend surface” command does its magic.
This is very common design mistake in ship hull design. Inexperienced people combine two control points to make a triangular-ish surface. This approach leads to many errors down the line. Incl. extrusion making bowtie looking surfaces or offsetsrf breaking polysurfaces creating gaps.
my (not mine but the one I use ) solution is not splitting one edge, because this in fact may also lead to errors, instead drag one of the two coincident control points and place it on the neighboring edge.
Hi Wim, thanks for the advice! Usually I post newly found bugs in dedicated threads, but I mentioned the issue in the current thread, because I wanted to share a working solution for the lost continuity.
I know what you mean and I too avoid using that fake trick to make a 4-sided surface appear as a 3-sided one. But in my post above I had in mind those cases of creating a 3-sided surface with “Sweep 2 rails” using 3 curves that form a triangle, where all the rows of the control polygon meet to a single, common control point at the tip of the surface.
One “old-timer’s” trick to deal with singularities (edges collapsed to a point) is to select the point and use _Smooth - have “fix boundaries” unchecked, and give it some pretty small tolerance value like your file tolerance. It will “unstick” the collapsed points and create a tiny edge that has the same UV structure as the rest of the surface so that it really is a 4-edged surface. You do need to be careful what actually happens at that edge later, but it can make some things work that didn’t before.
Building a nice G1 or G2 blend surface between two input surfaces that don’t intersect together is very easy by using curves drawn on those surfaces, then building a “Loft surface” between the two curves, followed by “Match surface” with the “CurveNearSurface=On” option. Here is a short turotial:
As Ivelin Peychev already mentioned, sometimes “Blend surface” tends to create an excessive number of control points that in essence are not necessary to achieve the desired result. Also, “Blend surface” may create uneven distribution of control points that causes messy flow and broken reflections.
Another advantage of the “Match surface” technique with aligning to curve on a surface is that you can control the shape of the resulting blend surface. Also, it lets you edit the shape at any time when History is activated, ether by editing the curve (dragging points, dragging the entire curve, changing the degree or number of control points of the curve) or by direct manipulation of the surface control points.
Here is the same set of surfaces, but split with isocurve and connected by “Blend surface” with the default weight of 1 for G2 on both ends. Not only it created more control points, it also has a wrong control point flow that’s easy to notice when turning the Zebra analysis on.
