Bevel Problem #53145

Closed
opened 2017-10-24 11:59:25 +02:00 by Alvin Nashif Magarang · 43 comments

System Information
Windows 10

Blender Version
Blender 2.79, cc96cdd

Short description of error

when I bevel an object for a second try by dragging mouse to adjust the effect and it moves to 1000000.000000 Offset.
and when I try it on 2.80 build for the sake that if its a hardware problem, well it only affects just the current Oct 24 Build of 2.79.

Exact steps for others to reproduce the error

  1. Edit the default cube, Ctrl + B and make a bevel
  2. Go out edit mode and add another cube, repeat step 1 and adjust the bevel offset by dragging the mouse ...
**System Information** Windows 10 **Blender Version** Blender 2.79, cc96cdd **Short description of error** when I bevel an object for a second try by dragging mouse to adjust the effect and it moves to 1000000.000000 Offset. and when I try it on 2.80 build for the sake that if its a hardware problem, well it only affects just the current Oct 24 Build of 2.79. **Exact steps for others to reproduce the error** 1) Edit the default cube, Ctrl + B and make a bevel 2) Go out edit mode and add another cube, repeat step 1 and adjust the bevel offset by dragging the mouse ...

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @AlvinNashifMagarang

Added subscriber: @AlvinNashifMagarang

#53379 was marked as duplicate of this issue

#53379 was marked as duplicate of this issue

#53237 was marked as duplicate of this issue

#53237 was marked as duplicate of this issue

Added subscriber: @V-11

Added subscriber: @V-11

Same thing for me in last builds from buildbot (now is cc96cdd).
Walk here to report this.
Reloading blender helps to drop this aftermath for one problem beveling, but then comes again, and save->quit->load->do it again again.

Same thing for me in last builds from buildbot (now is cc96cdd). Walk here to report this. Reloading blender helps to drop this aftermath for one problem beveling, but then comes again, and save->quit->load->do it again again.

Added subscribers: @ideasman42, @FloridaJo

Added subscribers: @ideasman42, @FloridaJo
Campbell Barton was assigned by Joel Godin 2017-10-24 12:39:00 +02:00

@ideasman42 I'm guessing this is either yours or Brechts?

Oct 6 build was good, Oct 24 (on OSX) has the problem.

@ideasman42 I'm guessing this is either yours or Brechts? Oct 6 build was good, Oct 24 (on OSX) has the problem.

Added subscriber: @Chris_Blend

Added subscriber: @Chris_Blend

System Debian 9.2 and Ubuntu 17.04

Hi,

Same thing from Buildbot 2.79 and 2.80 Oct 24.

Thanks

System Debian 9.2 and Ubuntu 17.04 Hi, Same thing from Buildbot 2.79 and 2.80 Oct 24. Thanks

Bevel problem still there

Blender 2.79 2ae6a93
Nov 1 2017 build Win64

Bevel problem still there Blender 2.79 2ae6a93 Nov 1 2017 build Win64

Added subscriber: @EugenioPignataro

Added subscriber: @EugenioPignataro

Ubuntu 16.04 Too.

Ubuntu 16.04 Too.

Added subscriber: @Ace_Dragon

Added subscriber: @Ace_Dragon

Added subscriber: @NahuelBelich

Added subscriber: @NahuelBelich
Campbell Barton was unassigned by Joel Godin 2017-11-06 14:56:29 +01:00

Not sure if connected issue, but 'inset' also has a weird glitch where a second 'inset' insets to the same proportion as the first.
One small move of the mouse and it jumps back to normal size (just less than original face size).
Will wait for developer to see if issues are connected before generating bug report for this as well.

Not sure if connected issue, but 'inset' also has a weird glitch where a second 'inset' insets to the same proportion as the first. One small move of the mouse and it jumps back to normal size (just less than original face size). Will wait for developer to see if issues are connected before generating bug report for this as well.
Campbell Barton was assigned by Joel Godin 2017-11-06 14:57:12 +01:00

Added subscriber: @pauljs75

Added subscriber: @pauljs75

Can confirm as another user. Having the same exact problem with the latest Blender-Edge (via Thomas Sheix PPA) release on Linux Mint 17.3.

