Page MenuHome

Apply Transforms doesn't work with Auto Keying
Closed, ArchivedPublic

Description

System Information
Operating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21

Blender Version
Broken: version: 2.93.0, branch: master, commit date: 2021-06-02 11:21, hash: rB84da05a8b806
Worked: (newest version of Blender that worked as expected)

Short description of error
When Auto Keying is on, applying an object's transforms leaves the keyframes in old (unapplied) states.

Exact steps for others to reproduce the error

  1. Turn on Auto Keying
  2. Create a cube
  3. Move it to (1, 1, 1)
  4. Apply All Transforms

The keyframed location is still (1, 1, 1), while it should be (0, 0, 0).

Event Timeline

@Lai Yu-Hsuan (raincole) , thanks for the report. Applying transform do set the location value to (0, 0, 0)

But scrubbing and then moving back to initial keyframe, location has turned up to (1, 1, 1) instead of (0, 0, 0).

Are you trying to point the same issue? (want to make sure if we are on same track)

@Lai Yu-Hsuan (raincole) , thanks for the report. Applying transform do set the location value to (0, 0, 0)

But scrubbing then moving back to initial keyframe, location has turned up to (1, 1, 1) instead of (0, 0, 0).

Are you trying to point the same issue? want to make sure if we are on same track)

Yes, I meant the exact same issue. As I said in the initial post, the "keyframed" location is still (1, 1, 1), not the location.

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Confirmed.EditedJul 8 2021, 11:27 AM
Philipp Oeser (lichtwerk) claimed this task.

Clearing Transform does this (will re-set the key), will check...

This can be done, but of course, one way or the other you can run into unexpected situations here (if you have [other] keyframes, you object will seemingly shift anyways...)
Same is true for other operators as well [Set Origin]
That being said, personally I would still vote for including an autokey in operators that alter transforms (outside the transform system - which always handles autokey [also when only transforming origin for example])

This was discussed in yesterday's Animation & Rigging module meeting (meeting notes), and it was decided that the operation shouldn't auto-key. Simply put, the operation is seen more like a mesh/geometry operation than an animation operation. Furthermore, it would require updating much more than just the key of the current frame. That said, something like proportial editing over time would be a great tool, also for all kinds of other adjustments. Regardless, the lack of auto-keying for Apply Transforms is not seen as bug, so I'll close this report.

OK, thx checking on this.