Vertex weight not carried through bevel modifier #105012

Open
opened 2023-02-21 11:07:22 +01:00 by Dimitar P. · 12 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080 4.5.0 NVIDIA 528.24

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
Worked: (newest version of Blender that worked as expected)

Short description of error
Vertex weight not carried through bevel modifier in some cases

Exact steps for others to reproduce the error

105012.blend

  • open blend
  • apply visual geometry on the good object
    image
  • apply visual geometry on the bad object
    image

OK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well [which is posted below]):

  • open the file
  • go into editmode on the bad object
  • select all edges (edge select mode)
  • Mesh > Sort Elements > e.g. Cursor Distance
  • voila!

Original report

Short description of error
When wishing to create a bevel with the modifier on a specific vertex group aftern another Bevel modifier, the vertex group does not carry over.

Exact steps for others to reproduce the error

  • Create a geometry
  • Mark some edges to bevel with bevel weight set to 1
  • Add an edge loop in to a vertex group
  • Add a bevel modifier and use Weight
  • Add 2nd bevel modifier and use vertex group. The area where the first Bevel modifier has been executed does not become incorporated into the vertex group

image

image
image
image
image

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4080 4.5.0 NVIDIA 528.24 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `rB55485cb379f7` Worked: (newest version of Blender that worked as expected) **Short description of error** Vertex weight not carried through bevel modifier in some cases **Exact steps for others to reproduce the error** [105012.blend](/attachments/60dcdbfe-4ea5-4cc8-937d-256e9a8cd57e) - open blend - apply visual geometry on the `good` object ![image](/attachments/92a80946-4f47-4379-a8cd-634c9a8b12be) - apply visual geometry on the `bad` object ![image](/attachments/d0c8bd51-9232-40cf-a86f-3304e86550cd) OK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well [which is posted below]): - open the file - go into editmode on the `bad` object - select all **edges** (edge select mode) - `Mesh` > `Sort Elements` > e.g. `Cursor Distance` - voila! ----- **Original report** **Short description of error** When wishing to create a bevel with the modifier on a specific vertex group aftern another Bevel modifier, the vertex group does not carry over. **Exact steps for others to reproduce the error** * Create a geometry * Mark some edges to bevel with bevel weight set to 1 * Add an edge loop in to a vertex group * Add a bevel modifier and use Weight * Add 2nd bevel modifier and use vertex group. The area where the first Bevel modifier has been executed does not become incorporated into the vertex group ![image](/attachments/0165df92-9e74-4a28-a666-8e33c2a35ac5) ![image](/attachments/d3eb2a82-0818-4403-9051-906198269378) ![image](/attachments/a97e9c29-e09f-4193-a6aa-62fbe447491e) ![image](/attachments/3e03825e-46a3-4db1-a22c-75dbd5eb853b) ![image](/attachments/049a3b04-f671-48cb-aa59-373e21684ee2)
Brecht Van Lommel added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-02-21 11:14:56 +01:00

Since this is an attribute, this appears to be a duplicate of a closed report: #104288

Since this is an attribute, this appears to be a duplicate of a closed report: https://projects.blender.org/blender/blender/issues/104288
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-02-21 13:40:37 +01:00
Iliya Katushenock added
Status
Duplicate
and removed
Status
Archived
labels 2023-02-21 13:40:41 +01:00
Author

@mod_moder , Since this predates the whole attributes system introduced with geometry nodes, it is not a duplicate of the report mentioned above. The vertex weights appear to work in some areas, and not in others, leading me to believe that it is some kind of bug

@mod_moder , Since this predates the whole attributes system introduced with geometry nodes, it is not a duplicate of the report mentioned above. The vertex weights appear to work in some areas, and not in others, leading me to believe that it is some kind of bug

Notice the different behavior for different domains?

Notice the different behavior for different domains?
Author

The bevel modifier doesn't allow for any different domains in vertex weights other than points.

The bevel modifier doesn't allow for any different domains in vertex weights other than points.
Blender Bot added
Status
Needs Triage
and removed
Status
Duplicate
labels 2023-02-21 13:57:42 +01:00
Iliya Katushenock added the
Interest
Modeling
Interest
Modifiers
labels 2023-02-21 14:02:12 +01:00
Member

Interesting.

Got a file here that has two objects with seemingly the same geometry.
One works, the other doesnt

Interesting. Got a file here that has two objects with seemingly the same geometry. One works, the other doesnt
Philipp Oeser added
Status
Confirmed
Module
Modeling
and removed
Status
Needs Triage
labels 2023-02-21 16:07:54 +01:00
Member

@howardt : would you know what is going on? (cant spot the difference on those two meshes)

@howardt : would you know what is going on? (cant spot the difference on those two meshes)

@lichtwerk They both don't work, play around with the modifier radius

@lichtwerk They both don't work, play around with the modifier radius
Author

@lichtwerk They both don't work, play around with the modifier radius

Yes, if the radius is quite small, the vertex weights transfer over, but it if it is larger, they decide not to. However, that is not always the case. In the original example I posted above, there is no issue on the corners of the mirrored object, which also utilised the same bevel weights and vertex groups. Maybe concave/convex have something to do with it also?

> @lichtwerk They both don't work, play around with the modifier radius Yes, if the radius is quite small, the vertex weights transfer over, but it if it is larger, they decide not to. However, that is not always the case. In the original example I posted above, there is no issue on the corners of the mirrored object, which also utilised the same bevel weights and vertex groups. Maybe concave/convex have something to do with it also?
Member

@lichtwerk They both don't work, play around with the modifier radius

Not sure I understand correctly.
I assume we are talking about Amount?

I can increase/decrease that on my example file for the good object as much as I want and still get correct results, bad is more or less always broken (unless you set Amount to zero of course).

Also, these two objects have the verts in the same positions (I snapped those), so unsure how concave/convex should matter here?

> @lichtwerk They both don't work, play around with the modifier radius Not sure I understand correctly. I assume we are talking about `Amount`? I can increase/decrease that on my example file for the `good` object as much as I want and still get correct results, `bad` is more or less always broken (unless you set `Amount` to zero of course). Also, these two objects have the verts in the same positions (I snapped those), so unsure how concave/convex should matter here?
Member

OK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well):

  • open the file
  • go into editmode
  • select all edges (edge select mode)
  • Mesh > Sort Elements > e.g. Cursor Distance
  • voila!
OK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well): - open the file - go into editmode - select all **edges** (edge select mode) - `Mesh` > `Sort Elements` > e.g. `Cursor Distance` - voila!

By the way, yes, this is not a regression ...

By the way, yes, this is not a regression ...

One more test. It seems that the interpolation used some kind of position data and there is some kind of error.

One more test. It seems that the interpolation used some kind of position data and there is some kind of error.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#105012
No description provided.