Creating new geometry with blend shape causes only new points to be interpolated on all subsequent new keys. #48609

Closed
opened 2016-06-08 06:12:21 +02:00 by Joseph Catrambone · 6 comments

System Information
Windows 10 Pro 64-bit (10.0 Build 10586)
DirectX Version: 12
Graphics Card: nVidia GTX 970
Graphics Driver: 10.18.13.6451
Processor: Intel Core i5-2500K
Ram: 24576MB Ram

Blender Version
Broken: 2.77a

Short description of error
If new geometry is created in a shape key, any new shape keys created after the fact will have some amount of the first key's deformation applied to them. New keys should be 'clean' and not deform, since there's no way to reset new shape keys to the default. It should also be noted that only the new geometry is interpolated on the new key, not the old geometry.

Exact steps for others to reproduce the error
Steps to Reproduce:

  1. Begin with the default scene.
  2. Create a cube.
  3. Subdivide the cube twice.
  4. Create a 'basis' shape key.
  5. Create a 'key 1' shape key.
  6. Adjust the 'key 1' value to 100%.
  7. Switch to the sculpt tool and deform the cube.
  8. Tab into edit mode and create a ring cut with Ctrl+R.
  9. Tab back into object mode and move the 'key 1' value back to 0.
  10. Create a new shape key, 'key 2'.

Expected Behavior: New shape key should match the basis key and should have no deformation applied to it.

Observed Behavior: New shape key, when dragged to 100%, applies the same interpolation as the newly created geometry from key 1. It is not currently possible to create a 'clean' key which can have additional deformation added to it.

Reproducibility: 100%

Blend file, video, and system info are attached.

system-info.txt

blender_shape_key_bug.blend

blender_shape_key_bug.gif

**System Information** Windows 10 Pro 64-bit (10.0 Build 10586) DirectX Version: 12 Graphics Card: nVidia GTX 970 Graphics Driver: 10.18.13.6451 Processor: Intel Core i5-2500K Ram: 24576MB Ram **Blender Version** Broken: 2.77a **Short description of error** If new geometry is created in a shape key, any new shape keys created after the fact will have some amount of the first key's deformation applied to them. New keys should be 'clean' and not deform, since there's no way to reset new shape keys to the default. It should also be noted that only the new geometry is interpolated on the new key, not the old geometry. **Exact steps for others to reproduce the error** Steps to Reproduce: 1) Begin with the default scene. 2) Create a cube. 3) Subdivide the cube twice. 4) Create a 'basis' shape key. 5) Create a 'key 1' shape key. 6) Adjust the 'key 1' value to 100%. 7) Switch to the sculpt tool and deform the cube. 8) Tab into edit mode and create a ring cut with Ctrl+R. 9) Tab back into object mode and move the 'key 1' value back to 0. 10) Create a new shape key, 'key 2'. Expected Behavior: New shape key should match the basis key and should have no deformation applied to it. Observed Behavior: New shape key, when dragged to 100%, applies the same interpolation as the newly created geometry from key 1. It is not currently possible to create a 'clean' key which can have additional deformation added to it. Reproducibility: 100% Blend file, video, and system info are attached. [system-info.txt](https://archive.blender.org/developer/F316396/system-info.txt) [blender_shape_key_bug.blend](https://archive.blender.org/developer/F316397/blender_shape_key_bug.blend) ![blender_shape_key_bug.gif](https://archive.blender.org/developer/F316398/blender_shape_key_bug.gif)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @JosephCatrambone

Added subscriber: @JosephCatrambone

Added subscriber: @SpectreFirst

Added subscriber: @SpectreFirst

I think I can get where your problem comes from: when you are making a loop cut, is your selected shape key is "Key 1"? It seems that if you create shape key "Key 1", select "Basis" and then make your loop cut, key 2 will not retain changes from "Key 1". Maybe I got something wrong, but I was able to replicate your problem when I was making a loop cut while "Key 1" was selected.

I think I can get where your problem comes from: when you are making a loop cut, is your selected shape key is "Key 1"? It seems that if you create shape key "Key 1", select "Basis" and then make your loop cut, key 2 will not retain changes from "Key 1". Maybe I got something wrong, but I was able to replicate your problem when I was making a loop cut while "Key 1" was selected.

That's correct, Alex. I see having "Basis" selected when adding geometry alleviates the issue (in my small-scale test) and provides a workaround for me, so I'm unblocked. Is this expected behavior?

That's correct, Alex. I see having "Basis" selected when adding geometry alleviates the issue (in my small-scale test) and provides a workaround for me, so I'm unblocked. Is this expected behavior?
Campbell Barton self-assigned this 2016-06-13 11:48:34 +02:00

Closed as duplicate of #44415

Closed as duplicate of #44415
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
3 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#48609
No description provided.