Missing Face Set Operators #92944
This task is a todo list for missing face set operators. - [x] means operator works on either a user-picked face set or all of them. A single arrow means conversion operator in one direction already exist (so, Mask to Face Set already exists).
- Face Set-
- Face Set-
- Face Set-
- Face Set-
- Make Disconnected Face Sets Unique
- Separate By Face Sets
- Face Set-
- Face Maps
Changed status from 'Needs Triage' to: 'Confirmed'
Vertex colors to face sets: so we can use colors of the existing color paint to mask in a very advance way.
Face sets from different density topology areas. And the a way to populate with a especific topological density a face set.
I think before spending a lot more dev time on face
sets maps, it would be nice to have a design as to their purpose. As far as I understand their current implementation, they can only be used by addons, and those addons could very well just interpret vertex groups as face sets maps by inspecting the topology. The difference between face maps and face sets is even more esoteric.
Also, I think (hope) all of these things will be refactored during the Attribute Edit phase of the Geometry Nodes project, but I could be wrong. But definitely something to double check before you burn a lot of time into this.
In #92944#1251021, @Mets wrote:
I think before spending a lot more dev time on face sets, it would be nice to have a design as to their purpose. As far as I understand their current implementation, they can only be used by addons, and those addons could very well just interpret vertex groups as face sets by inspecting the topology. The different between face maps and face sets is even more esoteric.
Face sets are highly used in sculpt mode, it is an essential tool, every 3d sculptor can say that to you. That is why Joseph want them to be as a complete tool as it can be.
Sorry, I meant face maps, whose existence is so confusing that I still can't get it right.
So my comment only pertains to
2 Face Set- [x] <-> Face Maps
8 Face Maps <-> Face Sets
Not sure if this can be closed. Most of these can be achieved with exisiting operators or geometry nodes.
Some are not even needed since the Face Sets attribute can now be directly accessed.
I saw some users trying to implement some of these with combinations of geometry nodes and scripts on BlenderArtists. It's way too much work.
Just to be clear though. From that list many wouldn't be needed.
- The primary use case of Vertex Group conversion is to use them for modifiers. In that case, Geometry Nodes offers more options, including using the Face Sets directly, right?
- Face Maps are essentially depricated and are a generic attribute now. So that's geometry nodes territory.
- UV Seams and UV maps should be handled by #109773
- Face Sets can already be filled with a Mask with Expand. No extra operator needed there.
- "Make Disconnected Face Sets Unique" is already implemented with "Initialize by Face Set Boundaries"
- I don't know of the use case of converting Face Sets to Material Slots. Would be good to get some info there.
Geometry Nodes offers more options, including using the Face Sets directly, right?
Geometry nodes can't use the
.sculpt_face_set attribute directly (except the future node group operators, not the modifier). So we should have an operator to copy face set values to an face domain integer attribute (that could also be a node group operator, depending on the timeline).
What could be really useful then is to have operators to
- save masks and face sets as named attributes
- create masks and face sets from named attributes
This back and forth conversion can offer options for quick use with geometry nodes as well as the ability to store mask and face sets for later use.
For example, the use of "initialize face sets by uv seams" is done because it's a convenient way to store face sets atm. If face sets could just be saved directly, that could be a better way.
The use cases for converting face sets to material slot and vertex groups are not clear to me atm.
The purpose of converting to material slots is to interface with remesher addons, I imagine addon authors will eventually update them to read face set data directly.
One thing we could do is just make face sets a normal attribute. Almost all of the
.sculpt_XXX attributes are temporary ones. We could make all non-temporary sculpt attributes public, so
.sculpt_face_set could become
paint_face_set or something (remember we want to eventually support face sets in all paint modes). We could do something similar for the persistent base attributes (e.g.
.sculpt_persistent_co could be
sculpt_persistent_co or something). I dunno.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?