Click a location on each surface edge to add another shape curve. Here we go. Selecting a curve or surface edge automatically selects all curve segments connected with the level of continuity set by the ChainContinuity option. I also have a few suggestions for the BlendSrf command: Is it possible to add a “Relax shape” option whose purpose is to smooth out the middle rows of the blend surface, without affecting the height of the surface at both both ends? I have 3d Connexion SpacePilot (the old discontinued model, not the more recent “SpacePilot Pro” one) that works flawlessly in Rhino 5, but in Rhino 6 I noticed that 3d Connexion’s automatic rotation center no longer can “see” through solids and surfaces that were given a custom “wireframe” viewport setting through the “SetObjectDisplayMode” command. Optionally, this may add an additional row of control points across the middle of the blend surface so that its both ends remain unaffected by the curve rail. Hole larger than surface (right). This also happens if I delete the Blend surface and try to build a new one. In my above example I drew curves directly on the target surface with “Interpolate curve on surface”. Ability to divide the blend surface (while still into its creation phase) into a number of sections, where the user is able to set a different, individual continuity setting to each section. And makes an approximation between both U and V directions? I also noticed another bug. *Only showed in my second image. Make sure there is enough room for the blend surface to trim and join with adjacent surfaces. If the edge is untrimmed, the shapes are parallel to the surface isocurves. Not active (rendered as unpickable grey text) if “Position” or “Tangency” is selected. Rhino v6 is shipping now with the great features of Rhino v5 for Windows plus the following: For more SimplyRhino videos and tutorials, check out their YouTube Channel here. Here is a visualization of my idea. Just wanted to express my support for all the above mentioned points and suggestions by @Rhino_Bulgaria especially regarding edge alignment of hblend surface handles. Then I built a lofted surface between both curves. However, to go around this limitation, there is still a possibility to pick either an extracted isocurve or a projected curve on the target surface. The following case is just one example of that. No matter how many times I save the toolbar settings, the “Osnap” toolbar is always missing and probably this error is caused by the presence of other toolbars at the bottom. Surface Matching with History; Sweep & Blend Surface with History; And much more! Another helpful thing for the “Match surface” command is to have a secondary, smart auto-chain option that will limit the latter to only those edges that sit adjacent to the surface that’s being matched. If I use the BlendSrf command with the “Interior shapes” option off, sometimes the resulting blend surface will lack proper G2 continuity. If there are additionally added shapes with the “Add Shapes” button, they will follow the same rules. Sets the continuity for each surface end. This surface can be smooth, continuing the curvature of both objects, or it can be straight – depending on blending parameters. Check the picture with the Zebra stripes. Remove any edges you can prior to blending with. This never happened in Rhino 5 where the continuity was perfect at all times. The BlendSrf command creates a blend surface between two surfaces. That will completely resolve the issue with randomly shaped blend surfaces that require extensive work to be fixed afterwards. Several days ago in another topic you posted an image showing one improvement for “Blend surface” in Rhino 7 WIP that build a simplified surface. Sometimes some holes appear in rendering between blend surfaces and their original surfaces appear in rendering. Usually I place the Osnap toolbar at the bottom and then place several tabs with other toolbars on top of it. However, “Blend surface” was unable to obtain the same number of control points as the input surfaces, ultimately adding extra control point rows. NVIDIA Quadro Card Tests with Rhino 6 WIP. Here is an image to explain that visually. Looking at VSR shape modeling would not hurt, in fact, developers should be inspired and take it as a model. But aren’t you glossing over the fact that you need to trim (at least in the above example) in order to loft and match, and thus end up with the complexity problem again? This will basically turn it onto a “Sweep 3 rail” command.”. “Reset handles”. Example 3 shows how my proposed limited auto chain could work, by offering to match the surface only to those edges (and/or curves) that are close to the surface we match. This will basically turn it onto a “Sweep 3 rail” command. Hole the same size as surface. When Continuity = Tangent or Curvature, allows you to blend a curve to a surface edge perpendicular to the surface with continuity.. AtAngle. However, if I rebuild the 2nd surface, the blend surface will no longer have its history enabled. Problems with this page? Depending on the shape of the model, this may lead to frustration, especially without a 3d mouse for camera navigation. This will save a lot of time when a blend surface is constructed along multiple surfaces (or a match surface is run to match a surface to multiple edges/curves) and for some reason the modeler must redo the command. This way, I avoided splitting the surfaces there (check my 3d model where the surfaces remain uncut). There are no limits on complexity, degree, or size. By default the shape curves are perpendicular to the surface edge or parallel to the surface isocurves. Being able to divide the “Blend surface” into custom number of segments greatly increases the ability to manually adjust its shape via control point manipulation, prior applying “Match surface”. Selects curves in the negative curve direction. Selects surface edges that are touching the selected curve. Sometimes I match a surface to more than 50 edges together and my intent is to match to, say, only 17 of these, while the remaining 33 edges I have to deselect manually. Rhino can create, edit, analyze, and translate NURBS curves, surfaces, and solids in Windows. Matches the blend surface either to the U or V direction of the target surface, as I explained this in my previous post. “Match target isocurve U direction” and “Match target isocurve V direction”. Hopefully it’s easier to understand now. I see that many people already requested edge align of the “Blend surface” handles years ago. You can change the continuity setting or just click on the current ones. When Continuity is set to Tangency, if the angle between two edges/curves is less than this value, the chain selection will consider the criteria for continuity met and will select the next segment. Surface generation and editing should always be the priority for Rhino, in every possible tool. It exists only in the command line, so if people don’t pay close attention to see it on time (after picking the surface edge to be matched), they end up missing the chance and using “Match surface” with the default settings that accept only surface edges (for G0, G1 or G2) and curves (for G0) as an input. ===================================================. This is somewhat implemented in the Patch command and I find it quite useful. Note: When you snap to a point and add a shape, the command automatically creates a shape that connects to the corresponding point on the other side, which attempts to keep the blend simple. Also, many people want to build a Blend surface that’s at 90-degree angle towards the target surface, so this is a quick way to do that and avoid using the “Fin” tool to extract a curve and build extruded surface normal to the target one. Rhino 7, is that you? Perpendicular. The padlocks are moved to the left side of the boxes for a more logical appearance. The “Same high” option works in a different way, trying to equate the height of the surface. Being able to control the draft angle is especially useful when working with products that will be manufactured by injection moulding or by using fibreglass moulds. Always blend from the largest radius to the smallest radius across a model. Selects curves in the positive curve direction. Example number 2 shows how it looks when the handles were further modified. Lock sliders icon (1), surface end bulge controls (2). Hold Alt while dragging the handles to change the angle between the shape curve and the surface edge. (quote) “An option “Use guide rail” would help a lot, if we were able to pick a spline that the BlendSfr command could use as a guide for its middle body. Another proposition for a vast improvement of the Blend surface is to have an option to influence the control handles by the adjacent edge direction with one of the following settings: b) Match target surface isocurve direction. Rhino 6’s “Blend surface” creates an excessive number of control points that are not necessary most of the time. If the edges of two surfaces you are trying to blend share a corner intersection, the. Note that the two input surface at the left side were cut by isocurve, exposing a very clean edge to work with. Then it will automatically have 10 rows of control sections (shapes), which is very disturbing, because that will not allow me to have a more smooth control over the shape of the blend surface. No Software Rental. Command-line options. The UVN command is too limited and slow in these situations. This is because the rendering was done with polygon mesh approximations of the true surfaces, so the meshes are not matching up exactly. For me, this is a game changer in Rhino 5 and being unable to use it properly in Rhino 6 prevents me from buying the program at this moment. Rhino also supports polygon meshes. As far as I know, Rhino’s existing Blend surface tool does not offer this functionality. This is where even Match surface’s “Match target isocurve direction” was unable to properly “read” the actual isocurve direction of the adjacent surface: Hi Bobi - it looks to me like MatchSrf is doing too good a job, if anything , in matching the iscurve directions here - since the trimmed edge cuts arbitrarily across the U&V directions, each can end up being potential target depending where along the edge you ask. It’s a bit funny that “Match surface” only requires 4 control points along the blend edge to achieve G2 continuity (using the same input surfaces split by isocurve), while “Blend surface” requires 6. Rhino 6’s “Blend surface” creates an excessive number of control points that are not necessary most of the time. It resets the original position, angle and size of the handles.