Alembic integration improvements #69058
Labels
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
16 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69058
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design task to coordinate the Alembic project.
Order of importance:
?
Incomplete - Tasks needing more details before implementing.Open Bugs
Improvements
New Features
These features are related, in the sense that implementation would be possible (or at least easier) when #69046 is finished:
Other new features:
Design Tasks
Added subscriber: @dr.sybren
Added subscriber: @SteffenD
Added subscriber: @p2or
Hi Sybren,
I'm using alembic every day so many thanks for all your work and effort.
What I've noticed is that collections are ignored while exporting (flattened out). I think including/supporting collections might be a nice (and probably quick) improvement in order to keep the same hierarchy in other packages. I'm currently using a custom export operator, converting all the collections to empties before exporting the scene to alembic, which essentially is faking a group but is in fact just a quick and dirty workaround. Exporting heavy scenes just takes a few seconds longer so there is no real issue by that. However, in case there is any chance supporting groups/collections by default, would be a nice of course. In case you support that idea and you think I can help on that, providing or testing some files, just let me know. What do you think?
Thanks & Cheers,
Christian
We're thinking of ways of including collections into the exported hierarchies, both for USD and Alembic, but it's not an active task at the moment. It's unfortunately not a quick thing to do, because:
Because of the above points, there is no clear one-to-one mapping that will always work. The USD exporter currently supports case 2. from the above list, and properly handles cases where an object in an instanced collection has a parent outside that collection. I think that it's best to first get the USD exporter into master, then alter the Alembic exporter to use the improvements I made for USD, and then we can improve the way we handle collections.
Hey Sybren,
many thanks for that explanation, makes sense. Just thought, that's an easy thing to do and would improve it drastically consistency wise...
Thanks again,
Christian
Added subscriber: @Momotron
Added subscriber: @MaciejJutrzenka
Added subscriber: @PixelTrader
Added subscriber: @juang3d
HI Sybren.
Great to see this task! :D
Please don't forget about velocities or motion blur for fluid meshes (or variable vertex count meshes), right now we cannot render motion blur for fluids baked on alembic format.
Cheers.
That is actually already in the tracker... #49234 (Alembic not importing motion blur)
Added subscriber: @ajohnson223
This comment was removed by @ajohnson223
@ajohnson223 Please don't comment here to report issues or discuss problems; if you have found a bug, please file a bug report. I have removed your comment to keep the tracker clean; in case you don't agree, let me know in a private message.
Added subscriber: @frameshift
Added subscriber: @Pipeliner
Added subscriber: @g-lul
Added subscriber: @YegorSmirnov
This comment was removed by @YegorSmirnov
Added subscriber: @evantryan
Added subscriber: @Javon-Adams
Added subscriber: @steffenk
Added subscriber: @ahmed.hindy96
I'm closing this task, as I'm no longer working on the Alembic code, and the information here is rather outdated.