"Smooth Vertex Weights" uses wrong state if settings are changed #119740

Closed
opened 2024-03-21 13:41:05 +01:00 by RavenWorks · 1 comment

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: unknown

Short description of error
When I'm in weight painting mode, and I do Weights > Smooth, the initial result is as I expect. But if I go into the popup in the lower-left and change any of the values ("subset", "factor", etc), those new settings will be applied to a very different state of the document -- sometimes it's just a different vertex group than the one I had selected, but sometimes it turns on 'paint mask' even though I had it off!

Exact steps for others to reproduce the error
Unfortunately, I can't reproduce this in a new document, and I'm not at liberty to share the .blend file that it's occurring in. I know that's not ideal, but I'll describe my steps regardless in case it gives any clues, or someone else is in a better position to provide a reproduction project:

  1. In object mode, select a mesh with weight paint data
  2. Enter weight paint mode
  3. Select the vertex group that you would like to operate on
  4. In the 'weights' menu, select 'smooth'
  5. The options popup opens in the lower left, and a smooth is performed on the data according to its listed options.
  6. Change the options in any way you see fit (i.e. change the number of iterations).
  7. Blender suddenly switches to a DIFFERENT set of data on the same mesh, and performs the new options there. As mentioned before, I have encountered different changes at this point -- one time it would turn on 'paint mask' mode even though I had it off, but more often it switches to a different vertex group, that I had been working on recently.
  8. At this point, changing the options "works fine" other than the fact that it's working on the wrong data; and if you try and switch to the data that you want to be working on, changing the settings again will always force you back to the incorrect data.
  9. Click somewhere else in order to close the 'smooth vertex weights' popup.
  10. Press undo, to restore the state of the weights before these bugged changes to them.
  11. Switch back to the vertex group that you actually wanted to change.
  12. Do 'weights' > 'smooth' again.
  13. The state of the settings is as you left it last time, and it's being performed on the correct data this time, because you haven't touched the options yet!
  14. Change any of the settings, and suddenly it will jump to the wrong state again.

Steps 13 and 14 mean that there is a workaround -- put the settings how you want them on the wrong data, then undo, then invoke the command again -- but it's awfully tedious to iterate that way.

It's worth mentioning, while I was performing the steps over and over to settle on a writeup, the bug would start and stop happening at random; a few times, everything started working completely normally without warning, but then it would start behaving strangely again just as suddenly. I think it may have had to do with me moving to edit mode and back, but I haven't been able to reproduce it consistently?

It's also worth mentioning: I'm pretty sure that all of the bugged states that the command keeps jumping me into, are states that I'd been in recently (but not very recently) -- I had been working with paint mask mode earlier in the session where it was forcing that on, and the vertex group that it kept forcing me to was one that I had been working on earlier in the session. Could it have something to do with undo states/

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: unknown **Short description of error** When I'm in weight painting mode, and I do Weights > Smooth, the initial result is as I expect. But if I go into the popup in the lower-left and change any of the values ("subset", "factor", etc), those new settings will be applied to a very different state of the document -- sometimes it's just a different vertex group than the one I had selected, but sometimes it turns on 'paint mask' even though I had it off! **Exact steps for others to reproduce the error** Unfortunately, I can't reproduce this in a new document, and I'm not at liberty to share the .blend file that it's occurring in. I know that's not ideal, but I'll describe my steps regardless in case it gives any clues, or someone else is in a better position to provide a reproduction project: 1. In object mode, select a mesh with weight paint data 2. Enter weight paint mode 3. Select the vertex group that you would like to operate on 4. In the 'weights' menu, select 'smooth' 5. The options popup opens in the lower left, and a smooth is performed on the data according to its listed options. 6. Change the options in any way you see fit (i.e. change the number of iterations). 7. Blender suddenly switches to a DIFFERENT set of data on the same mesh, and performs the new options there. As mentioned before, I have encountered different changes at this point -- one time it would turn on 'paint mask' mode even though I had it off, but more often it switches to a different vertex group, that I had been working on recently. 8. At this point, changing the options "works fine" other than the fact that it's working on the wrong data; and if you try and switch to the data that you *want* to be working on, changing the settings again will always force you back to the incorrect data. 9. Click somewhere else in order to close the 'smooth vertex weights' popup. 10. Press undo, to restore the state of the weights before these bugged changes to them. 11. Switch back to the vertex group that you actually wanted to change. 12. Do 'weights' > 'smooth' again. 13. The state of the settings is as you left it last time, and it's being performed on the correct data this time, because you haven't touched the options yet! 14. Change any of the settings, and suddenly it will jump to the wrong state again. Steps 13 and 14 mean that there *is* a workaround -- put the settings how you want them on the *wrong* data, then undo, then invoke the command again -- but it's awfully tedious to iterate that way. It's worth mentioning, while I was performing the steps over and over to settle on a writeup, the bug would start and stop happening at random; a few times, everything started working completely normally without warning, but then it would start behaving strangely again just as suddenly. I think it may have had to do with me moving to edit mode and back, but I haven't been able to reproduce it consistently? It's also worth mentioning: I'm pretty sure that all of the bugged states that the command keeps jumping me into, are states that I'd been in recently (but not very recently) -- I had been working with paint mask mode earlier in the session where it was forcing that on, and the vertex group that it kept forcing me to was one that I had been working on earlier in the session. Could it have something to do with undo states/
RavenWorks added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-03-21 13:41:06 +01:00
Member

This unfortunately looks like an incarnation of longstanding #69760.

Will close as a duplicate, please subscribe and raise your voice in #69760 if you want further updates of have this fixed for good...

This unfortunately looks like an incarnation of longstanding #69760. Will close as a duplicate, please subscribe and raise your voice in #69760 if you want further updates of have this fixed for good...
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2024-03-21 14:08:09 +01:00
Philipp Oeser added
Status
Duplicate
and removed
Status
Archived
labels 2024-03-21 14:08:21 +01:00
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
2 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#119740
No description provided.