Bevel modifier bug #114860

New Issue

Closed

opened 2023-11-14 19:17:22 +01:00 by Mykola Filon · 4 comments

Mykola Filon commented

2023-11-14 19:17:22 +01:00

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01

Blender Version
Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: 878f71061b8e
Worked: (newest version of Blender that worked as expected)

Short description of error
Complex Solidify + Bevel working incorrectly with marked with bevel - ignoring which vertexes have wbevel weight 1.0 or 0.0, making bevel on all vertexes

Exact steps for others to reproduce the error

Open attached .blend file or
- Create plane
- Add some subdivisions to have more vertecies on the mesh
- Mark outer edges with bevel weight 1.0
- Mark corner vertecies with bevel weight 1.0
- Add Solidify modifier to mesh, change from Simple to Comlex Type
- Add Bevel modifier. Limit method to Weight

In 3.6 you are getting bevel only on marked edges+marked vertecies
In 4.0 making bevel on all vertecies which are in the marked edges with bevel weight

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01 **Blender Version** Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: `878f71061b8e` Worked: (newest version of Blender that worked as expected) **Short description of error** Complex Solidify + Bevel working incorrectly with marked with bevel - ignoring which vertexes have wbevel weight 1.0 or 0.0, making bevel on all vertexes **Exact steps for others to reproduce the error** - Open attached .blend file or - Create plane - Add some subdivisions to have more vertecies on the mesh - Mark outer edges with bevel weight 1.0 - Mark corner vertecies with bevel weight 1.0 - Add Solidify modifier to mesh, change from Simple to Comlex Type - Add Bevel modifier. Limit method to Weight In 3.6 you are getting bevel only on marked edges+marked vertecies In 4.0 making bevel on all vertecies which are in the marked edges with bevel weight

solidify_400__change.blend

855 KiB

Bevel_3.6.png

1.6 MiB

Bevel_4.png

1.6 MiB

Bevel_3.6.png

Mykola Filon added the

labels 2023-11-14 19:17:22 +01:00

Germano Cavalcante added

and removed

labels 2023-11-15 15:37:41 +01:00

Germano Cavalcante commented

2023-11-15 16:17:50 +01:00

Member

Strangely, the new edges created by solidify copy the bevel weight of neighboring edges.

It would make more sense to use the bevel weight of the original vertex.

Caused by 2a56403cb0

@HooglyBoogly ^

Strangely, the new edges created by solidify copy the bevel weight of neighboring edges. It would make more sense to use the bevel weight of the original vertex. Caused by 2a56403cb0 @HooglyBoogly ^

Hans Goudey commented

2023-11-15 16:19:21 +01:00

Member

Long term this can be done by storing different attribute propagation settings. But for now, bevel weights are just propagated as generic attributes, that's the tradeoff of the design.

Long term this can be done by storing different attribute propagation settings. But for now, bevel weights are just propagated as generic attributes, that's the tradeoff of the design.

Germano Cavalcante commented

2023-11-15 16:45:05 +01:00

Member

I see.

Since the modifier will not know for what use the attribute will be intended, it would be somewhat random to take attribute from one type of element (vertices) and convert it to another (edges).

But propagating what is intended for the edge bevel to new edges does not seem to be advantageous. It looks like a regression.

Maybe the Solidify interface should add a new feature to avoid this?
Something like: Propagate Attribute from Vertex: [Source Attribute] [Target Attribute]

I see. Since the modifier will not know for what use the attribute will be intended, it would be somewhat random to take attribute from one type of element (vertices) and convert it to another (edges). But propagating what is intended for the edge bevel to new edges does not seem to be advantageous. It looks like a regression. Maybe the Solidify interface should add a new feature to avoid this? Something like: `Propagate Attribute from Vertex: [Source Attribute] [Target Attribute]`

Germano Cavalcante commented

2023-11-15 16:51:58 +01:00

Member

Or:
Propagate Vertex Attribute to Edge: [Attribute A, Attribute B, Attribute C] + Add

Or: **Propagate Vertex Attribute to Edge:** [Attribute A, Attribute B, Attribute C] + Add

Laurynas Duburas referenced a pull request that will close this issue

2023-11-20 13:05:17 +01:00

Fix #114860: Edge bevel weights in complex solidify #115178

Hans Goudey added

and removed

labels 2023-11-20 14:43:30 +01:00

Hans Goudey referenced this issue from a commit

2023-11-20 14:44:25 +01:00

Fix #114860: Edge bevel weights in complex solidify

Hans Goudey closed this issue

2023-11-20 14:44:27 +01:00

Blender Bot added

and removed

labels 2023-11-20 14:45:34 +01:00

Laurynas Duburas referenced this issue

2023-11-22 11:23:03 +01:00

Fix: bevel weights in Simple mode of Solidify #115258

Hans Goudey referenced this issue from a commit

2023-11-22 13:42:11 +01:00

Fix: bevel weights in Simple mode of Solidify

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

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#114860

No description provided.