Bevelling an edge loop gives bad geometry #50819

New Issue

Paul R · 2017-02-28T15:33:02+01:00

Paul R commented

2017-02-28 15:33:02 +01:00

System Information
Suse Leap 42.1
NVidia GTX 560ti (official drivers)

Blender Version
Broken: all tested versions

Short description of error
The bevel seems inconsistent; when working with single or multiple edges, new geometry doesn't move past adjacent existing geometry (as expected). But when bevelling a complete edge loop, the new geometry isn't constrained in the same way and overshoots.

I can't think of a situation where this would be desirable.

Demo video: blender_bevel_bug_demo_v2.mp4
alternative link: https://youtu.be/bBjjFsImcOc?t=14

Exact steps for others to reproduce the error

add a torus and select a complete edge loop
bevel
geometry overshoots

**System Information** Suse Leap 42.1 NVidia GTX 560ti (official drivers) **Blender Version** Broken: all tested versions **Short description of error** The bevel seems inconsistent; when working with single or multiple edges, new geometry doesn't move past adjacent existing geometry (as expected). But when bevelling a complete edge loop, the new geometry isn't constrained in the same way and overshoots. I can't think of a situation where this would be desirable. Demo video: [blender_bevel_bug_demo_v2.mp4](https://archive.blender.org/developer/F498836/blender_bevel_bug_demo_v2.mp4) alternative link: https://youtu.be/bBjjFsImcOc?t=14 **Exact steps for others to reproduce the error** - add a torus and select a complete edge loop - bevel - geometry overshoots

Paul R commented

2017-02-28 15:33:02 +01:00

Changed status to: 'Open'

Paul R commented

2017-02-28 15:33:02 +01:00

Added subscriber: @intracube

Aaron Carlisle commented

2017-02-28 18:10:56 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-02-28 18:10:56 +01:00

The video is not playing for me

Howard Trickey was assigned by Aaron Carlisle

2017-02-28 19:47:28 +01:00

Howard Trickey was unassigned by Paul R

2017-02-28 19:48:30 +01:00

Paul R commented

2017-02-28 19:48:30 +01:00

Added subscriber: @howardt

Paul R commented

2017-02-28 19:59:32 +01:00

Looks like there's no single video format that's compatible with modern browsers...

Hopefully the Youtube link works.

Looks like there's no single video format that's compatible with modern browsers... Hopefully the Youtube link works.

Howard Trickey was assigned by Paul R

2017-02-28 20:07:53 +01:00

Ray molenkamp commented

2017-02-28 20:13:29 +01:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-02-28 20:13:29 +01:00

@Blendify right click save as, seems to do the job for me

Howard Trickey commented

2017-02-28 22:47:20 +01:00

Sorry, I haven't had a chance to look into this yet. The code that prevents overlap is (the 'clamp overlap' option) is only approximately right, since getting it really right is quite hard. But I agree it seems to be failing completely in the case of selecting a whole loop, and hopefully it will be easy to figure out why and correct it.

Paul R commented

2017-03-01 16:21:04 +01:00

There seems to be two independent clamping events/rules. The 'clamp overlap' option only affects whether new bevel geometry overlaps other new bevel geometry. But even with that disabled, the bevel doesn't normally cross over pre-existing geometry (which seems sensible) - unless you're bevelling a complete edge loop.

example:
^ two adjacent edges bevelled with clamp overlap disabled, the new geometry (purple) can cross over each other, but is still constrained by the existing edges (green). The other side of the bevel can still continue outwards until it too hits existing geometry (yellow).

A side-issue; with clamp overlap enabled, the bevel sometimes stops short:

In that setup, It should reach the midpoint.

There seems to be two independent clamping events/rules. The 'clamp overlap' option only affects whether new bevel geometry overlaps other new bevel geometry. But even with that disabled, the bevel doesn't normally cross over pre-existing geometry (which seems sensible) - unless you're bevelling a complete edge loop. example: ![bevel_clamp_overlap_04_example_v2.png](https://archive.blender.org/developer/F499518/bevel_clamp_overlap_04_example_v2.png) ^ two adjacent edges bevelled with clamp overlap disabled, the new geometry (purple) can cross over each other, but is still constrained by the existing edges (green). The other side of the bevel can still continue outwards until it too hits existing geometry (yellow). A side-issue; with clamp overlap enabled, the bevel sometimes stops short: ![bevel_clamp_overlap_05_stops_short.png](https://archive.blender.org/developer/F499520/bevel_clamp_overlap_05_stops_short.png) In that setup, It should reach the midpoint.

Howard Trickey commented

2017-08-11 15:21:26 +02:00

The fix just committed only fixes this bug if the 'Clamp overlap' option is enabled. The fact that sometimes the existing code stops the edge slides when it hits another vertex was not something that was intended to find and fix all geometry collisions. Even 'Clamp overlap' doesn't do that, though it tries harder.

Paul R commented

2017-08-18 19:40:28 +02:00

Hi,

I can confirm this fixes the clamp function in all bevel modes except for 'percent' - in that case the bevel still sometimes stops short.

Bevelling two adjacent edge loops on a default torus works, but if the loops are shifted apart beforehand, the newly created geometry doesn't meet up with itself.

Hi, I can confirm this fixes the clamp function in all bevel modes except for 'percent' - in that case the bevel still sometimes stops short. Bevelling two adjacent edge loops on a default torus works, but if the loops are shifted apart beforehand, the newly created geometry doesn't meet up with itself.

Howard Trickey commented

2019-03-21 12:03:32 +01:00

Changed status from 'Open' to: 'Resolved'

Howard Trickey closed this issue

2019-03-21 12:03:32 +01:00

Howard Trickey commented

2019-03-21 12:03:32 +01:00

Clearing out old bugs. Clamping is currently working as intended, even if not ideal. The long term fix is to actually have the geometry merge and/or otherwise do intelligent things when collision happens, and then remove 'Clamp' completely. I hope to get to that as my next big bevel improvement project, though it is some time off.

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

Bevelling an edge loop gives bad geometry #50819