Bevel just jumps up to this ridiculously high value that makes it unusable with the initial mouse input. For now I have to fall back to using the menu.

Can confirm as another user. Having the same exact problem with the latest Blender-Edge (via Thomas Sheix PPA) release on Linux Mint 17.3. Bevel just jumps up to this ridiculously high value that makes it unusable with the initial mouse input. For now I have to fall back to using the menu.

Added subscriber: @ArnasKarmaza

Added subscriber: @ArnasKarmaza

Yeah me too, windows 10 64 bit GTX 1080 Ti, newest Nvidia drivers. The first bevel operation is always okay but the second one fails like described.

Yeah me too, windows 10 64 bit GTX 1080 Ti, newest Nvidia drivers. The first bevel operation is always okay but the second one fails like described.

Added subscriber: @AlbertoVelazquez

Added subscriber: @AlbertoVelazquez

Added subscriber: @GatisKurzemnieks

Added subscriber: @GatisKurzemnieks

This issue was referenced by 5e13097dc3

This issue was referenced by 5e13097dc3a3463d6b8643a5ace673d7a462c934

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

This is not yet resolved. The updated daily build still has very weird bevel functionality, the values almost always jump too high from the start, making the interactive tool almost useless again. Please take a better look into the issue, but it's already better than before :) Thanks!

This is not yet resolved. The updated daily build still has very weird bevel functionality, the values almost always jump too high from the start, making the interactive tool almost useless again. Please take a better look into the issue, but it's already better than before :) Thanks!

I can confirm that the tool have change the behaviour but still having issues.

I can confirm that the tool have change the behaviour but still having issues.

This is already resolved to me ... Thanks devs :)

my build is 11-23-2017, Blender 2.79.1 b63442e ...

This is already resolved to me ... Thanks devs :) my build is 11-23-2017, Blender 2.79.1 b63442e ...

In #53145#472256, @ArnasKarmaza wrote:
This is not yet resolved. The updated daily build still has very weird bevel functionality, the values almost always jump too high from the start, making the interactive tool almost useless again. Please take a better look into the issue, but it's already better than before :) Thanks!

did you try to hold shift while dragging, in that way you will easily control the values?

> In #53145#472256, @ArnasKarmaza wrote: > This is not yet resolved. The updated daily build still has very weird bevel functionality, the values almost always jump too high from the start, making the interactive tool almost useless again. Please take a better look into the issue, but it's already better than before :) Thanks! did you try to hold shift while dragging, in that way you will easily control the values?

It's not about precision, I'm saying that the default value isn't 0 but instead it's a lot higher. Basically when you start beveling it jumps to a high value (not the maximum as previously) but still high.

It's not about precision, I'm saying that the default value isn't 0 but instead it's a lot higher. Basically when you start beveling it jumps to a high value (not the maximum as previously) but still high.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Resolved' to: 'Open'

Changed status from 'Resolved' to: 'Open'

Is the problem that it now remembers the bevel amount when you use the bevel tool a second time? I assumed that was by design, so that you can easily redo the same bevel in another place, but seems that in 2.79 it always starts from 0.

Is the problem that it now remembers the bevel amount when you use the bevel tool a second time? I assumed that was by design, so that you can easily redo the same bevel in another place, but seems that in 2.79 it always starts from 0.

All the tools have the same initial value, zero, It doesn't have memory.

To repeat an action always you need to use Repeat Last.

All the tools have the same initial value, zero, It doesn't have memory. To repeat an action always you need to use Repeat Last.

This comment was removed by @ArnasKarmaza

*This comment was removed by @ArnasKarmaza*

This comment was removed by @ArnasKarmaza

*This comment was removed by @ArnasKarmaza*

Here's the issue demonstrated: https://streamable.com/3rv94 at first the issue is there, but then suddely after trying to bevel a different edge it goes back to normal again. This is hard to reproduce exactly. Also it seems to not depend on mouse position sometimes when the issue persists.
Side note, this could be caused by object's scale, but in this case it's default so that's not the culprit.
Just after writing this and uploading the video I realized what's happening -_- :

If you perform a higher value bevel and then try to perform a smaller value bevel it clamps. This is somewhat of an issue, but expected behaviour after all. Damn

