Bevel Problem
Closed, ResolvedPublic

Description

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 ...

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.

Joel Godin (FloridaJo) triaged this task as Confirmed priority.Oct 24 2017, 12:39 PM

@Campbell Barton (campbellbarton) I'm guessing this is either yours or Brechts?

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

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

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.

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.

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.

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.

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

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

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.

Brecht Van Lommel (brecht) reopened this task as Open.EditedNov 26 2017, 4:05 PM

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.

This comment was removed by Arnas Karmaza (madllama).
This comment was removed by Arnas Karmaza (madllama).

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

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!

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.

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 Van Lommel (brecht) I'm amazed at how well you manage everything! :)

@Brecht Van Lommel (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.