Weight paint mode "Levels" option changes active vertexgroup after execution #73302

Closed
opened 2020-01-21 20:47:29 +01:00 by Todd Gillissie · 15 comments

System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d4
Worked: (optional)

Short description of error
Trying to set vertex group levels, the active group keeps changing automatically and unpredictably.

Exact steps for others to reproduce the error
See attached video.
Setting the weight level of a vertex group is very un-intuitive, and even when following the correct steps, often doesn't work as expected.

  1. Go into weight paint mode.
  2. Select a vertex group.
  3. Choose menu option Weights/Levels.
  4. Choose "Active Group" for "Subset", and make some changes.
  5. Sometimes, a different group is automatically selected and the changes applied to instead of the group that was selected when choosing the menu option.
    Weight Levels 720.mov
**System Information** Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: `f1aa4d18d4` Worked: (optional) **Short description of error** Trying to set vertex group levels, the active group keeps changing automatically and unpredictably. **Exact steps for others to reproduce the error** See attached video. Setting the weight level of a vertex group is very un-intuitive, and even when following the correct steps, often doesn't work as expected. 1. Go into weight paint mode. 2. Select a vertex group. 3. Choose menu option Weights/Levels. 4. Choose "Active Group" for "Subset", and make some changes. 5. Sometimes, a different group is automatically selected and the changes applied to instead of the group that was selected when choosing the menu option. [Weight Levels 720.mov](https://archive.blender.org/developer/F8292640/Weight_Levels_720.mov)
Author

Added subscriber: @Gillissie

Added subscriber: @Gillissie
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Can confirm, checking...

Can confirm, checking...
Member

Setting the weight level of a vertex group is very un-intuitive

Not sure about this, if it was staying on the vertexgroup which was selected when executing the operator [aka: if the confirmed bug would be resolved], what would be so "un-intuitive"?

> Setting the weight level of a vertex group is very un-intuitive Not sure about this, if it was staying on the vertexgroup which was selected when executing the operator [aka: if the confirmed bug would be resolved], what would be so "un-intuitive"?
Member

The (unwanted) changing of the vertexgroup after execution is only happening if the user actually changed the vertexgroup directly before the execution
This is the same issue as #69760 (Undo/Adjust Last Operation: vertex and weightpaint operators/strokes undo more then they should (change back any setting changed prior to execution)), will merge these reports...

In #73302#855490, @lichtwerk wrote:

Setting the weight level of a vertex group is very un-intuitive

Not sure about this, if it was staying on the vertexgroup which was selected when executing the operator [aka: if the confirmed bug would be resolved], what would be so "un-intuitive"?

@Gillissie : if there is another issue that is not covered by #69760, please report this seperately, thx

The (unwanted) changing of the vertexgroup after execution is only happening if the user actually changed the vertexgroup directly before the execution This is the same issue as #69760 (Undo/Adjust Last Operation: vertex and weightpaint operators/strokes undo more then they should (change back any setting changed prior to execution)), will merge these reports... > In #73302#855490, @lichtwerk wrote: >> Setting the weight level of a vertex group is very un-intuitive > Not sure about this, if it was staying on the vertexgroup which was selected when executing the operator [aka: if the confirmed bug would be resolved], what would be so "un-intuitive"? @Gillissie : if there is another issue that is not covered by #69760, please report this seperately, thx
Philipp Oeser changed title from Weight paint mode "Levels" option has really bad UI/UX to Weight paint mode "Levels" option changes active vertexgroup after execution 2020-01-22 10:02:39 +01:00
Member

Closed as duplicate of #69760

Closed as duplicate of #69760
Author

It's unintuitive because it's very unclear how the tool panel works.
Here's how it currently works (if it worked properly)...

  1. Select a vertex group.
  2. Choose the "Levels" menu item.
  3. Set the desired values in the tool panel.
  4. There is no confirmation button, or any other clear way to dismiss the tool panel after you've set the values you want.
  5. Choose another vertex group.
  6. Set the values in the tool panel. What? It affects the previously selected vertex group instead?
    6a. To make it work, you have to again select the "Levels" menu item after selecting the next vertex group, although there is NO DIFFERENCE in how it appears on the screen. No indication of what vertex group the panel is affecting.

To make it more intuitive, the tool panel would have a way to confirm/dismiss the input values for the selected vertex group, OR the panel would automatically disappear when selecting a different vertex group, forcing you to choose the Levels menu option again, making it clear that the new panel is for the newly selected vertex group.

It's unintuitive because it's very unclear how the tool panel works. Here's how it currently works (if it worked properly)... 1. Select a vertex group. 2. Choose the "Levels" menu item. 3. Set the desired values in the tool panel. 4. There is no confirmation button, or any other clear way to dismiss the tool panel after you've set the values you want. 5. Choose another vertex group. 6. Set the values in the tool panel. What? It affects the previously selected vertex group instead? 6a. To make it work, you have to again select the "Levels" menu item after selecting the next vertex group, although there is NO DIFFERENCE in how it appears on the screen. No indication of what vertex group the panel is affecting. To make it more intuitive, the tool panel would have a way to confirm/dismiss the input values for the selected vertex group, OR the panel would automatically disappear when selecting a different vertex group, forcing you to choose the Levels menu option again, making it clear that the new panel is for the newly selected vertex group.
Author

Please re-open this ticket as originally reported, with my additional explanation of the unintuitive nature of the tool.

