Bevel tool (and modifier) doesn't work properly #58822

New Issue

Vlad · 2018-12-05T21:36:30+01:00

Vlad commented

2018-12-05 21:36:30 +01:00

System Information
Operating system: windows 10
Graphics card: gtx 1080

Blender Version

2.80.35

Short description of error

Bevel tool doesn't work as it should in this case - shown in the screenshots. It also concerns 2.79 version

bevelTool.blend

**System Information** Operating system: windows 10 Graphics card: gtx 1080 **Blender Version** 2.80.35 **Short description of error** Bevel tool doesn't work as it should in this case - shown in the screenshots. It also concerns 2.79 version ![2.png](https://archive.blender.org/developer/F5840541/2.png) ![1.png](https://archive.blender.org/developer/F5840540/1.png) [bevelTool.blend](https://archive.blender.org/developer/F5840564/bevelTool.blend)

Vlad commented

2018-12-05 21:36:30 +01:00

Added subscriber: @GlancingEYE

Howard Trickey was assigned by Bastien Montagne

2018-12-06 09:01:13 +01:00

Howard Trickey commented

2018-12-06 15:20:28 +01:00

Yes, I see the problem. You can work around it by turning off the 'Loop Slide' option.
There's some complicated optimization that goes on to try to even out the loops when loop slide is on, and looks like there might be a bug in that.

Yes, I see the problem. You can work around it by turning off the 'Loop Slide' option. There's some complicated optimization that goes on to try to even out the loops when loop slide is on, and looks like there might be a bug in that.

Howard Trickey commented

2019-03-22 17:07:06 +01:00

Changed status from 'Open' to: 'Archived'

Howard Trickey closed this issue

2019-03-22 17:07:06 +01:00

Howard Trickey commented

2019-03-22 17:07:06 +01:00

OK, I finally found time to look at this. Unfortunately, I am going to close this as "working as intended". The workaround cited above (turn off Loop Slide) should be satisfactory in cases like this.

Some more explanation:
When 'Loop Slide' is on, it sets up a frequently unsolvable set of constraints on what the solution is supposed to do. We want the bevel widths to match their specified widths, but that is impossible if the intersection between two adjacent beveled edges is forced by 'Loop Slide'. So there is an optimization pass which tries to keep the bevel widths as even as possible while matching the specs as closely as possible. In this case, the place where the angled up connecting edge occurs is where the width of the long beveled edge differs from the spec by being smaller (in order to not distort the width too much along the bottom) and that forces an intersection point that is angled up. Other than giving the user more control over what to favor in the optimization step ("even widths" vs "spec width matched"), I don't know how to solve this problem.
I checked and the math for the optimization problem was correct. When I originally got this report, i wondered whether I had made a mistake there, but no I did not.

OK, I finally found time to look at this. Unfortunately, I am going to close this as "working as intended". The workaround cited above (turn off Loop Slide) should be satisfactory in cases like this. Some more explanation: When 'Loop Slide' is on, it sets up a frequently unsolvable set of constraints on what the solution is supposed to do. We want the bevel widths to match their specified widths, but that is impossible if the intersection between two adjacent beveled edges is forced by 'Loop Slide'. So there is an optimization pass which tries to keep the bevel widths as even as possible while matching the specs as closely as possible. In this case, the place where the angled up connecting edge occurs is where the width of the long beveled edge differs from the spec by being smaller (in order to not distort the width too much along the bottom) and that forces an intersection point that is angled up. Other than giving the user more control over what to favor in the optimization step ("even widths" vs "spec width matched"), I don't know how to solve this problem. I checked and the math for the optimization problem was correct. When I originally got this report, i wondered whether I had made a mistake there, but no I did not.

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

Bevel tool (and modifier) doesn't work properly #58822