Page MenuHome

Bevel Tool cycling through percent mode locks numerical input
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-09-07 08:12, hash: rBb351607996e4
Worked: (newest version of Blender that worked as expected)

Short description of error
In edit mode, if you input a precise value for a bevel (edge bevel tool), like lets say 0,5, and then cycle through the modes (M-key), after cycling past the percent mode, it resets your numerical input to 0, and you cannot change it anymore.

Depending on what value you have input, and whether you have also moved your mouse or not, gives different results. Sometimes it resets to 0, sometimes to another number. In any case, it is then frozen, and you cannot change it.

Exact steps for others to reproduce the error

Version 1, without mouse movement:

  • Add a cube
  • In edit mode, start the edge bevel tool (Ctrl + B)
  • Input a bevel value, like 0,1
  • Press M several times to cycles through modes.
  • The value has reset to 0.
  • Try deleting the input value (backspace) or writing any other number. It is locked.
  • Try moving the mouse. No effect.

Version 2, with mouse movement:

  • Add a cube
  • In edit mode, start the edge bevel tool (Ctrl + B)
  • Move your mouse around
  • Input a bevel value, like 0,1
  • Press M several times to cycles through modes.
  • The value has reset to some other value, probably based on the mouse position.
  • Try deleting the input value (backspace) or writing any other number. It is locked.
  • Try moving the mouse. No effect.

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Wed, Sep 16, 5:30 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I confirm that the Percent mode messes up the entered value.