Rhino WIP Feature: Constraints

[gustojunk (Gustavo Fontana)]

Hi Joshua,

Thanks for your interest on this. Let me please get you up to speed with feedback already provided.

@Joshua_Kennedy

I’m sure you already are but you need to be hammering us with the failing examples so we can fix them. Feel free to ping me directly and I’ll at least make the issue and get it on the right persons list

I used to send a lot of examples, and I’ve seen with a simple search here on those that lack of examples provided by uses here doesn’t seem to be your bottleneck. But please let me know any very specific areas you are thirsty for examples and then, only then, I’ll stop doing billable work and gather those examples for you.

I’m going to ask you the same thing that you guys ask us, your users: Please be specific, provide me descriptions of the types of cases you are interested in, what kind of geometry problem you are trying to solve. Examples of intersections, number of edges, snippets of code, screenshots, etch will be helpful so I can focus only on relevant examples and I do not overcrowd your system with repetitive examples of failures that we have all been sharing here ad nauseam.

---

@Joshua_Kennedy

Can you start a thread about this and go over the gaps in your workflow and what’s too slow?

Are you sure you need more threads on this? Why don’t we start reviewing the top search results from my posts alone on SubD friction and limitations? I think most of this is still unaddressed AFAIK.
From August 1019:

Basic polygon selection is painful, slow, unreliable. Example attached

Hi RMA, The only way that I’m aware I can select individual polygons on a mesh is using SubObject selection. Is this correct? If so, that means I have to constantly be using two fingers pressing shift + CTRL simple to select my work? (do you know how many hours a week a SubD modeler spends just selecting? (if you don’t, you should measure it, it will be humbling and eye-opening) Please take a look a what I’m used to: and now watch me try and fail miserably doing the same in Rhino: …

April 2020:

Wishes for V7 - Sub-D

Great feedback Holo, I’m glad its not just me that finds a lot of friction here. yes! I also mentioned this yesterday on my feedback to Kyle. One more thing needed to not having geometry ‘in your way’ is hiding-subobjects or faces. Like I show here: This makes a lot more sense than making 5 clipping planes to hide parts of my mesh, like I was showing recently too. G

Also April 2020:

Subd and named selections for rapid iteration

Sure, we have shared good selection workflows before, many many times. But here it is again, in case you missed them before. This video is dealing with marquee-click-paint select combined very seamlessly. And combined also with select-though vs. select visible equally seamlessly IMO: Keep in mind the most important part here: It’s all ONE tool you never have to click more than one modifier: either Shift to add or Crtl to remove. you can do click-paint-marquee based on how/where…

From February 2021:

SubD edge selection insanity

hi RMA, I tried do a simple thing in SubD inside Rhino today. Everything takes forever, for many frictiony things already discussed here, but this one is one of the worst crimes: When will this be fixed? It’s nuts! G

From February 2022:

Friction in SubD continues, all so unresolved, so slow, so frustrating

hi RMA team, Today I just wanted to make some quick edits to a SubD bracket model (modeled in Blender) and I’m shocked at how time-consuming and full of errors, oversights, and untested tools the workflow still is (running Version 7 SR14 (7.14.22010.17001, 2022-01-10)) here. Quick stream on mind of all the things that this morning made me shake my head: Bridge only accepts edges, not curves, not polylines (using nurbs curves as input to new SuD geometry is way faster that slapping around cu…

---

@Joshua_Kennedy

What do you want to do with blocks that you can’t?

from December 2022:

Rhino 8 Feature: Block Manager Panel

Hi @lars and team, Great to see this stuff is getting some love. I understand that this is mostly for your architectural customers, but in the name of the small minority here doing industrial design work in Rhino, and working as a team, I’d like to ask a few other things to consider including, that might benefit users in all industries. I numbering them with the g-prefix to avoid confusion with all the previous numbered lists on the thread: g1. date of creation of the block definition g2. dat…

In summary… lack of feedback probably ain’t the problem. Don’t you agree?

Best,

Gustavo