Animated ABC Won't Collide With Fluid Simulation #62980
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#62980
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?
Blender 2.79
It's pretty simple to recreate, Import an animated ABC mesh and try to use it as a collision object. The fluid system ignores the the mesh completely, even when placed in Triangle MESH mode.
NOTE: The .ABC file I am using is the CRAG ROBOT Test Geometry that I exported from Houdini. It is a 420 frame animation that weighs in around 2GB. (not sure if your system can handle that size of an upload)
I tried to create a companion python script that would fetch the data block from the ABC object and assign it to standard mesh, but only fetches the first frame from the animation and produces the following error on all other frames.
My guess is the data block is no being updated for the .ABC object, when the frame changes.
Here is my basic transfer mesh data block that runs in a frame change.
Added subscriber: @AtomP
Added subscriber: @lichtwerk
Changed status from 'Open' to: 'Archived'
This is because the alembic modifier cannot be placed above the fluidsim modifier.
(this would be needed in order for the fluidsim to pick the changes up)
You should get a message like
I think the reason is that .abc [in contrast to .mdd or .pc2] can have changing vertex count across frames, which apparently fluidsim obstacles cant handle...
If you know your vertex count is not changing, try caching in .mdd or .pc2 instead.
Then use the
Mesh Cache
modifier (not theMesh Sequence Cache
modifier) to load the cache.The
Mesh Cache
modifier can indeed be place above the fluidsim modifier, thus this can be used as an (deformation-animated) obstacle.Long story short: this is a known limitation [which might be lifted with upcoming mantaflow integration, but not sure...].
And there is a workaround that would work in most cases (non-changing vertex count).
Will archive this report, feel free to comment again if issues persist...
So why can't I fetch the mesh data block, from the .abc animation, in a frame change?
Shouldn't the Mesh Sequence Cache modifier correctly present the current mesh data block, to the API, for the frame it is displaying?
Why does the frame change code fail?
NOTE: I have attached a shortened version of the .ABC file that I am using, for others to test with.
crag_robot_HIT_ONLY.abc
Havent actually checked it, and it feels like swapping mesh datablocks in a framechange handler is not the best solution, but would it help getting the evaluated object?
Added subscriber: @3di
@AtomP what was the solution here? Currently trying to get a rigid body simulation to collide with an alembic, but no joy.