Rhino BETA Feature: Patch re-implemented

I see that, thanks for reporting the crash. I’ve created this ticket and I’ll get right on it. RH-91626

UPDATE: fixed and this will make it into the next WIP version. Please keep the spancount to 30 or less to prevent the crash. The next version will not allow values of 31 or higher spans.

Advance warning: next week’s WIP version will have an updated Grasshopper component (“Continuous Patch”) that will break existing Grasshopper definitions that used the existing component that was added last year.

You will need to remove the old component from the canvas, add it fresh from the toolbar, and re-connect the wires.

Changes:

  • Moved options around so the order matches the command dialog
  • Added input surface
  • Added UV rotation
  • Added separate U/V spans
  • Added internal tolerance
  • Added boolean/null output for result being in tolerance
  • Stiffness parameter goes from 0-100 (same as the command) instead of 0-1. Note that the old value of zero corresponds to new 100 and the old value of 1 corresponds to new 0.

I expect that this will not change until the release. If you think it should, let me know without delay.

RH-91478 is fixed in Rhino WIP

  1. FilletEdge, ChamferEdge and BlendEdge have double-click to edit too :slight_smile:

  2. Correct. Edit mode is like “interactive history”, and it will reference the original input curves, which only makes sense if the result has not been moved, copied around, transformed etc. The latest WIP version will retain all the relevant information, but you need to pick the input curves of the copied/transformed object again.

There are a couple more objects that accept a double click to edit:
Blocks
Annotations
Details

In WIP a clipping plane can be double-clicked to toggle it on/off

I hope we can add it to more commands eventually.

I didn’t know, I was years old today.
I always used:

Sure, I didn’t have that in my mind.

(german speaking…)
i think most stuff that is obvious should not be translated.
int - in german there is “interne” which fit s nicely. Maybe “innenliegend” would be nicer / more precise, but “inn” is a river passing “Innsbruck”, and having “int” is much more verbose as the “t” is already part of the sound. “int” is already used for intersection ;-(
there is “inner” in englisch as well - one more :+1: for “inn”
Maybe even the analogy to the river fits …

Anyway - my recommendation - and at least all Universities here in Zürich do it - is to use the english interface, stripe of translation glitch and profit from a great community. If there is any struggle google and chatgpt help.

just saying Vierecksneuvermaschung and wonder if their is already a Krautrocksong about it.

it would be nice to have more of this (delayed / optional) “interaction-hints” like we have for gumball. some kind of “inline” documentation.
(double click = edit)
(double click = toggel on/off)
especially if the behaviour is different for different kinds of objects.

Will the internal tolerance be per element?
List of tolerances matching list of inputs?

The internal tolerance is one number that applies to all internal curve and point input.

My reasoning. I asked previously if there was a way in this surface method to give internal points, weights.

I use a mix of internal curves and points, some of which are more precisely driven. Points in my application could be thought of as more open to tolerance variations, weighting.

What are the basic guidelines for using a starting surface with the new patch?

The input edges, curves and points are projected onto the starting surface, so the starting surface should be in the vicinity of the input to allow for a good projection. The projection is needed to find the surface parameter values of the input.
Secondly, the input surface should be degree 3 or higher. Degree 1 surfaces will not give a smooth result.

Thanks. What is the method of projection?

The input edges and curves are sampled at regular intervals and the sample points are projected onto the starting surface with a closest-point projection.

That sounds like what the Rhino command Pull does. The Project command works in a single pre-selected direction, not to the closest points.

Yes it is more similar to Pull than Project.

Perhaps “pull” should be used rather than “project” to avoid confusion.

I’ll check the documentation for the wording, but please read ‘pull’ where I used ‘project’ in the few messages above.