Please re-open this ticket as originally reported, with my additional explanation of the unintuitive nature of the tool.
Member

Choose another vertex group.
Set the values in the tool panel. What? It affects the previously selected vertex group instead?

This is the bug already reported in #69760 (you execute the operator, and if you changed the vertexgroup right before that it will undo that change as well resulting in this weird behavior, definitely a bug!)

There is no confirmation button, or any other clear way to dismiss the tool panel after you've set the values you want.
To make it work, you have to again select the "Levels" menu item after selecting the next vertex group, although there is NO DIFFERENCE in how it appears on the screen. No indication of what vertex group the panel is affecting.
To make it more intuitive, the tool panel would have a way to confirm/dismiss the input values for the selected vertex group, OR the panel would automatically disappear when selecting a different vertex group, forcing you to choose the Levels menu option again, making it clear that the new panel is for the newly selected vertex group.

This is all behaving as designed atm. The Adjust Last Operation panel stays as long as you dont execute another operator. Selecting a vertexgroup is not an operator (in contrast to e.g. selecting a vertex - in which case the panel would close), so this panel stays open. In the particular case of this report, this is a bit unintuitive and maybe can be improved upon in the future, but it is not considered a bug atm...
When the real bug will be fixed, this will also be a bit less of an issue.
A "confirm" type of button would not really work out nicely since you wont see your changes in realtime then...

> Choose another vertex group. > Set the values in the tool panel. What? It affects the previously selected vertex group instead? This is the bug already reported in #69760 (you execute the operator, and if you changed the vertexgroup right before that it will undo that change as well resulting in this weird behavior, definitely a bug!) > There is no confirmation button, or any other clear way to dismiss the tool panel after you've set the values you want. > To make it work, you have to again select the "Levels" menu item after selecting the next vertex group, although there is NO DIFFERENCE in how it appears on the screen. No indication of what vertex group the panel is affecting. > To make it more intuitive, the tool panel would have a way to confirm/dismiss the input values for the selected vertex group, OR the panel would automatically disappear when selecting a different vertex group, forcing you to choose the Levels menu option again, making it clear that the new panel is for the newly selected vertex group. This is all behaving as designed atm. The `Adjust Last Operation` panel stays as long as you dont execute another operator. Selecting a vertexgroup is not an operator (in contrast to e.g. selecting a vertex - in which case the panel would close), so this panel stays open. In the particular case of this report, this is a bit unintuitive and maybe can be improved upon in the future, but it is not considered a bug atm... When the real bug will be fixed, this will also be a bit less of an issue. A "confirm" type of button would not really work out nicely since you wont see your changes in realtime then...
Author

The panel could still operate exactly as it does, with realtime feedback, but the ability to dismiss the panel when finished would be the expected design. I've never seen any other software behave the way that tool panel does, where it just sits there forever after you're done, potentially allowing for further accidental changes. As suggested, selecting a different vertex group should make it go away too, especially if selecting a vertex makes it go away already. Consistency is good.

The panel could still operate exactly as it does, with realtime feedback, but the ability to dismiss the panel when finished would be the expected design. I've never seen any other software behave the way that tool panel does, where it just sits there forever after you're done, potentially allowing for further accidental changes. As suggested, selecting a different vertex group should make it go away too, especially if selecting a vertex makes it go away already. Consistency is good.
Member

In #73302#856094, @Gillissie wrote:
The panel could still operate exactly as it does, with realtime feedback, but the ability to dismiss the panel when finished would be the expected design. I've never seen any other software behave the way that tool panel does, where it just sits there forever after you're done, potentially allowing for further accidental changes. As suggested, selecting a different vertex group should make it go away too, especially if selecting a vertex makes it go away already. Consistency is good.

Probably agree here (at least for some situations), but still not a bug...
Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

> In #73302#856094, @Gillissie wrote: > The panel could still operate exactly as it does, with realtime feedback, but the ability to dismiss the panel when finished would be the expected design. I've never seen any other software behave the way that tool panel does, where it just sits there forever after you're done, potentially allowing for further accidental changes. As suggested, selecting a different vertex group should make it go away too, especially if selecting a vertex makes it go away already. Consistency is good. Probably agree here (at least for some situations), but still not a bug... Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Author

Ok, I can post in the requests. I always get the feeling that they aren't looked at though.
Question on this topic... what is the expected behavior if the tool panel is showing for a vertex group operation, then you select a different vertex group and make changes to the still-showing tool panel?

Ok, I can post in the requests. I always get the feeling that they aren't looked at though. Question on this topic... what is the expected behavior if the tool panel is showing for a vertex group operation, then you select a different vertex group and make changes to the still-showing tool panel?

Added subscriber: @Geeky

Added subscriber: @Geeky

The bug mentioned in this thread is still not fixed in blender 2.91.0 as well. Even there are few more issues related with "Levels" which we're facing.
Can any moderator please guide me to the right files where I can edit the "Levels" in blender source and fix it?
In our case we've been encouraging our art team to switch to Blender and issues like these are quite annoying.

The bug mentioned in this thread is still not fixed in blender 2.91.0 as well. Even there are few more issues related with "Levels" which we're facing. Can any moderator please guide me to the right files where I can edit the "Levels" in blender source and fix it? In our case we've been encouraging our art team to switch to Blender and issues like these are quite annoying.
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
3 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#73302
No description provided.