Add the Vertex Crease in the Data Transfer modifier.
Maybe devs forgot to update Data Transfer. (Considering vertex crease is not such an old feature).
I miss this many times, as a simple action of applying a subdivision will erase all creases.
Retrieving edge creases is easy (as option is available), but for vertex creases it's not possible to recover or transfer this data. (Even in Geometry Nodes I can't find a workaround).
Design Proposal:
Note that this modifier is present before the invention of Geometry Nodes and Blender LTS will keep this modifier alive for years ahead, even though the plan is replacing all the modifiers for Geometry Nodes in the future.
So I don't think this could be an excuse to not update the modifier because it will take a long time for pipelines to move full GN-modifier-wise.
5 Comments
A little suggestion/correction on the design could be renaming the buttons:
Vertex Groups to Groups. And the proposed Vertex Crease to only Crease.
This for avoiding redundancy as both are already under the Vertex Data section.
Vertex crease and generally all old hardcoded attributes are becoming generic attributes, so DataTransfer would have to supper them too.
As of now You can* make your own GN data transfer.
*- i havend done anything like that bu i assume its already possible
There is nothing wrong with the Data Transfer modifier besides this missing attribute. GN it not able to read neither write into this data. It’s obscure even from the API.
While I realize the long term goal of the next 2 decades is to deprecate modifiers for geo nodes, but sometimes we don't want to a) completely rebuild all of a modifier or b) wait years for a single field/feature to be added to the existing.
1 - Yeah those are my points. It feels much more closer to just add this missing feature than wait for an unforeseeable time to come. When you need it in a pipeline and you can't even workaround in GN you will miss it. A task that should happen almost instantaneously gonna take minutes or hours of manual clicking and it is very frustrating.
2 - It has been reported and it sounds it could be added: projects.blender.org/blender/blender/issues/117535
3 - If someone here is familiar with C/C++ and Blender we could try submitting a patch. I suggest we investigate how it is coded for Vertex Data > Bevel Weight and adapt it to a new button for Vertex Weight as the logic might be very similar as both are dealing with a very similar context and kind of data.