Hey,
So I'm having an issue where when I have fluids inside an animated container, they wont hold their volume. As soon as the geometry moves they just begin to collapse in on themselves. I have reseeding turned off so I can see that all the points still exist, they just exist on top of each other. If the geometry is not animated it will hold its volume. I have been running into this issue for a while now whenever I try to fill a container with fluid, anybody know what I may be doing wrong? Ill attach a simplified sample file as well. Thanks!
note - Changing the velocity type in the collisions tab of the fluid solver helps but the issue still happens. Just slower.
Collapsing Flip Fluids
5845 5 1
-
- mrhumbility
- Member
- 7 posts
- Joined: Jan. 2013
- Offline
-
- vleermeneer
- Member
- 245 posts
- Joined: Sept. 2011
- Offline
I've changed a few things in your scene (see screenshots for more information).
First I've disabled the xform node, and instead I've transformed the geometry at /obj/ level, so altering the SOP node instead.
Then you can go to autodop and disable “deforming geometry” because its not actually deforming, its transforming. When you enable “deforming geometry”, your object will actually be recalculated every frame which can cause slowdown. Next you need to change the OBJ path or in the static object node or else it wont take in account the transformations.
First I've disabled the xform node, and instead I've transformed the geometry at /obj/ level, so altering the SOP node instead.
Then you can go to autodop and disable “deforming geometry” because its not actually deforming, its transforming. When you enable “deforming geometry”, your object will actually be recalculated every frame which can cause slowdown. Next you need to change the OBJ path or in the static object node or else it wont take in account the transformations.
-
- mrhumbility
- Member
- 7 posts
- Joined: Jan. 2013
- Offline
-
- vleermeneer
- Member
- 245 posts
- Joined: Sept. 2011
- Offline
When you import Alembic files you will have nested geometry files usually, some of them are actually geometry nodes (at /obj/ level).
So when you import .abc files you get one alembic node with many nodes inside that one.
What I would do is create a new Geometry node, inside that one place down an “object merge” node, and fetch the Alembic geometry (see screenshot).
The “transform object” part specifies which node it should use for transformations. Here you can fetch the nested abc node with some sort of animations..
So when you import .abc files you get one alembic node with many nodes inside that one.
What I would do is create a new Geometry node, inside that one place down an “object merge” node, and fetch the Alembic geometry (see screenshot).
The “transform object” part specifies which node it should use for transformations. Here you can fetch the nested abc node with some sort of animations..
-
- mrhumbility
- Member
- 7 posts
- Joined: Jan. 2013
- Offline
-
- mrhumbility
- Member
- 7 posts
- Joined: Jan. 2013
- Offline
Hey all,
So I spent a long time trying to use collision volumes to act as a container but I wasn't able to have the fluid source node create an accurate enough volume representation to behave the way I needed it to. A friend of mine helped me get this working though and as usual in my experience, it turned out to be a simple drop down. In the fluid solver in the volume motion > collisions tab the velocity type needed to be point instead of rigid. This allowed me to use rbd's for the collision type which was faster than the velocity volume method, and still have the fluids hold their separation. Here is a sample file of how I have it working now.
So I spent a long time trying to use collision volumes to act as a container but I wasn't able to have the fluid source node create an accurate enough volume representation to behave the way I needed it to. A friend of mine helped me get this working though and as usual in my experience, it turned out to be a simple drop down. In the fluid solver in the volume motion > collisions tab the velocity type needed to be point instead of rigid. This allowed me to use rbd's for the collision type which was faster than the velocity volume method, and still have the fluids hold their separation. Here is a sample file of how I have it working now.
-
- Quick Links