Insert keyframe wrong with cycle-aware keying after deleting end frame #111322

Closed
opened 2023-08-20 15:45:02 +02:00 by tj2n497vxdq1ui · 6 comments

System Information
Operating system: Linux-6.4.6-arch1-1-x86_64-with-glibc2.37 64 Bits, X11 UI
Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05

Blender Version
Broken: version: 3.6.0, branch: makepkg (modified), commit date: 2023-06-27 08:08, hash: c7fc78b81ecb

Short description of error
I have an action with manual frame range, 1 to 11, with cyclic animation checked. I have cycle-aware keying on.

I'm not sure exactly when the bug starts, but eventually adding a frame at time 9 creates the keyframe at frame 4 again.

Exact steps for others to reproduce the error

I'm not sure exactly when the issue started, but roughly

  1. Cube
  2. Insert frame at time 1
  3. Turn overlay action into layer (stack?) action with the down icon button
  4. Set up manual frame range 1-11, cyclic
  5. Turn on cycle-aware keying
  6. Insert another frame at time 6, blender automagically adds a frame at time 11 to match the frame at time 1
  7. Delete the frame at time 11
  8. Move to time 9 and insert frame

7 seems to be the key. Additionally, it's impossible to add a new frame at time 11. The issue persists after closing and re-opening.
The issue disappears when cycle-aware keying is off, but comes back if I turn it back on.

I didn't try a daily build, but I searched issues to see if anything similar was reported and found nothing.

**System Information** Operating system: Linux-6.4.6-arch1-1-x86_64-with-glibc2.37 64 Bits, X11 UI Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.86.05 **Blender Version** Broken: version: 3.6.0, branch: makepkg (modified), commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` **Short description of error** I have an action with manual frame range, 1 to 11, with cyclic animation checked. I have cycle-aware keying on. I'm not sure exactly when the bug starts, but eventually adding a frame at time 9 creates the keyframe at frame 4 again. **Exact steps for others to reproduce the error** I'm not sure exactly when the issue started, but roughly 1. Cube 2. Insert frame at time 1 3. Turn overlay action into layer (stack?) action with the down icon button 4. Set up manual frame range 1-11, cyclic 5. Turn on cycle-aware keying 6. Insert another frame at time 6, blender automagically adds a frame at time 11 to match the frame at time 1 7. Delete the frame at time 11 8. Move to time 9 and insert frame 7 seems to be the key. Additionally, it's impossible to add a new frame at time 11. The issue persists after closing and re-opening. The issue disappears when cycle-aware keying is off, but comes back if I turn it back on. I didn't try a daily build, but I searched issues to see if anything similar was reported and found nothing.
898 KiB
tj2n497vxdq1ui added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-20 15:45:02 +02:00
Author

I played around a little more and it seems like the cycle-aware keying is based on the start and end frame per channel rather than the action start-end frame. If some channels have a keyframe at 11 and some have their last keyframe at 6, inserting a frame will create keyframes at 4 or 9 differently per channel.

I can understand how this is consistent with other rules, but I can't believe this is the intended UX and it makes it impossible to re-add the end frame so I'm leaving it as a bug report.

I played around a little more and it seems like the cycle-aware keying is based on the start and end frame per channel rather than the action start-end frame. If some channels have a keyframe at 11 and some have their last keyframe at 6, inserting a frame will create keyframes at 4 or 9 differently per channel. I can understand how this is consistent with other rules, but I can't believe this is the intended UX and it makes it impossible to re-add the end frame so I'm leaving it as a bug report.
Author

#54724 is probably related but since this is about released features I think it makes sense as a separate issue.

#54724 is probably related but since this is about released features I think it makes sense as a separate issue.
Author

I was playing some more, and this appears to be inconsistent depending on some internal state.

  • When you have a single frame, creating a frame after the last frame, the new frame is created and blender automatically creates an end frame at the end time of the action frame range
  • When you have two frames (before enabling manual range + cycle), creating a frame after the last frame creates the new frame but not the end frame
  • If you delete the second frame, it goes back to creating the end frame automatically on the next frame you create
  • If you manually create the end frame then delete the end frame (back to 1 frame), creating a new frame (ex at frame 6) causes blender to create the end frame
  • If you create a second frame and blender creates the end frame, then you delete both frames, then create a new frame at 6, blender creates the end frame again
  • Only if you create a non-end frame, blender automatically creates the end frame, you delete it, then create a new frame after your second frame does it not create the end frame and insert the new frame in the existing range
I was playing some more, and this appears to be inconsistent depending on some internal state. - When you have a single frame, creating a frame after the last frame, the new frame is created _and_ blender automatically creates an end frame at the end time of the action frame range - When you have two frames (before enabling manual range + cycle), creating a frame after the last frame creates the new frame but not the end frame - If you delete the second frame, it goes back to creating the end frame automatically on the next frame you create - If you manually create the end frame then delete the end frame (back to 1 frame), creating a new frame (ex at frame 6) causes blender to create the end frame - If you create a second frame and blender creates the end frame, then you delete both frames, then create a new frame at 6, blender creates the end frame again - Only if you create a non-end frame, blender automatically creates the end frame, you delete it, then create a new frame after your second frame does it not create the end frame and insert the new frame in the existing range
Member

Thanks for the report. I can confirm. Looks like behavior has changed in 4.1, need to check it.

Thanks for the report. I can confirm. Looks like behavior has changed in 4.1, need to check it.
Pratik Borhade added
Module
Animation & Rigging
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-12-14 08:16:59 +01:00

I am going to close this issue, since the feature is working as intended.
However that doesn't mean it's not a valid issue. The cyclic animation system is overly complex, hard to find/use and easy to break as a user as well as a developer.
We can hopefully come up with a better design with the new animation datamodel.

Just linking the original design task for cyclic animations for further reading
#54724: Workflow improvements for creating Animation Loops

@PratikPB2123 there is an issue with cycle aware keying in 4.1
I have a fix lined up but it needs other PRs to go through first
#116943: WIP: Fix: Issue with Cycle aware keying when inserting second key

I am going to close this issue, since the feature is working as intended. However that doesn't mean it's not a valid issue. The cyclic animation system is overly complex, hard to find/use and easy to break as a user as well as a developer. We can hopefully come up with a better design with the new animation datamodel. Just linking the original design task for cyclic animations for further reading [#54724: Workflow improvements for creating Animation Loops](https://projects.blender.org/blender/blender/issues/54724) @PratikPB2123 there is an issue with cycle aware keying in 4.1 I have a fix lined up but it needs other PRs to go through first [#116943: WIP: Fix: Issue with Cycle aware keying when inserting second key](https://projects.blender.org/blender/blender/pulls/116943)
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-01-09 17:19:30 +01:00
Member

there is an issue with cycle aware keying in 4.1, I have a fix lined up but it needs other PRs to go through first

Great! thanks :)

> there is an issue with cycle aware keying in 4.1, I have a fix lined up but it needs other PRs to go through first Great! thanks :)
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#111322
No description provided.