Vertex groups created with Geometry Nodes are not processed by subsequent modifiers #100042

New Issue

Stephan Kellermayr · 2022-07-28T13:15:32+02:00

2022-07-28 13:15:32 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691
Worked: (newest version of Blender that worked as expected)

Short description of error
Vertex groups created with Geometry Nodes are not processed by subsequent modifiers

Exact steps for others to reproduce the error
Suppose I have a cube where some vertices are assigned to a vertex group. If I then apply a bevel modifier and select this vertex group, the edges are rounded correctly.

If I then create further geometry with Geometry Nodes before the bevel modifier and also assign some vertices to this vertex group there, these are also rounded correctly.

However, if I do not include the original mesh in the Group Output, but only output the geometry created in Geometry Nodes, the vertex group is no longer processed correctly by the subsequent bevel modifier.

It then looks like this vertex group does not exist at all.

More details can be found here: https://blender.stackexchange.com/a/270569/145249

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: `e05e1e3691` Worked: (newest version of Blender that worked as expected) **Short description of error** Vertex groups created with *Geometry Nodes* are not processed by subsequent modifiers **Exact steps for others to reproduce the error** Suppose I have a cube where some vertices are assigned to a vertex group. If I then apply a bevel modifier and select this vertex group, the edges are rounded correctly. If I then create further geometry with *Geometry Nodes* before the bevel modifier and also assign some vertices to this vertex group there, these are also rounded correctly. However, if I do not include the original mesh in the *Group Output*, but only output the geometry created in *Geometry Nodes*, the vertex group is no longer processed correctly by the subsequent bevel modifier. It then looks like this vertex group does not exist at all. More details can be found here: https://blender.stackexchange.com/a/270569/145249

Stephan Kellermayr commented

2022-07-28 13:15:32 +02:00

Added subscriber: @Stephan-Kellermayr

blender-admin commented

2022-07-28 13:15:32 +02:00

#101364 was marked as duplicate of this issue

blender-admin commented

2022-07-28 13:15:32 +02:00

#100186 was marked as duplicate of this issue

Jeran commented

2022-07-28 13:23:50 +02:00

Added subscriber: @TheJeran

Pratik Borhade commented

2022-07-28 14:28:56 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-07-28 14:28:56 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Pratik Borhade commented

2022-07-28 14:28:56 +02:00

Thanks for the report. Could you share your .blend file so that we both will has same reference?

Jeran commented

2022-07-28 14:55:23 +02:00

Here's a good example. Half of the instances here should be beveled, however, all of them are.

beveltest.blend

Here's a good example. Half of the instances here should be beveled, however, all of them are. [beveltest.blend](https://archive.blender.org/developer/F13324067/beveltest.blend)

Pratik Borhade commented

2022-07-28 15:59:10 +02:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Pratik Borhade commented

2022-07-28 15:59:10 +02:00

Thanks for the file. I think behavior in your file is expected.
vertex groups are part of the mesh data. In you example, vertex groups exists for original cube only and not for the meshes generated from the Cube and Grid node.
With that setup you're not updating the vertex group but basically creating a new boolean attribute.
Also- Creating vertex groups for the default mesh nodes is not possible I guess.
I think we can archive this report but I'll forward this report to developers for the final check

Thanks for the file. I think behavior in your file is expected. vertex groups are part of the mesh data. In you example, vertex groups exists for original cube only and not for the meshes generated from the `Cube` and `Grid` node. With that setup you're not updating the vertex group but basically creating a new boolean attribute. Also- Creating vertex groups for the default mesh nodes is not possible I guess. I think we can archive this report but I'll forward this report to developers for the final check

Stephan Kellermayr commented

2022-07-28 17:03:27 +02:00

Here is another example: https://blend-exchange.com/b/e6SbvWop/

The strange thing about this is that apparently this "bug" only comes into play when the mesh is not closed. In the example I show two different approaches. One of them does not work, but the other one does.

Here is another example: https://blend-exchange.com/b/e6SbvWop/ The strange thing about this is that apparently this "bug" only comes into play when the mesh is not closed. In the example I show two different approaches. One of them does not work, but the other one does.

Stephan Kellermayr commented

2022-07-28 17:11:21 +02:00

In #100042#1396611, @PratikPB2123 wrote:
Thanks for the file. I think behavior in your file is expected.
vertex groups are part of the mesh data. In you example, vertex groups exists for original cube only and not for the meshes generated from the Cube and Grid node.
With that setup you're not updating the vertex group but basically creating a new boolean attribute.
Also- Creating vertex groups for the default mesh nodes is not possible I guess.
I think we can archive this report but I'll forward this report to developers for the final check

No, I would not see it that way. It works ...sort of or partially and the behavior is misleading. I have tested this extensively, and it does indeed work if the original geometry is hooked in with Join Geometry before the geometry created in GN.