Here's the issue demonstrated: https://streamable.com/3rv94 at first the issue is there, but then suddely after trying to bevel a different edge it goes back to normal again. This is hard to reproduce exactly. Also it seems to not depend on mouse position sometimes when the issue persists. Side note, this could be caused by object's scale, but in this case it's default so that's not the culprit. Just after writing this and uploading the video I realized what's happening -_- : If you perform a higher value bevel and then try to perform a smaller value bevel it clamps. This is somewhat of an issue, but expected behaviour after all. Damn

In #53145#472343, @ArnasKarmaza wrote:
Here's the issue demonstrated: https://streamable.com/3rv94 at first the issue is there, but then suddely after trying to bevel a different edge it goes back to normal again. This is hard to reproduce exactly. Also it seems to not depend on mouse position sometimes when the issue persists.
Side note, this could be caused by object's scale, but in this case it's default so that's not the culprit.
Just after writing this and uploading the video I realized what's happening -_- :

If you perform a higher value bevel and then try to perform a smaller value bevel it clamps. This is somewhat of an issue, but expected behaviour after all. Damn

did you try to, Ctrl + A - Apply Scale and Rotation to the object before beveling?

I tried to higher value then smaller ...
it just place the last value from the higher value or just the last bevel value ...

which I think it's somewhat better, that you can easily apply the same bevel value across all selected edges and even on different objects ...

> In #53145#472343, @ArnasKarmaza wrote: > Here's the issue demonstrated: https://streamable.com/3rv94 at first the issue is there, but then suddely after trying to bevel a different edge it goes back to normal again. This is hard to reproduce exactly. Also it seems to not depend on mouse position sometimes when the issue persists. > Side note, this could be caused by object's scale, but in this case it's default so that's not the culprit. > Just after writing this and uploading the video I realized what's happening -_- : > > If you perform a higher value bevel and then try to perform a smaller value bevel it clamps. This is somewhat of an issue, but expected behaviour after all. Damn did you try to, Ctrl + A - Apply Scale and Rotation to the object before beveling? I tried to higher value then smaller ... it just place the last value from the higher value or just the last bevel value ... which I think it's somewhat better, that you can easily apply the same bevel value across all selected edges and even on different objects ...

As I said the scale is default, reset. But yes this is expected behaviour. It took me quite a while to figure it out.

However that doesn't mean that it's perfect. If you bevel an edge a lot and then try to bevel a smaller one, the value will be clamped and won't go down to 0.

Anyways whether it'll be changed or not this is no longer related to the initial problem of this topic which was fixed already (thanks Campbell :))

Thanks!

As I said the scale is default, reset. But yes this is expected behaviour. It took me quite a while to figure it out. However that doesn't mean that it's perfect. If you bevel an edge a lot and then try to bevel a smaller one, the value will be clamped and won't go down to 0. Anyways whether it'll be changed or not this is no longer related to the initial problem of this topic which was fixed already (thanks Campbell :)) Thanks!

This issue was referenced by 2bf3825711

This issue was referenced by 2bf382571126382d80bd12b471324d38a480cd6a

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

I've set it to start bevelling with amount 0 again now. There were two commits that together caused this bug, and hopefully the unintentional changes from both are resolved now.

In #53145#472338, @AlbertoVelazquez wrote:
All the tools have the same initial value, zero, It doesn't have memory.

Definitely not true for all tools, each property can specify if it needs to be remembered or not.

I've set it to start bevelling with amount 0 again now. There were two commits that together caused this bug, and hopefully the unintentional changes from both are resolved now. * 96ce50449c * {83b60dac57a}. > In #53145#472338, @AlbertoVelazquez wrote: > All the tools have the same initial value, zero, It doesn't have memory. Definitely not true for all tools, each property can specify if it needs to be remembered or not.

Thanks @brecht I'm amazed at how well you manage everything! :)

Thanks @brecht I'm amazed at how well you manage everything! :)

@brecht Interesting the Inset has the same bug.
I was waiting to see if the correction would fix that too, but Dec 1 build still have the issue with inset.
I will submit a new bug report for that.

@brecht Interesting the Inset has the same bug. I was waiting to see if the correction would fix that too, but Dec 1 build still have the issue with inset. I will submit a new bug report for that.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
Asset Browser Project
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
12 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#53145
No description provided.