Bevel clamp overlap incorrect with percentage #79898

Closed
opened 2020-08-18 22:55:51 +02:00 by michael campbell · 12 comments

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

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-05 22:29, hash: 675700d948
Worked: Never (2.8+)

Short description of error
edit mode bevel operation clamp overlap is basing overlap on offset rather than percentage, and therefore clamping even when there is no overlap.

Exact steps for others to reproduce the error
#79898.blend

  • Open file
  • Select all edges
  • Set bevel to percent
  • Turn on clamp overlap

Increase the width to 100%.

Even though it’s set to percent, the clamp will still stop the edges that shouldn’t be clamped from fully bevelling.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48 **Blender Version** Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-05 22:29, hash: `675700d948` Worked: Never (2.8+) **Short description of error** edit mode bevel operation clamp overlap is basing overlap on offset rather than percentage, and therefore clamping even when there is no overlap. **Exact steps for others to reproduce the error** [#79898.blend](https://archive.blender.org/developer/F8809621/T79898.blend) - Open file - Select all edges - Set bevel to percent - Turn on clamp overlap # Increase the width to 100%. Even though it’s set to percent, the clamp will still stop the edges that shouldn’t be clamped from fully bevelling.

Added subscriber: @3di

Added subscriber: @3di

Added subscriber: @iss

Added subscriber: @iss

Is this reported problem?
Untitled.png

Is this reported problem? ![Untitled.png](https://archive.blender.org/developer/F8798710/Untitled.png)

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

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

No, your bevelling vertices.

Create an object where one edge would cause a clamp to occur before other edges were fully bevelled

Select all edges
Bevel
Set bevel to percent
Turn on clamp overlap
Now increase the width.

Even though it’s set to percent, the clamp will still stop the edges that shouldn’t be clamped from fully bevelling.

No, your bevelling vertices. Create an object where one edge would cause a clamp to occur before other edges were fully bevelled Select all edges Bevel Set bevel to percent Turn on clamp overlap Now increase the width. Even though it’s set to percent, the clamp will still stop the edges that shouldn’t be clamped from fully bevelling.
Richard Antalik changed title from edit mode bevel operation clamp overlap is basing overlap on offset rather than percentage. to Bevel clamp overlap incorrect with percentage 2020-08-25 06:41:42 +02:00

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

Changed status from 'Needs User Info' to: 'Confirmed'
Member

Added subscriber: @howardt

Added subscriber: @howardt
Howard Trickey self-assigned this 2020-09-23 02:12:13 +02:00
Member

There is indeed a bug here. The clamp code works when the offset edges move parallel to the original edges, but that is not usually the case when Percentage mode is used. (The same bug will affect the new Absolute mode.) I will have to work out the different math for this case.

There is indeed a bug here. The clamp code works when the offset edges move parallel to the original edges, but that is not usually the case when Percentage mode is used. (The same bug will affect the new Absolute mode.) I will have to work out the different math for this case.
Member

In working on adding clamping for Percent (which is hard!), I have discovered that the whole method of doing Percent is wrong. It is making constant width offset lines.

In working on adding clamping for Percent (which is hard!), I have discovered that the whole method of doing Percent is wrong. It is making constant width offset lines.
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

Well this was quite the rabbit-hole. The whole method of doing percent (and absolute) mode was wrong. It worked if the required offset lines were parallel to the original edge, and maybe in a few other cases accidentally, but really I needed to write whole new code to handle these modes.

After doing that, the clamping for percent was trivial to fix: you need to clamp to 50% if two beveled edges shared the same leg.
The clamping for absolute mode is significantly harder. It is improved, but I'm going to leave its still-somewhat-brokenness as a known issue.
I really hope to be able to do away with clamping all together with a major upgrade to Bevel that I hope to work on next.

Well this was quite the rabbit-hole. The whole method of doing percent (and absolute) mode was wrong. It worked if the required offset lines were parallel to the original edge, and maybe in a few other cases accidentally, but really I needed to write whole new code to handle these modes. After doing that, the clamping for percent was trivial to fix: you need to clamp to 50% if two beveled edges shared the same leg. The clamping for absolute mode is significantly harder. It is improved, but I'm going to leave its still-somewhat-brokenness as a known issue. I really hope to be able to do away with clamping all together with a major upgrade to Bevel that I hope to work on next.

Cool, perhaps bevel width could be done based on the visual representation of vertex weight falloff on the face. 0.5 would always be halfway towards the nearest vertex for example. Would probably need edge weight too though for that to work on long edges.

Cool, perhaps bevel width could be done based on the visual representation of vertex weight falloff on the face. 0.5 would always be halfway towards the nearest vertex for example. Would probably need edge weight too though for that to work on long edges.
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#79898
No description provided.