check out this short video about how to use named selections with subd models to create super fast variations-
here is the model to play with bike frame_named selections.3dm (154.6 KB)
Ctrl+ click the faces you want to deselect with the face selection filter active.
One at a time? Easy in this case that you have 3-5 faces sure, but a non starter when you have 15+
I think we need a quick way to unselect subobjects from existing selection, just like we have with objects. If there’s a way I’m completely missing it.
I was about to start a conversation about that. Is there a way to window deselect sub-objects?
I see it useful in SubD and I really need it also in other cases.
Cleaning some meshes of 3d scanned data is a good case for this - for example selecting a bush and deleting it. When I window select a bunch of mesh faces, most of the time I select e.g. 15 faces too much on one side and I want to window unselect them.
but I am also interested in deselecting borders, points and specific faces and it seems that all the selection is canceled, this seems to be an error
I recall some discussion of having a ‘single key’ (not Ctrl+Alt+Windows+mother’s maiden name+name of your first pet…) approach to swap immediately between vertex/edge/face/mesh mode. Similar to Modo’s 1-2-3-4 keys on the keyboard. I think T-splines has this too? Every other SubD modeling software has it. I can’t imagine a decent workflow without this, for as long as this level of manual sub object selection is still needed.
Is something like this already working in V7? Or in the works for development?
You can alias all the selection filters and assign them any key you want.
Mine are verts =vv
You could just as easily assign them to 1234- asdf or whatever you want.
That work for you?
Aliases require and ‘enter’ or ‘space are after you press the alias key, correct? If that’s the case is not working for me, at all. I need a single stroke. I’ll test it tomorrow. Also I have no idea what to put to each filter, with some trial and error I could figure it out. But there’s currently no easy way to share any toolbars with my team since we are using WIP builds that need toolbar resets, but that’s a whole different can of worms.
We need what the rest of the industry is doing: have the development team do the work for this. Not us the users.
Another option for now [until this is done by the Mcneel team] is if you use a device like a multi button mouse, [a 3DConnestion variety, a Wacom, or another device that has several configurable buttons.]
Assign an acrobatic keystroke combination that for sure won’t be used directly. for example. I set : Command+Option+Control+Shift+E as Edge Filter to an intuos button. and then it is just one click.
Thanks Akash for pointing out the absolute UX failure that’s the current disregard and deprioritization of basic SubD workflows.
I don’t use obscure hardware, except for my 17” Precision laptop. And that’s hard enough to make it portable. No interest in Wacom or 3D connections products. They will only slow me down, and are not portable.
I just one 1-key shortcuts. I expect McNeel to provide a solution. Ideally really soon. It’s time.
Use the keyboard shortcuts instead of aliases. they work without the enter. Especially the f keys. I reassigned my f9 thru 12 to selection filters… >>poof<< one key and done.
Hi Kyle, maybe not intentionally, but what you are saying is misleadingly incorrect.
So let me please clarify for you and everyone else:
’especially’, is the key word here. Since the only single key options to map to keyboard are:
- Function Keys (F1 through F12, and all those have very useful assignment already)
- Home key
- End key
- Tab key
So, we do not have a way to assign selection filters to keys like 1-2-3-4-5 or transform shortcuts to keys like q-w-e-r-t.
This is a major limitation. It need to be resolved IMO.
that’s fair and you are correct only f keys are accessible unless you have a fancy keyboard or mouse with programmable buttons.
Sadly that is a hard limitation of the current rhinosphere. Because we are command based, everything we do has to be scriptable, otherwise it can’t be accessed in GH or by 3rd party plugins. If we deviate from that we break alllll sorts of stuff for people who rely on it.
The best we could offer is aliases with a single key and a right click mouse to enter.
tab is currently used to toggle between box/smoth mode
I’d I’d push back and say not all the f keys have useful assignments. Or at least not as useful as selection filters for me.
transform is done via gumball all in one shot, so I’d argue the 1234 keys for transforms are obsolete.
WHY? There must be something in Rhino that fundamentally breaks when you do single key input? Otherwise it does not make sense this level of coordinated avoidance for this request.
Is this a technical limitation?
A support problem? (someone hit 1 when focus was on viewport, they meant to type one somewhere and now they turned on vertex selection filter)
How come Tsplines could do it without any problems? (or at least no problems that I can recall)
I made a _GumbalwaysOnMyWay video to show you why for old people like me, the ‘obsolete’ is still the better way to work. I look forward to work with something better. Not seeing it here, not even close.
tried paint selections for stuff like that? 2 seconds of swiping vs, loooots of clicking…
also has a select thru yes/ no option to avoid the back faces being picked.
(ps… im older than you are… can’t claim that as an excuse yet…)
also, do you have an example where this is done better elsewhere? I’m genuinely curious as to what we are measuring by.
This is as far as I know basically a binary question/solution. As Rhino is command line based, any keyboard input - even one letter - might be the start of a typed command or option. If that is a given, then one letter/number key hot keys are just out - it’s not possible to interpret the keyboard input any other way.
So, as I said, the solution is binary - you either have the use of the command line… or you don’t. There could be for example a function tied to a hotkey to divert the command line’s reception of keystrokes from the keyboard. In that mode, single keys could then be programmed to toggle pick modes, selection filters etc.
The downside of this is that you would still need to continuously toggle back and forth between command line keyboard input and hotkey input modes. If you always launch your commands via icons or the menu and never type anything on the command line, this would be fine I guess.
That was IIRC how the T-Splines hotkey mode worked… maybe I’m wrong about that though.
It sounds like you have the right knows somethere deep in the code, to do better selection but I, a user, and one that it’s quite a bit familiar with Rhino, have no idea where that stuff is.
This is all I can get to when trying paint selection:
No idea where select-though setting is.