Shape key keyframes won't change in value. They keep snapping back to the original keyframe's value #60598

Closed
opened 2019-01-17 21:37:30 +01:00 by Chris Steinberger · 17 comments

System Information
Operating system: Windows 10
Graphics card: GTX Geforce 770

Blender Version
(blender2.8, 2019-01-17 10:44)

When I try to animate shape keys, the value keeps snapping back to whatever the original keyframe was. Granted, I'm fairly new, so I can't tell whether this is a bug or a mistake on my end. I had the same issue with a previous build (Blender 2.8 2019-12-26 22:09). Doesn't matter whether or not the record button is enabled. The layer is unlocked (it let me edit the value to set the first keyframe).

To make it easier to explain, here's a video capture of the problem: https://youtu.be/mcGlZgx5Y1s

**System Information** Operating system: Windows 10 Graphics card: GTX Geforce 770 **Blender Version** (blender2.8, 2019-01-17 10:44) When I try to animate shape keys, the value keeps snapping back to whatever the original keyframe was. Granted, I'm fairly new, so I can't tell whether this is a bug or a mistake on my end. I had the same issue with a previous build (Blender 2.8 2019-12-26 22:09). Doesn't matter whether or not the record button is enabled. The layer is unlocked (it let me edit the value to set the first keyframe). To make it easier to explain, here's a video capture of the problem: https://youtu.be/mcGlZgx5Y1s

Added subscriber: @CStein

Added subscriber: @CStein
Member

Added subscriber: @Mets

Added subscriber: @Mets
Member

This seems like normal behaviour, and should be affecting all types of animation, not just shape keys.

Since you already keyframed that value, any changes you make to that value are, logically, overwritten by that keyframe when the timeline moves, unless you say otherwise, by placing a new keyframe.

If you find this unintuitive for your workflow, take a look at the Auto-Keying option. This will automatically create a keyframe for you when you move something(including shape key values). It can be quite dangerous if you forget about it and unwittingly move things around without meaning to put down a keyframe.

Hope that helps, let me know if I misunderstood the issue.

This seems like normal behaviour, and should be affecting all types of animation, not just shape keys. Since you already keyframed that value, any changes you make to that value are, logically, overwritten by that keyframe when the timeline moves, unless you say otherwise, by placing a new keyframe. If you find this unintuitive for your workflow, take a look at the Auto-Keying option. This will automatically create a keyframe for you when you move something(including shape key values). It can be quite dangerous if you forget about it and unwittingly move things around without meaning to put down a keyframe. Hope that helps, let me know if I misunderstood the issue.

Thanks for the response but I don't think that's what's happening here. Coming from video, I'm familiar with keyframes and auto-keying, and this is odd behavior. I'm saying when I try to adjust the value at any point in the timeline after the first keyframe is set, the value will snap back immediately. Blender will not let me adjust the value at all. It doesn't matter if I set the second keyframe before or after adjusting the shape key value, or whether or not I use auto-keying. The value will not change.

Thanks for the response but I don't think that's what's happening here. Coming from video, I'm familiar with keyframes and auto-keying, and this is odd behavior. I'm saying when I try to adjust the value at any point in the timeline after the first keyframe is set, the value will snap back immediately. Blender will not let me adjust the value at all. It doesn't matter if I set the second keyframe before or after adjusting the shape key value, or whether or not I use auto-keying. The value will not change.

Oddly enough I found one exception. I had an audio track in the video sequencer so I could time the animation to the audio. When I deleted the audio and tried to make a new keyframe with a different value, Blender let me make the adjustment. But now it's back to how it was before, snapping back to whatever value it's currently set to.

Oddly enough I found one exception. I had an audio track in the video sequencer so I could time the animation to the audio. When I deleted the audio and tried to make a new keyframe with a different value, Blender let me make the adjustment. But now it's back to how it was before, snapping back to whatever value it's currently set to.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Cannot reproduce here [doing this from scratch]

