Adding vertices when Basis Shapekey is active prevents changes to the Basis from affecting other keys #96681
Labels
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#96681
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-8.1-6.3.9600-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89
Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash:
c77597cd0eWorked: (Unknown, bug exists at least as far back as 2.79b)
Short description of error
As requested by @ideasman42, this is a report of the following shapekey bug:
When vertices are added to a mesh with shapekeys when the Basis Shapekey is selected, any changes made to the Basis key will NOT propagate to other keys.
HOWEVER, if vertices are added when any key OTHER than the Basis is selected (ie. Key1), and then the Basis key is edited, any changes to the Basis WILL correctly propagate to other keys.
ADDITIONALLY, if vertices are added when the Basis Shapekey is selected, BUT Edit mode is first EXITED then RE-ENTERED before any vertex manipulation is made to the Basis key, then any changes to the Basis WILL correctly propagate to other keys.
Exact steps for others to reproduce the error
All three scenarios below (based on a new empty project) are demonstrated in this example video HERE .
1. Add a cube, add 2 shapekeys. With the "Basis" key selected, enter Edit mode and add loop cuts. Move the vertices. Select "Key1" and notice the changes to the "Basis" key have NOT affected Key1. This is the only scenario where the bug exists.
2. Add a cube, add 2 shapekeys. With the "Key1" key selected, enter Edit mode and add loop cuts. Now select the "Basis" key. Move the vertices. Select "Key1" again and notice the changes to the Basis key have affected Key1 as expected. This is one workaround.
3. Add a cube, add 2 shapekeys. With the "Basis" key selected, enter Edit mode and add loop cuts. Now EXIT Edit mode and RE-ENTER. Move the vertices. Select "Key1" and notice the changes to the Basis key have affected Key1 as expected. This is a second workaround.
P.S. Apologies for the very late report. The last 3 weeks have been heavily pre-occupied with music production. And I'm super thrilled that #44415 made it into the 3.1 release. Thanks so much to @ideasman42 and all the talented Blender devs for making this happen! :-)
Added subscribers: @ideasman42, @AdamJanz
#103427 was marked as duplicate of this issue
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @mano-wii
Added subscriber: @Art4D
Will it take us another 7 years to fix this critical bug?
Blender still breaks shapekeys if new vertices are added to Basic.
#44415 is only half fixed. The fix doesn't work if new vertices are added to Basic.
Added subscribers: @qwezxcaa, @lichtwerk, @PratikPB2123
And so, two more years have passed, and this critical bug from nine years ago is still not fixed.
Due to this bug, I can't add a new mesh to my finished character with shape keys and rig. Because at some random moment, the blender just breaks all the shape keys of the character. The blender just destroys all my work done with the new mesh because the old shape keys stop working correctly at some point.
@Art4D Yes, that definitely can be very frustrating when changes made to the mesh don't get transferred to the other keys. At the moment, the best workaround is to add any new loop cuts and extrusions to the Base Key but do NOT move the new vertices or faces (ie. if extruding, right-click to cancel so the new faces will stay in place). Then EXIT Edit Mode and re-enter Edit Mode. Now you can move your vertices and faces as you wish and the new positions will correctly propagate to the other shapekeys.
Of course, it's very easy to forget to to do this. And using "Vertex" > "Propagate to shapes" is not a viable solution in most cases, because the new vertex positions in the Base Key will OVERRIDE the other keys' existing vertex positions instead of blending with them.
So unfortunately, it's VERY crucial to follow the workaround mentioned until a much-needed fix is implemented, otherwise hours of work can be permanently lost.
Hopefully Campbell Barton @ideasman42 can shed some light on whether this bug can be addressed. It is currently not assigned to anyone.