Baking animation on 2s ( Frame Step = 2) and with 'Overwrite Current Action' enabled, still keeps old keyframes inbetween steps. #85050
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#85050
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: Linux-5.8.0-7630-generic-x86_64-with-debian-bullseye-sid 64 Bits
Graphics card: AMD Radeon RX 5700 XT (NAVI10, DRM 3.38.0, 5.8.0-7630-generic, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.1
Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-01-18 14:02, hash:
023ebb890b
Worked: (newest version of Blender that worked as expected)
Short description of error
Baking animation on 2s ( Frame Step = 2) and with 'Overwrite Current Action' enabled, still keeps old keyframes inbetween steps. I would expect these 'inbetween' keys to be overridden as well as it should be part of the baking process.
EDIT:
It would be great to have an option in the 'bake action' that will delete keys that are not on the stepped keyframes. This way the 'baking on 2s' will be absolutely on 2s, and not have some leftover keys that will still move the character inbetween 2 baked keys.
It would be great if 'baking actions' are respecting the preferences on which interpolation mode it is set. Let's say I set it to 'constant'. then baking action should output 'constant' keys instead of bezier keys.
As discussed in the meeting with Sybren, Hjalti, Rik and Sebastian. being able to determine the keys to be baked on frames based on keys of an arbitrary object gives us the freedom to be selective on which frames should be baked and which frames should be held. Let's say want my frames to be baked on frame 2, 4, 6, 7, 8, where frame 7 is an extra key (based on the 2s retoric). By having an object (cube, bone, etc) that has already keys on the designated frames 2, 4, 6, 7, 8. This object could dictate the frames that needs key baking.
Exact steps for others to reproduce the error
#85050-cube_anim_test_baking_on_2s_v1.blend
After baking, I still see existing keys on frames inbetween the 2 steo even though 'Overwrite Current Action' is turned on.
Added subscriber: @Rikstopher
cube_anim_test_baking_on_2s_v1.blend
Here, I uploaded an example file with a simple cube and bone animation.
The armature contains 2 actions:
The result of the baked animation, it still contains it's previous keys inbetween the 2-step keyframes.
Added subscriber: @dr.sybren
Changed status from 'Needs Triage' to: 'Confirmed'
This is working as designed. It's overwriting the existing keys with new keys, but otherwise leaving the existing Action alone.
The "Overwrite Current Action" option could be made to erase the keys in the affected FCurves in the bake frame range first. That's a new feature, though. I think it would be nice as a sub-task task of #82168 (Improvements to "Bake Action..." Operator).
Added subscriber: @BClark
Hi,
Overwrite implies replace though doesn't it? It isn't call merge to current action. Is that documented that that is what it does currently somewhere? That wasn't clear to me that it was doing this.
Yes, and currently it replaces existing keys on the current action. This is of course different from replacing an entire time interval, which is what Wayde made D10392 for.
Right but it says replace the action, not replace keys, action implying replacing all keys with new baked keys based on the settings given (interval 2 or 3 etc)
Why would I want to keep anything if I am "replacing" it.
If I open a blender file and save over another file with my open one, I don't expect it to keep what was in the file I am overwriting... overwrite should overwrite, not merge.
Added subscriber: @LucianoMunoz
Agree with Brad here.
We should maybe make a list and clarify the options / terms used so we're all on the same page