It may well be that the attribute was not there before if the original geometry is not included, and I also realize that a vertex group cannot actually be created in GN. But an existing group can be "added" to.

And the funniest thing is: If I extrude a surface with GN, I can change it afterwards with a Bevel Modifier, although the original geometry was not transferred. All in all there is a bug in there somewhere, because the result is not conclusive.

Please take a look at https://blend-exchange.com/b/e6SbvWop/ and see for yourself.

> In #100042#1396611, @PratikPB2123 wrote: > Thanks for the file. I think behavior in your file is expected. > vertex groups are part of the mesh data. In you example, vertex groups exists for original cube only and not for the meshes generated from the `Cube` and `Grid` node. > With that setup you're not updating the vertex group but basically creating a new boolean attribute. > Also- Creating vertex groups for the default mesh nodes is not possible I guess. > I think we can archive this report but I'll forward this report to developers for the final check No, I would not see it that way. It works ...sort of or partially and the behavior is misleading. I have tested this extensively, and it does indeed work if the original geometry is hooked in with *Join Geometry* before the geometry created in GN. It may well be that the attribute was not there before if the original geometry is not included, and I also realize that a vertex group cannot actually be created in GN. But an existing group can be "added" to. And the funniest thing is: If I extrude a surface with GN, I can change it afterwards with a Bevel Modifier, although the original geometry was not transferred. All in all there is a bug in there somewhere, because the result is not conclusive. Please take a look at https://blend-exchange.com/b/e6SbvWop/ and see for yourself.

Hans Goudey commented

2022-07-28 18:42:55 +02:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2022-07-28 18:42:55 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Archived'

Hans Goudey closed this issue

2022-07-28 18:42:55 +02:00

Hans Goudey commented

2022-07-28 18:42:55 +02:00

The result is indeed a bit confusing, but @PratikPB2123's analysis is also correct.
The issue is that the modifiers don't know how to read the generic attributes created by geometry nodes. Nodes that create a new geometry internally will make vertex group into generic attributes.
The way we're planning to fix this is by implementing these modifiers as geometry nodes. There is already work underway for a new bevel implementation as a node.
That's just a regular development task though, so I will archive this report. Thanks though.

The result is indeed a bit confusing, but @PratikPB2123's analysis is also correct. The issue is that the modifiers don't know how to read the generic attributes created by geometry nodes. Nodes that create a new geometry internally will make vertex group into generic attributes. The way we're planning to fix this is by implementing these modifiers as geometry nodes. There is already work underway for a new bevel implementation as a node. That's just a regular development task though, so I will archive this report. Thanks though.

Stephan Kellermayr commented

2022-07-28 18:49:23 +02:00

OK, I see, then this is a bug, but it won't be fixed because the causing mechanism will be replaced by another mechanism soon anyway?

Hans Goudey commented

2022-07-28 18:57:42 +02:00

Getting really technical, the definition of a bug is something we expect to work but doesn't, so technically this isn't a bug, but it does seem like one.
But yeah, that's basically it.

Getting really technical, the definition of a bug is something we expect to work but doesn't, so technically this isn't a bug, but it does seem like one. But yeah, that's basically it.

Stephan Kellermayr commented

2022-07-28 19:59:43 +02:00

OK, then let's agree on an "incomplete feature" that causes a lot of confusion ;-)

Thanks anyway, I'm looking forward to the Bevel node!

OK, then let's agree on an "incomplete feature" that causes a lot of confusion ;-) Thanks anyway, I'm looking forward to the Bevel node!

Hans Goudey commented

2022-08-04 00:15:45 +02:00

Added subscriber: @SergeL

Omar Emara commented

2022-09-26 22:59:06 +02:00

Added subscriber: @pseudoua

Yaniv Gershoni commented

2023-07-02 12:00:45 +02:00

Hi,
I tried the file: https://blend-exchange.com/b/e6SbvWop/
and got this:

Blender 4.0.0 Alpha :

It seems like it's not working anymore.

Hi, I tried the file: [https://blend-exchange.com/b/e6SbvWop/](https://blend-exchange.com/b/e6SbvWop/) and got this: ![image](/attachments/e147703a-af32-4c7e-a147-73525fc7ca7f) Blender 4.0.0 Alpha : ![image](/attachments/a419824b-dbd0-4ff7-b486-90198145282c) It seems like it's not working anymore.

image.png

752 KiB

image.png

5.6 KiB

Yaniv Gershoni commented

2023-07-06 12:00:14 +02:00

I found a way to do it and even change the Bevel Weight Edge, all you have to do is use the Store Named Attribute node as the last node and with the Selection choose what you want to get the effect when the selection is made earlier.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Vertex groups created with Geometry Nodes are not processed by subsequent modifiers #100042