Blender: Layer Move Animation Bug? Keyframed as Layer 1, comes out as Layers 1 AND 2. #29883

Closed
opened 2012-01-14 09:05:59 +01:00 by Ryan King · 5 comments

%%%1) Go to frame 1, keyframe the Layers for the object onto layer 1.
2) Go to frame 2, click on layer 2 (the object disappears), and keyframe that.
3) Go to frame 3, click layer 1, keyframe that.
4) Now when we go back to frame 2 the object is on both layer 1 and 2 (!).

Further odd behavior is visible if you click a second time on frame 2: the second click causes the layers to work correctly.
If you look at the Animation Curves, they are correct, and scrubbing through the list there correctly updates the 3D Viewport
If you LMB+Drag on the timeline, it updates the 3D Viewport correctly (but not when you simply LMB click on a frame--see above).

Here is a video of the behavior that has the demo:
http://www.youtube.com/watch?v=DJQ6zK5xQyU

I included a .blend, but this is very easy to replicate. So far we have done so on:

  • Official 2.61 (OS Unknown)
  • SVN version 2.61 (sub 2), r43365. Release - build date: 2012-01-14, 09:08:48 (Linux)
  • graphicall.org build 2.61.1, r43283 (Windows)

%%%

%%%1) Go to frame 1, keyframe the Layers for the object onto layer 1. 2) Go to frame 2, click on layer 2 (the object disappears), and keyframe that. 3) Go to frame 3, click layer 1, keyframe that. 4) Now when we go back to frame 2 the object is on both layer 1 and 2 (!). Further odd behavior is visible if you click a second time on frame 2: the second click causes the layers to work correctly. If you look at the Animation Curves, they are correct, and scrubbing through the list there correctly updates the 3D Viewport If you LMB+Drag on the timeline, it updates the 3D Viewport correctly (but not when you simply LMB click on a frame--see above). Here is a video of the behavior that has the demo: http://www.youtube.com/watch?v=DJQ6zK5xQyU I included a .blend, but this is very easy to replicate. So far we have done so on: * Official 2.61 (OS Unknown) * SVN version 2.61 (sub 2), r43365. Release - build date: 2012-01-14, 09:08:48 (Linux) * graphicall.org build 2.61.1, r43283 (Windows) %%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%This has probably to do with the fact that an object cannot be on no layer at all,
so, when switching frames, the removal of layer 1 is unsuccessful, but layer 2 is added.
A workaround is therefore obvious, have the object on some unrelated layer (or have it
on layer 2 the whole time, if you just want to remove it from 1).

Removing this restriction would probably be possible (I have not looked at the code),
but I don't know if it's worthwhile if it turns out to be complicated.%%%

%%%This has probably to do with the fact that an object cannot be on no layer at all, so, when switching frames, the removal of layer 1 is unsuccessful, but layer 2 is added. A workaround is therefore obvious, have the object on some unrelated layer (or have it on layer 2 the whole time, if you just want to remove it from 1). Removing this restriction would probably be possible (I have not looked at the code), but I don't know if it's worthwhile if it turns out to be complicated.%%%
Author

%%%David, yes, that workaround works for me.%%%

%%%David, yes, that workaround works for me.%%%

%%%Issue is indeed caused by curves applying one-by one and even if overall state on frame 2 is correct, it can't be reached because first curve is trying to make object to belong to no layers. Currently there's no nice way to resolve such restriction. Added not to our TODO wiki (http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation#Animation). Thanks for the report, but will close it now.%%%

%%%Issue is indeed caused by curves applying one-by one and even if overall state on frame 2 is correct, it can't be reached because first curve is trying to make object to belong to no layers. Currently there's no nice way to resolve such restriction. Added not to our TODO wiki (http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation#Animation). Thanks for the report, but will close it now.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#29883
No description provided.