NLA corrupt animation when adding armature strips. #84774

Closed
opened 2021-01-16 13:16:44 +01:00 by Aleksandr · 10 comments

System Information
Operating system: Linux-4.15.0-132-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04

Blender Version
Broken: version: 2.83.10, branch: master, commit date: 2020-12-07 14:09, hash: b439a15544
Worked: (newest version of Blender that worked as expected)

Short description of error

My goal was simple as that: just merge two actions in one. But I found that is impossible and even more of that - this operation corrupt my keys in action. See the video.

1. I do not why NLA didn't work as expected
2. NLA change my action without baking

Same trouble in 2.83.10 and 2.90.

Exact steps for others to reproduce the error
Open my blend file - add strips to NLA - switch on armature in NLA - take in account difference from source action and constrains has same configurations- switch off armature in NLA - open action "Reload" in action editor - check the issue
NLA_Bug.blend
Screencast-2021-01-16_14.45.04.mp4

**System Information** Operating system: Linux-4.15.0-132-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04 **Blender Version** Broken: version: 2.83.10, branch: master, commit date: 2020-12-07 14:09, hash: `b439a15544` Worked: (newest version of Blender that worked as expected) **Short description of error** My goal was simple as that: just merge two actions in one. But I found that is impossible and even more of that - this operation corrupt my keys in action. See the video. **1.** I do not why NLA didn't work as expected **2.** NLA change my action without baking Same trouble in 2.83.10 and 2.90. **Exact steps for others to reproduce the error** Open my blend file - add strips to NLA - switch on armature in NLA - take in account difference from source action and constrains has same configurations- switch off armature in NLA - open action "Reload" in action editor - check the issue [NLA_Bug.blend](https://archive.blender.org/developer/F9581829/NLA_Bug.blend) [Screencast-2021-01-16_14.45.04.mp4](https://archive.blender.org/developer/F9581830/Screencast-2021-01-16_14.45.04.mp4)
Author

Added subscriber: @viadvena

Added subscriber: @viadvena
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Thx for the report and the corresponding video.

NLA didn't work as expected

open action "Reload" in action editor - check the issue

Sorry for not getting it right away, but could you try to explain in a bit more detail what I should be looking at?

  • which bone specifically behaves differently than before?
  • or are keyframes altered? timing? spacing?

Sorry if this sounds obvious [ it is not for me - might need more coffee :) ].

Thx for the report and the corresponding video. > NLA didn't work as expected > open action "Reload" in action editor - check the issue Sorry for not getting it right away, but could you try to explain in a bit more detail what I should be looking at? - which bone specifically behaves differently than before? - or are keyframes altered? timing? spacing? Sorry if this sounds obvious [ it is not for me - might need more coffee :) ].
Author

Sure @lichtwerk. This shown in 0:59 of this video. When I switch off armature in NLA bones keeps incorrect poses in keyframes produced by NLA. Before I started use NLA bones have proper poses which I marked in the video.

Sure @lichtwerk. This shown in 0:59 of this video. When I switch off armature in NLA bones keeps incorrect poses in keyframes produced by NLA. Before I started use NLA bones have proper poses which I marked in the video.
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

Added subscriber: @wbmoss_dev

Added subscriber: @wbmoss_dev
Member

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

Changed status from 'Needs Triage' to: 'Resolved'
Wayde Moss self-assigned this 2021-05-13 02:02:46 +02:00
Member

This is not a bug, just a misunderstanding. The Reload animation has no animation fcurves for the root_CTRL. The Fire animation has root_CTRL animation and it isn't placed at the origin.

Without using the NLA, when you switch actions, properties are not reset to default transforms. Changing between Fire and Reload works as expected. Now, NLA blends vertically, not horizontally and it always resets all animated properties to default values before blending. That means root_CTRL will be placed at the origin for Reload, which some of the arm controls are children of. That seemingly "corrupts" the animation. The fix here is to ensure all controls are keyed before adding the action to the NLA. Or you can place the Reload strip above the Fire strip (so root_CTRL is properly placed), then insert the root_Ctrl keys then you can move the strips to be adjacent again.

This is not a bug, just a misunderstanding. The Reload animation has no animation fcurves for the root_CTRL. The Fire animation has root_CTRL animation and it isn't placed at the origin. Without using the NLA, when you switch actions, properties are not reset to default transforms. Changing between Fire and Reload works as expected. Now, NLA blends vertically, not horizontally and it always resets all animated properties to default values before blending. That means root_CTRL will be placed at the origin for Reload, which some of the arm controls are children of. That seemingly "corrupts" the animation. The fix here is to ensure all controls are keyed before adding the action to the NLA. Or you can place the Reload strip above the Fire strip (so root_CTRL is properly placed), then insert the root_Ctrl keys then you can move the strips to be adjacent again.
Author

@wbmoss_dev Thanks a lot for helping me figure this out! Now all gears are rolling right.

@wbmoss_dev Thanks a lot for helping me figure this out! Now all gears are rolling right.
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
3 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#84774
No description provided.