a way of organising modifiers into groups that describe their purpose
Would help to keep organised if you could group modifiers by task.
For example if you have two shrinkwrap modifiers that each affect different vertex groups of the same object, then you could group these into a 'shrink to landscape' modifier group for example. Then these could be collapsed to keep the modifier stack easier to navigate.
Perhaps you could opt to make certain inputs/sliders available at the group top level when collapsed, so you could make the parameters you think you're likely to modify available without expanding and searching through the group.
6 Comments
node based modifiers would be even better, then you could just make a 'modifier group' with inputs and outputs, do branching logic based on masks, etc.
* @testure * definitely, but this would be a welcome stand in, particularly as I suspect node based modifiers are a loooooong way off if ever.
Indeed, node-based modifiers will solve this
Being able to group modifiers of the same type into a expandable/collapsible folder would be very handy for organisation. Agreed.
In the use case you describe, I would simply change the name in the header of each shrinkwrap modifier so it's more clear what each is for. I do this frequently with array modifiers if I have to stack multiple ones (I may call one "x" for x-axis repeats and the other "y" for y-axis repeats).
Maybe you could provide a better example that better uses the grouping mechanism you envision.
* @Jason van Gumster * well this was just a very simple example to keep the description short. I often end up with maybe 50 modifiers to create a single feature on an object (booleans, bevels etc). And then another 50 to create a different feature on the object.
This gets tiring scrolling all the way to the top and back to the bottom repeatedly to tweak value. So it's not so much about the naming convention as the speed of stack navigation.
So perhaps the top level modifier group (visible when collapsed), could house parameters of my choosing from the various modifiers it contains. Or alternatively maybe a quick access dropdown which populates the group view with the parameters of the modifier selected from the dropdown (saves opening up and scrolling 5 metres :) )