Bevel Bug #40100

Closed
opened 2014-05-08 21:28:08 +02:00 by Vlad Mafteiu Scai · 15 comments

System Information
Win 8 64, 2x MSI 780 Lightning

Blender Version
Broken: (example: 2.70.5, 7660218, see splash screen)Untitled-1.png
Worked: (optional)

Beveling Edge creates huge spikes

Exact steps for others to reproduce the error
Checked attached blend file. Added edge issue to vertex group for easy selection and checking.bug.blend

**System Information** Win 8 64, 2x MSI 780 Lightning **Blender Version** Broken: (example: 2.70.5, 7660218, see splash screen)![Untitled-1.png](https://archive.blender.org/developer/F87933/Untitled-1.png) Worked: (optional) **Beveling Edge creates huge spikes** **Exact steps for others to reproduce the error** Checked attached blend file. Added edge issue to vertex group for easy selection and checking.[bug.blend](https://archive.blender.org/developer/F87932/bug.blend)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @00Ghz

Added subscriber: @00Ghz
Howard Trickey was assigned by Bastien Montagne 2014-05-10 08:36:34 +02:00

Added subscriber: @mont29

Added subscriber: @mont29

Added subscriber: @voyagercgi

Added subscriber: @voyagercgi

Percentage amount type works fine and other fails.

Percentage amount type works fine and other fails.

Added subscriber: @MarcClintDion

Added subscriber: @MarcClintDion

I've seen this many times. I've tried baking models when this is happening and didn't notice it right away. It shows up in the baked texture as torn triangles.

If I remember correctly, this always goes away for me when I set the number of segments to 1. Unfortunately, I still don't see the pattern behind what types of geometry are causing this.

Oh and, please pass this around. Reporting Bugs in Blender from Sebastian König http://vimeo.com/75649649

I've seen this many times. I've tried baking models when this is happening and didn't notice it right away. It shows up in the baked texture as torn triangles. If I remember correctly, this always goes away for me when I set the number of segments to 1. Unfortunately, I still don't see the pattern behind what types of geometry are causing this. Oh and, please pass this around. Reporting Bugs in Blender from Sebastian König http://vimeo.com/75649649

I have just found a situation that reproduces this. 2.png

1.png

bevelTear.blend

The cylinder is default scale and when I apply the modifier, that long section that is created by the bevel modifier gives the object size as 12144.138 units along the y-axis and 3686.569 along the x-axis.

I have just found a situation that reproduces this. ![2.png](https://archive.blender.org/developer/F114412/2.png) ![1.png](https://archive.blender.org/developer/F114413/1.png) [bevelTear.blend](https://archive.blender.org/developer/F114419/bevelTear.blend) The cylinder is default scale and when I apply the modifier, that long section that is created by the bevel modifier gives the object size as 12144.138 units along the y-axis and 3686.569 along the x-axis.
Member

Added subscribers: @howardt, @JulianEisel

Added subscribers: @howardt, @JulianEisel
Member

Any news on this @howardt?

Any news on this @howardt?
Member

I am on vacation now. Will look at this again when I get back, in a couple of days.

I am on vacation now. Will look at this again when I get back, in a couple of days.
Member

This is similar to bug #39486 where the "adjustment pass" to try to equalize bevel widths keeps accumulating a width increment. Here is a simplified file from the one in this bug report, that still exhibits the problem (even with a bevel amount of .0005).
adjust_error.blend
I'm stuck with the same choices I enumerated in that other bug: either add annoying "do not adjust" workaround flag, or figure out a better adjustment algorithm that doesn't cause this accumulation of increments. I'll try harder to think of the latter but for now this bug remains pending.

This is similar to bug #39486 where the "adjustment pass" to try to equalize bevel widths keeps accumulating a width increment. Here is a simplified file from the one in this bug report, that still exhibits the problem (even with a bevel amount of .0005). [adjust_error.blend](https://archive.blender.org/developer/F152366/adjust_error.blend) I'm stuck with the same choices I enumerated in that other bug: either add annoying "do not adjust" workaround flag, or figure out a better adjustment algorithm that doesn't cause this accumulation of increments. I'll try harder to think of the latter but for now this bug remains pending.
Member

@howardt, looks like the bugs can be merged as they likely have the same root?

@howardt, looks like the bugs can be merged as they likely have the same root?

Removed subscriber: @voyagercgi

Removed subscriber: @voyagercgi
Member

Closed as duplicate of #39486

Closed as duplicate of #39486
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
6 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#40100
No description provided.