I came here to post 3 things that have been really bugging me in trying to work with SubD, productively. Trying to documents these, I came up with 3 more + a select-though bug in shaded mode. so here they are all.
Can you please give these priority, they are all super basic stuff to work in SubD.
Copy to clipboard selected stuff. No matter what it is.
Please copy and paste this code into Rhino.NextTuesday.Build.
I want to be able to match two bevels, or at least manually be able to un-bevel bevel 2, then query the size of the bevel 1, and redo bevel 2 with that number.
Hi Gustavo - for your CopyPaste item - I assume that what you expect is that selected subobjects, say edges, will be duplicated as plain old top level curves and copied to the clipboard, correct? So that what you have selected to copy to the clipboard and what you paste may be two different and only indirectly related thingsā¦ ? or should it continue to skip objects that canāt be extracted āas isā like mesh faces etc?
@Gustavo - for the BevelPro command - if I understand, you want to be able to tell the command to bevel inside, outside or both, correct?
testMooCow to link two viewports. But as far as I now there is no way to have smooth and box modes in different views.
For the Distance constraint question that is in one of the images or clips, the Distance (nested) command should work but while it seems to do something, it is not quite what I expect - I need to poke at that some more. Hm - there is no distance input in Bevel so I do not see how this can work - there would need to be a base point set and at the moment there is none. Iāll investigate (= ask the developer)
For the Gumball, multiple selection gumballs cannot be remembered, nor can subobjects, in the current state of things- as far as I know that is just how it is for now. I am fairly certain there is a bugtrack item for the thing you point out, but I am not finding it at the moment. Iāll dig some more.
For copy paste of subobjects, what Iāve noticed is:
_Copy does what I intuitively expect and what I think Gustavo is asking for - it copies. _CopyToClipboard ignores subobjects. This applies to SubDs and polysurfaces. With polysurfaces, _CopyToClipboard even returns a message that it ignored subsurfaces if you try to copy them.
_Copy has a weird UX artifact: when the command is in process, it looks like youāre stretching the object by moving the subobjects. Again this is true for both SubD and polysurface subobjects.
Intuitively, the only difference I would want from the UX in terms of what _Copy and _CopyToClipboard do would be that _CopyToClipboard should paste in the original location by default. If it does this with subobjects, I wonder if _ExtractSurface may be redundant. But I always think of these things from the perspective of a brand new user. A newbie who wants to copy a polysurface or SubD subobject is probably going to try ctrl-C first. So it should work when they try it.
About _Bevel: not just _Bevel, but also _Inset should have a command option where if the user preselects or selects multiple faces, they can choose to globally bevel or inset only the perimeter. For face selections that have both an interior hole and a perimeter, choosing a ā_globalā option (or maybe a better name) should bevel or inset on both the hole and perimeter border.
If I select a bunch of polys, then copy>paste, I want to see duplicates of those polys pasted. And stay selected since I then I have to go ahead and move them elsewhere. Otherwise Iāll have stacked polys on top of each other.
Iād normally do that by having the faces filter on, so Iād only be selecting (copying and then pasting) polys.
But if I ctrl+shift marque select an area of a model, like to top of that cube in my video, I guess Iād be selecting polygons+edges+vertices? If I understand Rhinoās logic correctly? ā¦still Iād want to only grab/select/extract/coby the highest ranking subject, in this case just the polys.
On the other hand if I selected a bunch fo edges (from a Surface/Polysurface/SubD-Mesh Face) and only edges then Iād want to paste as curves/polylines.
Right, this is the bit I was wondering about - I get it, just making sure, since the copy(selection)/and the paste will be two completely different things.
If you window-sub-select, I do not see how to avoid getting all levels of things pastedā¦ no way to know what you want.
This already sort of works with _Copy. Select a subD vertex, call _copy, and you find yourself moving a point around with a weird stretch effect. Same with edges. Same with faces. Click again and you paste a copy.
And selecting faces and their vertices and edges and calling _copy only copies the faces.
However, if I select faces and an edge that isnāt part of the faces at the same time, _copy ignores the edge.
So most of what we want from _copytoclipboard is already coded in _copy. It just needs to be ported over.
for flat/coplanar faces yes those three options make sense.
But letās talk the important stuff now that I reeled you in: For non planar ones I want a sliding-style bevel. When means that no faces will ever be at a new angle different of their input faces, like what I did by hand in my green mesh, compared to what Rhino does in the gray mesh
This means that I can super easily modify the bevel amount by sliding those edges, or I can unbevel with a few clicks even if you guys donāt give us an unbevel tool. I can also scale the model and be able to rectify the changes on bevel that the scaling operation did.
Hi Gustavo - weāre on to a different thing though, here, right? Let me pin down the inside-outside thing - like does that make any sense or have any utility other than to fix the alignment case you showed? Would Inset for a group of faces be more appropriate?
