(WIP) matchSrf Wishes

[Tom_P]

i am hoping for a nice update on _matchSrf in Rhino 9.
my wishes - unsorted:

• a new UI, that is coherent / similar to _fillSrf, _edgecontiuity and others - a list that can be modified until everything is set up correct, skip the old linear UI concept
• multiple _matchSrf should cascade on one surface with history / and or
• a copy option, that allows history for a cascade of multiple _matchSrf for advanced “massage” tequniques
• constraint and lock CVs / better isocurve control
• limit CV-movement by distance
• turn on CurvatureGraph and/or zebra even if _matchSrf is already active (similar to _blendCrv)
• show deviation
• match G2, refine G0 only (meaning the amount of knots insert should only be definded by G0
• refine with maximum number of Cvs / spans

would be nice to see some improvements.
@Rhino_Bulgaria already posted a lot of important
aspects to make this tool up to date.
(maybe post some links / wishes below?)

thanks for some updates on what is planed for RH9

kind regards -tom

[Rhino_Bulgaria (Bobi)]

@Tom_P

• match G2, refine G0 only (meaning the amount of knots insert should only be definded by G0

This is one of the things that always bothers me. I do the following workaround. First, I match with G0 and the “Refine” option, then I delete the History (I keep it active all the time) for that very surface, then I apply another run of “Match surface” either with G1 or G2, but this time without the “Refine” option. If I match directly to G2 with “Refine”, quite often Rhino adds way too many unnecessary control points.

---

As for your request for including links:

Rhino urgently needs these tools!

Currently, Rhino is in something like a NURBS-crisis. Alias made a huge progress in the past 20 years, unlike Rhino’s main NURBS surfacing and control point editing tools that are nearly unchanged since Rhino 2 (with a few minor exceptions). The last few versions of Rhino focused more on non-NURBS stuff, such like tools for Sub-D, 3d meshes, ShrinkWrap etc. While these are nice additions, the NURBS tools are left in the corner. Both, “Blend surface” and “Match surface” lack a huge amount of fun…

Bugs in Rhino 6 + suggestions for the BlendSrf command

Hi there, Currently I’m using Rhino 6 Evaluation and I managed to find several bug in the program that were not present in Rhino 5. 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. This bug is…

[Tom_P]

@Rhino_Bulgaria

workaround

i do the same… annoying workaround.
another option / workaround:
_matchSrf G2 without refine but with history on
optional _pull the edge with history on
_crvdeviation - _insertknot … repeat until G0 is reached … but this feels more like craftsman sculpting a stone then cad defining a proper nurbs surface…

thanks for the links

[Rhino_Bulgaria (Bobi)]

I also do that other workaround, but it often needs undoing and is time consuming to figure out what’s the neat distribution of the newly added spans.

The biggest flaw of the current “Match surface” is the inability to match with G2 by moving the 3rd row of control points in the normal direction only, thus preserving the intended flow of the surface.

Another missing feature is the ability to individually match the start edge and/or end edge to inherit tangency from the target surface’s side edges, especially if they are trimmed.

Individuall matching to U direction or V direction is another missing feature. Currently, the “Match surface” tool has a common option for UV direction that produces ugly and unusable output surfaces.

[Gijs (Gijs de Zwart)]

I’m certainly with you that a non linear workflow is preferred. We are first attempting to Implement this idea into FillSrf, since it is a new command and has no legacy to deal with.