Shape Key editing not working as expected. #81644

Closed
opened 2020-10-12 09:03:29 +02:00 by Luke Costello · 6 comments

System Information
Operating system: Windows-10-10.0.17134-SP0 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: (newest version of Blender that worked as expected)

Short description of error
Experiencing a bug where editing the vertices of a dependent shape key changes the vertices of the basis shape key.

Exact steps for others to reproduce the error
go into edit mode of outerwall with key 1 selected, move a vertex. Then select the basis shape key and observe that it is behaving as though it is dependent. This isn't because the key 1 is actually the basis because if you move a vertex in the basis it also effects key 1 as you'd expect.

badshapekeys.blend

on an unrelated note, I have Mesh: LoopTools enabled and none of the functions are searchable.

**System Information** Operating system: Windows-10-10.0.17134-SP0 64 Bits Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: (newest version of Blender that worked as expected) **Short description of error** Experiencing a bug where editing the vertices of a dependent shape key changes the vertices of the basis shape key. **Exact steps for others to reproduce the error** go into edit mode of outerwall with key 1 selected, move a vertex. Then select the basis shape key and observe that it is behaving as though it is dependent. This isn't because the key 1 is actually the basis because if you move a vertex in the basis it also effects key 1 as you'd expect. [badshapekeys.blend](https://archive.blender.org/developer/F8981594/badshapekeys.blend) on an unrelated note, I have Mesh: LoopTools enabled and none of the functions are searchable.
Author

Added subscriber: @lukostello

Added subscriber: @lukostello
Author

I found out how I created this effect.

Make a mesh, create a basis key, Key1, and Key 2 shape keys. Delete the basis shape key. Move Key 2 up 1, then make Key 1 relative to Key 2.

I do this maneuver a lot because a lot of the time I want to change the basis shape key but not any of the dependent shape keys so I make a copy of the basis, do the changes, then delete the old one and make all the other shape keys relative to the new one. So its important that this work as expected.

I found out how I created this effect. Make a mesh, create a basis key, Key1, and Key 2 shape keys. Delete the basis shape key. Move Key 2 up 1, then make Key 1 relative to Key 2. I do this maneuver a lot because a lot of the time I want to change the basis shape key but not any of the dependent shape keys so I make a copy of the basis, do the changes, then delete the old one and make all the other shape keys relative to the new one. So its important that this work as expected.
Author

I can get around it for now by turning up Shape Key 1 to 1.0 doing new shape from mix then using that copy where I would have otherwise used Shape Key 1. Even though they are both relative to Key 2. What I suspect is happening is that when you delete the basis shape key Key 1 becomes the new basis shape for key 2 and this stays true after you move key 2 upward and switch the basis of Key 1 to Key 2. Which is why its solved by making a copy of Key 1 because Key 2's basis is Key 1 and not the copy of Key 1.

Seems the solution is when a key is moved to the top remove any shape keys it was set to be relative to, or just ignore the one that had been set.

I can get around it for now by turning up Shape Key 1 to 1.0 doing new shape from mix then using that copy where I would have otherwise used Shape Key 1. Even though they are both relative to Key 2. What I suspect is happening is that when you delete the basis shape key Key 1 becomes the new basis shape for key 2 and this stays true after you move key 2 upward and switch the basis of Key 1 to Key 2. Which is why its solved by making a copy of Key 1 because Key 2's basis is Key 1 and not the copy of Key 1. Seems the solution is when a key is moved to the top remove any shape keys it was set to be relative to, or just ignore the one that had been set.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Thanks for the report.
It is actually a duplicate of the #79892 (After swapping the basis shape key to another one, the former basis key still affects the new one).
So I'll merge them.

Thanks for the report. It is actually a duplicate of the #79892 (After swapping the basis shape key to another one, the former basis key still affects the new one). So I'll merge them.

Closed as duplicate of #79892

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