Dynamicly changed weight paint does not affect Shape Keys #97767

Closed
opened 2022-05-02 09:07:26 +02:00 by Aleksander Wisniewski · 7 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.1.2, branch: addon_v3.0_octane2021 (modified), commit date: 2022-04-27 03:29, hash: 5dfefe58f0
Worked: (newest version of Blender that worked as expected)

Short description of error
If you have weight paint that is being set dynamically - for example by using dynamic paint and a shape key that uses vertex group same as the one being modified, there is no change in the shape even if weight was changed.

Exact steps for others to reproduce the error
Reproduction steps:

  1. Create sphere
  2. Create Basis and Key 1 shape keys and set value to 1
  3. Enter edit mode and modify the shape key (for example resize the sphere), then exit edit mode
  4. Add Vertex group
  5. Set the new group in the Vertex Group in the shape key
  6. Add dynamic paint, canvas, Surface Type : Weight, Output: Vertex Group : Group
  7. Add second sphere
  8. On second sphere add Dynamic Paint : Brush, surface: Volume + Proximity
  9. Create animation where one ball is 2 ball lengths apart and gets as close as to touch the other ball

Result: In weight paint mode observe that weight changes, but the shape is not affected.
Bonus round: Paint the weight paint manually and observe object changing

I have tested it on Blender 3.1 and Blender 3.0, both have this problem

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.1.2, branch: addon_v3.0_octane2021 (modified), commit date: 2022-04-27 03:29, hash: `5dfefe58f0` Worked: (newest version of Blender that worked as expected) **Short description of error** If you have weight paint that is being set dynamically - for example by using dynamic paint and a shape key that uses vertex group same as the one being modified, there is no change in the shape even if weight was changed. **Exact steps for others to reproduce the error** Reproduction steps: 1. Create sphere 2. Create Basis and Key 1 shape keys and set value to 1 3. Enter edit mode and modify the shape key (for example resize the sphere), then exit edit mode 4. Add Vertex group 5. Set the new group in the Vertex Group in the shape key 6. Add dynamic paint, canvas, Surface Type : Weight, Output: Vertex Group : Group 7. Add second sphere 8. On second sphere add Dynamic Paint : Brush, surface: Volume + Proximity 9. Create animation where one ball is 2 ball lengths apart and gets as close as to touch the other ball Result: In weight paint mode observe that weight changes, but the shape is not affected. Bonus round: Paint the weight paint manually and observe object changing I have tested it on Blender 3.1 and Blender 3.0, both have this problem

Added subscriber: @exverxes

Added subscriber: @exverxes

Added quick demonstration video showing problem: https://youtu.be/mhAbRRfYAmY

Added quick demonstration video showing problem: https://youtu.be/mhAbRRfYAmY
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

To speed up the process: please share your example .blend file, thx in advance.

To speed up the process: please share your example .blend file, thx in advance.
Member

In fact, this is the same problem as described here #90276 (ShapeKey does not "see" modified Vertex Group (e.g. proximity modifier, dynamic paint)), so this is not really a bug, more of a design limitation in current blender.
Please have a look ath the other report for details, will merge reports.

In fact, this is the same problem as described here #90276 (ShapeKey does not "see" modified Vertex Group (e.g. proximity modifier, dynamic paint)), so this is not really a bug, more of a design limitation in current blender. Please have a look ath the other report for details, will merge reports.
Member

Closed as duplicate of #90276

Closed as duplicate of #90276
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#97767
No description provided.