Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


Zybrand last won the day on January 23 2017

Zybrand had the most liked content!

Community Reputation

12 Good


About Zybrand

  • Rank

Contact Methods

  • Skype

Personal Information

  • Name
  • Location

Recent Profile Visitors

2,607 profile views
  1. Retime Fluid Mesh

    Hi Zinogino, What you are trying to do will never work. The fluid mesh is an arbitrary mesh and the point numbers will be in different and in different places every frame, as far as Houdini is concerned it might as well be completely different shapes so there is nothing to interpolate. That is why you have to transfer velocity from points as well. If you want to retime the simulation you will have to do it before you mesh the fluid. Hope that helps. Z
  2. Collapsing to a material instead of a sub-net did the job thanks
  3. Hey guys, I am having trouble converting a SHOP setup to the MAT network. I am sampling colours from a cached point cloud to change the surface colour and it works as expected in the SHOP network if I promote the pcopen file and pick a sequence. But it doesn't work in the MAT network, if I leave it as a flat network there is no where to promote to and I get the "time dependent warning" and putting the setup in a subnet and promote that still doesn't work. I either get the first frame of the cache sampled or nothing at all. Is it because the MAT network is just a massive VOP? And is there another workaround? thanks, Z
  4. Pop Grain issue! Please help!

    Also grain has a built in speed and acceleration limit you can use. And uping the drift threshold might help with you sim as well.
  5. Mercury spilling using flip

    Have you tried using surface tension?
  6. Why no beer tutorial?

    OK that is fair enough, I thought you were saying that you were researching beer specifically for a long time. I used Realflow before I moved to Houdini haven't used it in a long time though but its SPH liquids are probably better for beer than FLIP. But since this is a Houdini forum I'll stop talking about other software. A good place to start would probably be variable density with using density by attribute in the FLIP solver. Or you could do the foam as a secondary sim after the initial flip sim. simple_beer_zj.hip
  7. Why no beer tutorial?

    If there is almost no info how have you been researching this area for a long time? To answer the why no tutorials question, my best guess it that traditionally the strength of FLIP fluids is in doing large scale water simulations and it is easier to do out of the box. Apart from more viscous small scale simulations large water sims is what more people use it for equaling more large scale sim and more large scale sim tutorials. Surface tension out of the box for example is a new feature so you won't have much tutorials on it. I am not saying you can't do good small scale fluid like a glass of beer, you can for sure. Its just that the main focus of the community has been geared more towards large scale ocean sim.
  8. Hi Phiphat, Sounds like you narrowed down your problem to the "Flatten Geometry" section of the Particle Fluid Surface. You mention that the problem happens at different frames with different particle separation values but does it consistently happen at the same frames at the same resolution? If so that eliminates any sort of ram limit issue. If you dive inside the Particle Fluid Surface you will find a FLATTEN subnet which handles the bounding box and flatten geometry calculations. In there VBDs are being edited and merged together with a VDB combine using SDF difference and another using SDF union. That is most likely with your problem is because it looks like on of those VDBs are being calculated wrong and subtracting the whole fluid surface on those frames. The simplest thing to try first is just to adjust your bounding box size and see if the problem persists.
  9. super stretchy flip

    This might be a good place to start Houdini Tutorial: Elasticity
  10. Granular Sheet - Can't Rip the Mesh

    @Skybar Nice one! getting the attribute as part of the sim handy. And good idea to just use the attribute copy to transform the mesh.
  11. Granular Sheet - Can't Rip the Mesh

    Thanks Johnny, next time I'll grab one of your setups Hi Alvaro, cool I'll glad it works. Yes I think you understand get it, I am setting the initial amount of neighbours before the sim and getting the amount of neighbours after the sim. You have to set the start neighbours before the 2D triangulate because the amount of neighbours changes and I am calculating the the neighbours after the sim to get the new amount. And then the difference node just compares the the values on the geometry you want to tear. You can probably get better results if you work on the attribute promote -> delete prims part of my setup. That was just a quick test to see if it would work but maybe an edge group can get you better tear lines.
  12. Granular Sheet - Can't Rip the Mesh

    A different approach you can try is to compare the sim point neighbours with the initial point neighbours and use the attribute to delete primitives on the mesh. Have a look at my hip file it's just a quick proof of concept but with some work I think you can get good results with it. granular sheet - ripping it ZJ.hiplc
  13. Stacking, python to vex

    Hey Sessionbeer, Slightly different setup but it works on a detail wrangle: //get start point vector new = point(0,"P",0); for (int i = 0; i < @numpt; i++){ if(i == 0) // skip first point continue; vector scale = point(0, "scale", i); vector prev_scale = point(0, "scale", i-1); //get the height fron current and prev_scale combined new.y = new.y + ((scale.y + prev_scale.y)*0.5); setpointattrib(0, "P", i, new); }
  14. thin-walled container in flip simulation

    Someone correct me if I am wrong but the reason for the vdb proxy from sops is because vdb is no currently supported in dops but it still creates a better collision sdf than ray intersect with less errors and faster. Calculating the vdb in sops and converting it in dops is faster and more efficient that calculating the collision volume in dops especially if the vdb is cached as well.