bevel bug #39184
Labels
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
11 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#39184
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
blender-2.70-8f1a6e2-win64-vc12
bevel_bug.zip
Changed status to: 'Open'
Added subscriber: @lopataasdf
#42442 was marked as duplicate of this issue
#41648 was marked as duplicate of this issue
Added subscriber: @mont29
Cannot reproduce this bug with current trunk, please try with a build from http://builder.blender.org/download
Also always please specify minimal steps to redo the issue (from your "no bevel" file, I simply hit ctrl-B, and wheel to increase number of edges, everything looks good to me...).
Added subscriber: @howardt
Added subscriber: @ignatz
Windows 7 Professional 64-bit
ASUS nVidia GeForce GTX 760 2GB GDDR5 DirectCU Mini
Blender 2.70 hash -
8f1a6e2I can confirm this behavior on my system:
lopataasdf has posted the images of how the bevel function is going wrong.
In this case, when more than one bevel segment is used, the profile setting is not being taken into account on every edge line passing through the profiled area.
This same problem can also be seen in the Blender 2.69 bevel function. There is no profile setting there, but the curve of the edges passing through the beveled area is also not always correct.
But it is latest version from http://builder.blender.org/download... Try to increase profile like "with bevel.png" screenshot
Ah, yes, indeed, can reproduce it now…
Added subscriber: @taxishop
hallo, i use the latest build blender-2.70-8f1a6e2-win64 and i get this workout. i use angle and depth. i hope, you meant the bevel modifier.
@taxishop - Thanks for the input, but...
The problem refers to the direct-action bevel command in edit (Ctrl-B) rather than the bevel modifier.
It seems that in my case, when the parameter "Profile" is changed, some edges moving along the axis Z, though they should move in the XY-plane only
bevel_bug_2.zip
outside edge is displaced up
anyway i reccomend you to use the bevel as a modifier+weight, so you can control, which part/vertex or edge should be beveled and how much. i never use the standard bevel option and actually its unnecessary.
bevel operation and bevel modifier use same code
I see what you are talking about. I need to investigate further to see if this is working as intended or whether there is a bug here. I think there is probably a bug that can be fixed.
Added subscriber: @Harshit-3
bevel_bug_3.zip
Changed status from 'Open' to: 'Resolved'
I think I fixed this with commit
84767a29f1but am not sure whether this bug is complaining about more than one problem. I'm closing this for now, feel free to reopen if there are remaining problem(s).Changed status from 'Resolved' to: 'Open'
Added subscriber: @cdog
Howardt, I can still reproduce the bug mentioned in the first post in today's build. That means edge loops which are close to each other still don't follow curvature and go straight. Just try a multisegment bevel on an edge loop.
bevel_bug.blend
The problem here is that you have edges totally in a plane (both the two edges to be beveled, and the two cross-edges on either side), and you want the multisegment bevel to be curved. I know that in this case, where they are running beside other edges that curve (because they aren't all in the same plane), it looks like a mistake. But there are other cases where making them curve can look wrong. So not clear what to do here.
Removed subscriber: @Harshit-3
I can't imagine a situation where I wouldn't want them to curve, but if you say so :) Maybe a checkbox then?
Here's a situation where making the cross-edges curved is not obviously the right thing to do. On the left is the edge to be beveled. In the middle is the current behavior. On the right is the result of an exploratory hack to recognize "being flat in a plane" as a special case and making them curve. (The outside edges don't curve because that's even more of a special case in the code that would have to be changed separately. Is the curved image always better and should I continue down this path? On issue could be that it is fragiley adapted to a special case, and making small changes in geometry could cause big flips in behavior. This could be the start of a long path of special cases to get this right...
The behaviour I would like is in the following image. Which means curved inside and outside edges included. The current behaviour really doesn't behave like a multisegment bevel. I could get the same with 1 segment bevel and then add loopcuts. So I think it's definitely worth continuing this path.
Added subscriber: @00Ghz
I agree. Curved all the way looks better but there should be an option to disable outside/inside curvature just in case.
Added subscriber: @Idlero
Added subscribers: @gandalf3, @ThomasDinges
Added subscriber: @JulianEisel
@howardt, so what's going on with this? Is it fixed or a Todo or a valid, un-fixed bug? ;)
I have a branch that partially fixes this, but it is not working correctly everywhere, yet, and is too big a change to put in the close to the next release. I continue to work in the branch and hopefully will commit the change after the release.
This issue was referenced by
2140cb60cbChanged status from 'Open' to: 'Resolved'
Closed by commit
2140cb60cb.