Transforming keyframes in dope sheet causes weird result in graph editor #38692

Closed
opened 2014-02-18 01:15:58 +01:00 by Sam Brubaker · 6 comments

Version: 2.69 official (win 64)

How to reproduce: In the dope sheet of the provided .blend file, select some keyframes and grab/duplicate them. Notice that as you slide those keyframes in the dope sheet, weird, impossible f-curves show up in the graph editor.

Once you left click to drop the keyframes, the curve goes back to normal. This bug is a very minor one, as it has no real effect on the animation. It only affects the appearance of the f-curves during transformation.

Keyframe_Bug.blend

Version: 2.69 official (win 64) How to reproduce: In the dope sheet of the provided .blend file, select some keyframes and grab/duplicate them. Notice that as you slide those keyframes in the dope sheet, weird, impossible f-curves show up in the graph editor. Once you left click to drop the keyframes, the curve goes back to normal. This bug is a very minor one, as it has no real effect on the animation. It only affects the appearance of the f-curves during transformation. [Keyframe_Bug.blend](https://archive.blender.org/developer/F77864/Keyframe_Bug.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @rocketman

Added subscriber: @rocketman
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Joshua Leung self-assigned this 2014-02-18 04:24:36 +01:00
Member

Without (needing to) checking the file, this sounds like it's simply a case of the keyframes not being sorted until after the transform is completed.

The F-Curve drawing is highly dependent on the keyframes in the curve being in the correct order. For transforms initiated in the Graph Editor, we had to add an extra sorting step after each transform step/update. However, currently, we don't do the same for the Dopesheet as 1) most of the time no-one will notice that it's going weird (since the curves aren't shown there), and 2) introducing this sorting step adds a significant amount of complexity to the code (since we need to keep track of what moved and what hasn't, fiddle all that around, hook it up, etc. etc.). Admittedly, this overhead is one of the reasons updates/tweaks/changes to the Graph Editor transform code are few and far between these days.

(Perhaps the only scenario when people are likely to notice that the curves are going wacko are if they use the default Animation workspace, which shows both editors one on top of the other. Then again, I don't believe that this is the best way to use these editors, and it's definitely not how they were designed...)

Now, unless we get a stream of reports that complain about the stuff jiggling around erratically in the viewport or elsewhere (AND causing significant issues due to that) while transforming keyframes in the dopesheet (from having the time cursor placed in the wrong place), it's probably not worth the trouble to fix this.

Without (needing to) checking the file, this sounds like it's simply a case of the keyframes not being sorted until after the transform is completed. The F-Curve drawing is highly dependent on the keyframes in the curve being in the correct order. For transforms initiated in the Graph Editor, we had to add an extra sorting step after each transform step/update. However, currently, we don't do the same for the Dopesheet as 1) most of the time no-one will notice that it's going weird (since the curves aren't shown there), and 2) introducing this sorting step adds a significant amount of complexity to the code (since we need to keep track of what moved and what hasn't, fiddle all that around, hook it up, etc. etc.). Admittedly, this overhead is one of the reasons updates/tweaks/changes to the Graph Editor transform code are few and far between these days. (Perhaps the only scenario when people are likely to notice that the curves are going wacko are if they use the default Animation workspace, which shows both editors one on top of the other. Then again, I don't believe that this is the best way to use these editors, and it's definitely not how they were designed...) Now, unless we get a stream of reports that complain about the stuff jiggling around erratically in the viewport or elsewhere (AND causing significant issues due to that) while transforming keyframes in the dopesheet (from having the time cursor placed in the wrong place), it's probably not worth the trouble to fix this.
Author

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Author

Thanks, @JoshuaLeung! I believe you if you say that this issue is more trouble than it is worth to fix.

One small point, though: More often than not, I do have both the Graph Editor and the Dope Sheet side-by-side together. I think a lot of animators do. I'm not trying to change your mind about this bug; I just wanted to let you know how I work.

Thanks, @JoshuaLeung! I believe you if you say that this issue is more trouble than it is worth to fix. One small point, though: More often than not, I *do* have both the Graph Editor and the Dope Sheet side-by-side together. I think a lot of animators do. I'm not trying to change your mind about this bug; I just wanted to let you know how I work.
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#38692
No description provided.