See #60598.blend

But we have a couple of reports that are similar in that values snap back after a keyframe has been inserted (for an [incomplete] list, see #60559)

So @CStein : could you share your blendfile, so we can have a look and reproduce?

Marking as incomplete until we have access to that file

Cannot reproduce here [doing this from scratch] See [#60598.blend](https://archive.blender.org/developer/F6326795/T60598.blend) But we have a couple of reports that are similar in that values snap back after a keyframe has been inserted (for an [incomplete] list, see #60559) So @CStein : could you share your blendfile, so we can have a look and reproduce? Marking as incomplete until we have access to that file

Sure. I simplified the project a bit and just left the object I'm having issues with. Gave it another test and it's still coming up with the same problem.

Keyframe Bug.blend

I tested the #60598 file you attached and that's working perfectly.

Sure. I simplified the project a bit and just left the object I'm having issues with. Gave it another test and it's still coming up with the same problem. [Keyframe Bug.blend](https://archive.blender.org/developer/F6329254/Keyframe_Bug.blend) I tested the #60598 file you attached and that's working perfectly.
Member

Can confirm in that file indeed....

Can confirm in that file indeed....

This issue was referenced by 83f8f44791

This issue was referenced by 83f8f44791374dd051728e44d89fbdeee15c60aa

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Added subscriber: @LizzyKoopa

Added subscriber: @LizzyKoopa

Okay, so i found a way around this bug, as one of my animation was having issues with the same problem you are facing.

How i got around it was i selected all of my character, ctrl - c and opened up a older version of blender like 2.79
i pasted my character in there and adjusted the shape keys there, as well as finished my animation there as it is more stable currently.
after i was finished i did the same ctrl - c after selecting my character and deleted the one in 2.8 and pasted the one i now had in 2.79 with the changed shape keys.

while its a hassle and i hope this bug is fixed, it was the only way and answer i found on this particular issue i think you are currently going through.

Okay, so i found a way around this bug, as one of my animation was having issues with the same problem you are facing. How i got around it was i selected all of my character, ctrl - c and opened up a older version of blender like 2.79 i pasted my character in there and adjusted the shape keys there, as well as finished my animation there as it is more stable currently. after i was finished i did the same ctrl - c after selecting my character and deleted the one in 2.8 and pasted the one i now had in 2.79 with the changed shape keys. while its a hassle and i hope this bug is fixed, it was the only way and answer i found on this particular issue i think you are currently going through.

Added subscriber: @Barblitzor

Added subscriber: @Barblitzor

Hey, in case anyone's still having this issue, I've got a solution of my own.
So the slider doesn't appear to be working, but fortunately you can type into the slider.
Well, it still doesn't work in most cases, but if you use the Auto-key thing, it'll work.
So yeah, just turn on the auto thing, then type the values of your stuff, make sure you do actually click the keyframe button next to the slider though, and it should work, worked for me.
Only problem is that if you want a precise value for your shape key, you're gonna have to go through a bunch of numbers.
Hope this helped!

Hey, in case anyone's still having this issue, I've got a solution of my own. So the slider doesn't appear to be working, but fortunately you can type into the slider. Well, it still doesn't work in most cases, but if you use the Auto-key thing, it'll work. So yeah, just turn on the auto thing, then type the values of your stuff, make sure you do actually click the keyframe button next to the slider though, and it should work, worked for me. Only problem is that if you want a precise value for your shape key, you're gonna have to go through a bunch of numbers. Hope this helped!

Added subscriber: @chinchisei

Added subscriber: @chinchisei

I just have find out where the problem is in my case.
If I set my scene>dimensions>time remapping back to : old 100 new 100 (befor it was old 22 new 100)
and it works well.

I just have find out where the problem is in my case. If I set my scene>dimensions>time remapping back to : old 100 new 100 (befor it was old 22 new 100) and it works well.
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
8 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#60598
No description provided.