Motion curve update mismatch #47762
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#47762
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?
Windows 7 Professional 64-bit SP1
Nvidia GeForce GTX 760
Broken: Blender 2.75a ...up to and including current version... 2.77 rc2
Description: When moving a keyframe from within the dope sheet editor the movement of the keyframe within the graph editor does not reflect the true condition of the new curve until the action is finished.
This is a small visualization bug.
It will be seen that when a keyframe is moved in time (along the X axis) from within the graph editor the keyframe handles as well as the associated curve will change as required during the move to constantly reflect changes related to the new position of the keyframe.
When the keyframe is moved from within the dope sheet editor the keyframe will also move within the grpah editor, but the simultaneous updating of handle length and correct curve shape will not be shown. However, when the action is completed, the curve and handles in the graph editor will update to reflect the new, correct position.
curve update visualization.blend
Changed status to: 'Open'
Added subscriber: @ignatz
Added subscriber: @mont29
Joshua, think this one is for you? ;)
Technically, this is not really a bug; it is however a glitch that we know about AND have thus-far decided against fixing.
This issue happens because the when transforming keyframes in the Action Editor, we do not rearrange the actual order of the keyframes in the FCurves until the transform is done. We could do so (and it is done for the Graph Editor, because it has to be done as the curves are visible), though so far, the cons of doing so outweight the pros.
Pros:
Cons:
3) Slower keyframe editing in Action Editor
4) Significantly more complicated (i.e. really convoluted, hard to maintain, head-scratching + confusing) code needs to be in place to track and remap the "transvert" pointers to refer to the correct keyframe point values, as reordering the keyframes while transforming will constantly invalidate the old mappings. (Note: Although similar code has been created for the Graph Editor, the differences between the two are significant enough that a separate set of code for this will be needed instead)
5) Making these changes is unnecessary when considering the intended use cases of these editors - The Action Editor is used mainly for blocking animation and broad/coarse timing corrections, while Graph Editor is for fine tuning value change over time in "polish" passes (where timing changes less).
So, overall, IMO it's better that we don't try going in fixing this, as it doesn't seem to be worth it. One or two particular feature changes may warrant a review of this, but until then, I think the current behaviour should be fine.
Thanks for the report anyway :)
Changed status from 'Open' to: 'Archived'