Apply Transforms doesn't work with Auto Keying #89716

Closed
opened 2021-07-07 20:52:40 +02:00 by Lai Yu-Hsuan · 12 comments

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: 84da05a8b8
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).

**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: `84da05a8b8` 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).
Author

Added subscriber: @raincole

Added subscriber: @raincole
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

@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)

@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)
Author

In #89716#1188423, @PratikPB2123 wrote:
@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.

> In #89716#1188423, @PratikPB2123 wrote: > @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.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Philipp Oeser self-assigned this 2021-07-08 11:27:31 +02:00
Member

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

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

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 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])

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

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.

This was discussed in yesterday's #animation_rigging module meeting ([meeting notes](https://devtalk.blender.org/t/2021-07-08-animation-rigging-module-meeting/19531)), 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.
Member

OK, thx checking on this.

OK, thx checking on this.
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
4 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#89716
No description provided.