Graph Editor - AutoMerge Keyframes does not happen when snapping to Current Frame #65521

New Issue

Wayne Johnson · 2019-06-05T12:46:26+02:00

Wayne Johnson commented

2019-06-05 12:46:26 +02:00

System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26

Blender Version
Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-04 22:32, hash: e80cbdac33
Worked: (optional)

Short description of error
Moving keyframes over each other merges keys as expected, but when you use Shift-S to snap to current frame, the keys do not merge like they used to.

Exact steps for others to reproduce the error
0. Ensure that 'AutoMerge Keyframes' is checked on the Graph Editor View menu

Animate the default cube to move away from the origin.
Duplicate the last keyframes, constraining to X a few frame to the left
Move the animation playhead cursor to frame 1, which has the 'origin' keyframes on it
With your new duplicated keyframes selected, use Shift-S to snap those keys to Current Frame (left on the Pie (4))
Expected behaviour is that the newest keyframes will overwrite the origin keyframes..
...however, this does not happen. Instead, all keyframes are maintained on the first frame

**System Information** Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon R9 M295X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26 **Blender Version** Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-04 22:32, hash: `e80cbdac33` Worked: (optional) **Short description of error** Moving keyframes over each other merges keys as expected, but when you use Shift-S to snap to current frame, the keys do not merge like they used to. **Exact steps for others to reproduce the error** 0. Ensure that 'AutoMerge Keyframes' is checked on the Graph Editor View menu 1. Animate the default cube to move away from the origin. 2. Duplicate the last keyframes, constraining to X a few frame to the left 3. Move the animation playhead cursor to frame 1, which has the 'origin' keyframes on it 4. With your new duplicated keyframes selected, use Shift-S to snap those keys to Current Frame (left on the Pie (4)) 5. Expected behaviour is that the newest keyframes will overwrite the origin keyframes.. 6. ...however, this does not happen. Instead, all keyframes are maintained on the first frame

Wayne Johnson commented

2019-06-05 12:46:26 +02:00

Added subscriber: @slowboy

Alexander Gavrilov was assigned by Sebastian Parborg

2019-06-13 18:19:48 +02:00

Alexander Gavrilov was unassigned by Dalai Felinto

2019-12-23 16:34:11 +01:00

Dalai Felinto commented

2019-12-23 16:34:11 +01:00

Added subscriber: @angavrilov

Philipp Oeser commented

2020-01-27 12:18:21 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-01-27 12:18:21 +01:00

Turns out this is actually the same as #49223 (AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)):

posttrans_fcurve_clean will only act on [delete] unselected keyframes, thus skipping the duplicates is all are selected...

Turns out this is actually the same as #49223 (AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)): - `posttrans_fcurve_clean` will only act on [delete] unselected keyframes, thus skipping the duplicates is all are selected...

Philipp Oeser commented

2020-01-27 12:18:29 +01:00

Closed as duplicate of #49223

Philipp Oeser closed this issue

2020-01-27 12:18:29 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Graph Editor - AutoMerge Keyframes does not happen when snapping to Current Frame #65521