Actions should be linked to particular objects #45808

Closed
opened 2015-08-15 18:03:57 +02:00 by Mark McKay · 5 comments

I've been writing a scene exporter for the last week and been learning the basics of the python API by examining the different data blocks that Blender presents to the user. Anyhow, I noticed how the Action blocks to not depend in any way on any particular Object.

This strikes me as really weird. Worse, it's ambiguous since if I iterate through the list of all actions in a scene they can potentially be assigned to every object in the scene. I could create an 'UpAndDown' animation action for a mesh in my scene and it would be just as valid for every other mesh. I could even apply it to a material if I wanted, even though that would make even less sense. (For my exporter, I just have to guess which actions are appropriate for which objects based on the property paths of their fcurves).

This behavior is unlike other 3D packages such as Maya. While I can understand changing something like this could be very disruptive, I would hope the designers would consider it if they ever overhaul the animation system.

I've been writing a scene exporter for the last week and been learning the basics of the python API by examining the different data blocks that Blender presents to the user. Anyhow, I noticed how the Action blocks to not depend in any way on any particular Object. This strikes me as really weird. Worse, it's ambiguous since if I iterate through the list of all actions in a scene they can potentially be assigned to every object in the scene. I could create an 'UpAndDown' animation action for a mesh in my scene and it would be just as valid for every other mesh. I could even apply it to a material if I wanted, even though that would make even less sense. (For my exporter, I just have to guess which actions are appropriate for which objects based on the property paths of their fcurves). This behavior is unlike other 3D packages such as Maya. While I can understand changing something like this could be very disruptive, I would hope the designers would consider it if they ever overhaul the animation system.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @kitfox

Added subscriber: @kitfox
Member

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Joshua Leung self-assigned this 2015-08-16 02:46:51 +02:00
Member

As of 2.74, you should be able to find the actions associated with particular objects stored in the NLA stacks for those objects.

http://wiki.blender.org/index.php/User:Aligorith/27X_ActionManagement

As of 2.74, you should be able to find the actions associated with particular objects stored in the NLA stacks for those objects. http://wiki.blender.org/index.php/User:Aligorith/27X_ActionManagement
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
2 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#45808
No description provided.