Wish SubD edge selection enhancement

Hi guys, with subd modeling we do a lot of edge selecting. While edge loops are useful, sometimes you just want to edit part of an edge loop.

A very useful selection method that I use all the time in T-Splines is the one that follows this workflow.

-Select first edge
-Select second edge with double click
-Software selects the edges in between the first and second selected edges.





Oh nice :+1: so much to discover with the new SubD tools. Thanks for pointing that out to me, appreciate it.

1 Like

This is cool and very useful.

There’s also more that could be done to speed things up.

Top on my list:

-preselecting a face should have the same effect as preselecting it’s edges.
-there should be some way to select only vertices, or only edges, or only faces, to make it easy to prevent accidental selection when working with complex objects. Maybe a set of toggle commands, combined with new Osnap check boxes?

1 Like

what if you set Control polygon pickable from the rhino options, if it works to select a row of control points on a surface by double clicking between points, it should work for subd too. I guess.

Like SelU and SelV?

With regards to selecting only vertices/edges/Faces, that’s already possible with the command “SelectionFilter” and SubD enabled. Check out the screenshot. SelectionFilter with Sub-objects enabled and only edges selected. Even though the control points are showing I cannot select them. Not as discoverable as the heads up display from T-Splines, but useful nonetheless



As @Mark_Landsaat points out, you can easily work with SelectionFilter

An edge ring isn’t the same as the edges of a few single faces, though.

Can that be put in a side panel?

easy and kind of sloooooooow…

Here are some benchmarks for contrast:

  1. Rhino swapping of components benchmark times: We can do 10 laps in 10 seconds. As long as you keep those fingers and eyes super sharp and focus on the task:

  1. Modo swapping of components benchmark times:
    We can do 12 laps, but simply walking the left index finger in the 1-2-3 keys, without even having to reposition the mouse for it, without having to even look:

  1. Rhino in-context swap with a cube:
    now this is a lot of round trips between where in the screen yoru components are and where the selection filter window is. I only got 1 & 1/3 of a lap. Sorry teh mouse cursor is not showing in my video capture. TShi is not slowed down. This is how slow this process is in Rhino, going as fast as I can:

04A. Modo in-context swap with a cube (default to re-select):
here’s an Easter Egg from Modo, when you change component types the last selection you had from that component type is still maintained, you have no idea how amazingly useful that is. Especially consider that most likely your new selection on the same component type will be based on/related/same as your prior selection. here we made 5 & 2/3 of a lap

04B. Modo in-context swap with a cube (looking for new stuff to select):
Even having to force myself to select something other that previous selection in each component type I easy make 4 laps here:

in summary:
Not having dedicated single stroke hot-keys for component mode, and sometimes combinit it to the fact that Rhino does not store previous selections of that component type Rhino is about 67% to 76% slower than Modo in selecting SubD components. And this is just talking about single item selection, not even complex selections such as propagation/in-between/conversion of types and all that stuff.

I always described Tsplis as modeling in SubD with Boxing-gloves. This is why I much rather left Rhino and went to Modo to do fast SubD modeling, even when I did most of my work in Rhino and I owned Tsplines.

Please don’t take this feedback as: “Gustavo is asking us to make Rhino as Modo”. You can probably get similar comparative ‘lapping results’ if you benchmark the selection speed of Rhino with pretty much any SubD solution out there that has been designed for speed.

The vast majority of improvement ahead here are somehow simple and probably a low hanging fruit: add hotkeys for selection filters. Single key shortcuts, not 4-finger stuff.



Yes that’s right, I hope developers think

@gustojunk, I didn’t say it was perfect, I said it was possible. And I agree with you that there’s a lot of room for improvement in the SubD area. But progress is made and I welcome that.

It’s currently a mixed bag for me. Some stuff is better than T-Splines, other stuff not so much. Modo is clearly a very good SubD modeler and I believe the good folks at McNeel should definitely look at Modo as an example of a good SubD modeler.

While the SubD implementation is currently slower than Modo, one thing you get with Rhino is precision that is easy to control. Which is something I found missing from Modo. If we continue to provide feedback we can hope that some of it will be implemented.

At the moment, I’m not sure how much I would use it, but I’m finding that I’m improving quite rapidly. If this is combined with software improvements I could easily see this evolve in something very useful for me.

Time will tell.

1 Like

I totally agree with you Mark, this is why I’m also here spending time in my night-shift to point where things can be made better, and in this case with a relatively low-level of effort: hotkeys = selection filter change! T-splines already proved that single-key shortcuts/hot-keys are possible in Rhino, and they work well.



Single stroke hot keys in general would be great, not just for subd. Clayoo has similar functionality to what you’re showing in Modo. (well, sort of. hot key functionality yes. but otherwise buggy and crashy)

@pascal, is it possible to assign a script for this to an F key to toggle selection modes? I played around with it this morning, but can’t get it to work. (I have zero scripting skills)

I was thinking and tried the following

F5 '_SelectionFilter Sub-objects Vertices
F6 '_SelectionFilter Sub-objects Edges
F7 etc, etc

Let me know if that is an option and what the correct syntax would be.

Hi Mark - something like this:
_-SelectionFilter _SubObjects=_Yes _SetAll _No _Curves=_Yes _Enter

_-SelectionFilter _SubObjects=_No _SetAll _Yes _Enter

to restore normal behavior.
The SetAll=No lets you avoid explicitly setting all but one as No.


Thanks for the quick response, but that doesn’t seem to work on my end. Could be user error, not sure what’s wrong