Draw brush with 0 weight doesn't show when using zero weight overlay #120618

Closed
opened 2024-04-13 21:29:36 +02:00 by Daniel Ulrich · 5 comments

System Information
Operating system: Windows 10
Graphics card: Nvidia 4080

Blender Version
Broken: 4.1
Worked: I don't think it ever has
When using the draw brush with 0 weight with Zero Weights overlay enabled, the overlay wouldn't show black (0) weights. When using the subtract brush it would show them just fine

Exact steps for others to reproduce the error
Add any object, create a vertex group with a value of 1. Enable Zero Weights overlay on active. Using the draw brush with the weight set to 0 try painting the weights. Now try the subtract brush set to 1.

**System Information** Operating system: Windows 10 Graphics card: Nvidia 4080 **Blender Version** Broken: 4.1 Worked: I don't think it ever has When using the draw brush with 0 weight with Zero Weights overlay enabled, the overlay wouldn't show black (0) weights. When using the subtract brush it would show them just fine **Exact steps for others to reproduce the error** Add any object, create a vertex group with a value of 1. Enable Zero Weights overlay on active. Using the draw brush with the weight set to 0 try painting the weights. Now try the subtract brush set to 1.
Daniel Ulrich added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-04-13 21:29:36 +02:00
Member

Can confirm. And looks like whether the vertex weight is displayed as black or not they are still in the vertex group.

Can confirm. And looks like whether the vertex weight is displayed as black or not they are still in the vertex group.
YimingWu added
Module
Sculpt, Paint & Texture
Status
Confirmed
and removed
Status
Needs Triage
labels 2024-04-15 04:28:45 +02:00
Member

Took a bit digging, looks like it's just that mixing is not as strong due to pressure and brush fall off. So if you Draw the 0 weight brush repeatedly, the value would eventually return to completely 0. So considering this not to be a bug.

I made a quick print for each time a specific vertex is touched, you can see as the value gets smaller, it's converging to 0 slower, but eventually it gets there.

0.938686490
0.996896684
0.943380237
0.246416599
0.134316921
0.019344907
0.011724274
0.009167921
0.001208893
0.001098510
0.000327714
0.000049107
0.000000482
0.000000003
0.000000003
0.000000003
0.000000002
0.000000001
0.000000000
0.000000000

Will close this issue for now since it's actually not a bug, but feel free to comment further :D

Took a bit digging, looks like it's just that mixing is not as strong due to pressure and brush fall off. So if you `Draw` the 0 weight brush repeatedly, the value would eventually return to completely 0. So considering this not to be a bug. I made a quick print for each time a specific vertex is touched, you can see as the value gets smaller, it's converging to 0 slower, but eventually it gets there. ``` 0.938686490 0.996896684 0.943380237 0.246416599 0.134316921 0.019344907 0.011724274 0.009167921 0.001208893 0.001098510 0.000327714 0.000049107 0.000000482 0.000000003 0.000000003 0.000000003 0.000000002 0.000000001 0.000000000 0.000000000 ``` Will close this issue for now since it's actually not a bug, but feel free to comment further :D
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-04-15 05:15:19 +02:00
Author

Using a mouse it took me 70 clicks and I was getting nowhere close to what 1 click of subtract was giving me. Arguably the 2 should be consistent. Not sure if massive inconsistencies qualify as a bug though. I mean we can just sweep it under the rug and hope for someone to pick it up by chance sometime in the future, not sure what that would accomplish.

Using a mouse it took me 70 clicks and I was getting nowhere close to what 1 click of subtract was giving me. Arguably the 2 should be consistent. Not sure if massive inconsistencies qualify as a bug though. I mean we can just sweep it under the rug and hope for someone to pick it up by chance sometime in the future, not sure what that would accomplish.
3.6 MiB
Member

You could try setting the falloff to constant and you should be able to get rid of it in one click.

You could try setting the falloff to constant and you should be able to get rid of it in one click.
Author

That doesn't make it consistent, only more tedious (having to set falloff just because of 1 operation). I could also not use the draw bursh but switch to subtract. The point was to report something that's broken, and it still is.

I understand your reasoning, and if the bug report regulations say to ignore anything that doesn't fall under certain criteria I understand of course. It's just not the best approach imo.

That doesn't make it consistent, only more tedious (having to set falloff just because of 1 operation). I could also not use the draw bursh but switch to subtract. The point was to report something that's broken, and it still is. I understand your reasoning, and if the bug report regulations say to ignore anything that doesn't fall under certain criteria I understand of course. It's just not the best approach imo.
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#120618
No description provided.