Jump to content

exel

Members
  • Content count

    161
  • Joined

  • Last visited

  • Days Won

    1

exel last won the day on May 27 2014

exel had the most liked content!

Community Reputation

1 Neutral

About exel

  • Rank
    Member
  • Birthday 10/08/1972

Contact Methods

  • Website URL
    http://

Personal Information

  • Name
    Jason
  • Location
    Los Angeles, CA
  1. It is indeed myself Mr. G, what's up man! In an attempt to solve one problem, I caused others -- blocky voxel shapes knocked out of the mesh on certain frames (attached). Something in the way it's resampling the compressed surface to match the VDB from particle fluid is causing Tetris-shaped holes in my mesh. I think I managed to fix that as well, sadly by removing the compressed fluid surface from the data and making the particle fluid surface node use only the particles. I think I'm losing most of the optimization and savings from the Fluid Compress node but the mesh is working a bit better. The scene I'm working with is kind of a beast, not particularly portable but if I can reproduce this in a more basic setup I'll send it in, thanks!
  2. ...for what it's worth I managed to improve it a bit after changing a lot of settings: --cranked up the particle bandwidth on the fluid compress node (caches now take up twice the disk space). The particles are still being packed but I think it's keeping pretty much all of them now, no culling going any more --cranked the erosion scale high enough until the particle fluid surface's internal "union" operation stopped wiping out the big shapes --turned off "rebuild SDF" on the VDB From Particle Fluid node -- for some reason this was key, none of the results were working until I changed this... Some of the smaller shapes still pop on and off, but I might be able to live with this, I'm hoping to generate enough bubbles and foam in there to hide the remaining crappiness...
  3. Hi all, hoping someone can help with this -- I've got a beach break sim, waves crashing on the rocky shore, etc. As the wave crests and curls over to crash, there's problems with the interior surfaces. While trying to eliminate variables and track down the issue, I've been working with a smaller section of the sim and turned off all the filtering on the mesh so it looks a bit crunchy right now, but hopefully this shows things clearly enough: (front view) (back view): --There it is, frames 98-99, a big part of the mesh just disappears, *pop*! This was done with the particle fluid surface SOP by the way, Houdini 15.5.565 . I've opened it up and have been digging around to try and diagnose the problem and so far all I can do is cause that shape to disappear on a different frame, sometimes it reappears for a few frames. So far I think it has something to do with how the surface layer of particles gets combined with the source @surface field out of DOPs. I get the same problem with or without using the Fluid Compress node. I've been all over the place with the erosion scale, droplet size, etc., but nothing is improving things If I look at the particles coming out of DOPs, I can see that the interior detail is there, nothing's popping from the sim: , and if I view the surface field coming from DOPs, that looks more like what I would expect: Anyway, I'm running out of ideas on how to fix this. I'd really like to take advantage of the fluid compression and the features that Particle Fluid Surface offers, but the "unioning" of the VDB from particles and the compressed fluid SDF isn't working so well. If I give up and just use the surface field straight from DOPS, I lose a lot of control over the detail and breakup of the splash areas. Any advice or tips are most welcome! Houdini 5.5.565 / Mac OS X 10.11.1
  4. Check out the example files for the Cone Twist constraint in the Houdini docs, there's a ragdoll physics example that helped clear a few things up for me.
  5. pyro to geometry tricks

    Thanks Ed, yeah it's hit or miss for me. The original renders are 1280x720, but they have a little noise in them from the environment light and PBR render, maybe it's causing some kind of interference.
  6. pyro to geometry tricks

    also this.
  7. I was doing some Pyro stuff and got majorly sidetracked, this is what came out: I'm bummed the compression is so bad, I tried a lot of things and just couldn't get it looking good in Vimeo, the original renders look so much prettier.
  8. Thanks David, Woops, yeah, pulling the vel field out of DOPs is smarter, thanks. I'll keep experimenting, I'm hoping to come up with technique that will scale up well when I start getting upwards of 8 or 10 million particles... Attribute Transfer is performing better than I remember, so I'll stick with it for now.
  9. Liquid from object Point Velocity issue

    Wow, that setup seems unusual to me, is that from a really old CMI video? I guess I've just never approached the pump relationship that way. On the fluidsolver1 node, I went to the "Pumps" tab under the "Fields" tab and changed Velocity Type to "Volume Velocity" and it looks like it's working now. Hope that helps! -JS-
  10. I always assume I'm missing something obvious. I'm doing some FLIP tests and would like to stick with VDB to create my meshes. Using the "VDB from Particle Fluid" SOP seems good-ish, but I'm left with a mesh that won't motion blur in mantra. So far I've tried creating another vdb using "vdb from particles", and sampling in "v" (using the additional point attributes options), and then transferring it over to the mesh with an Attribute from Volume SOP, but that doesn't seem like the greatest approach, and effectively doubles the amount of cooking involved. And I want to avoid the attribute transfer SOP for this, things will get ugly if I try to crank up the resolution. Maybe the "VDB from Particle Fluid" SOP just needs the same point attribute options that "VDB from Particles" has? Would it be better to pull the surface volume from DOPs and work with that? (instead of importing the particles) Thanks for any tips you can provide! -JS-
  11. Happy birthday...

    Happy birthday Marc! Enjoy your day off today, we're all going to get drunk at lunch in your absence... well, probably just me.
  12. Happy birthday...

    Happy Birthday bensimons! I hope you enjoyed the little tap dance I did for you at your desk this morning. THAT'S ALL YOU GET.
  13. expressions in Material SOPs?

    hmm that's a little wonky but you're right, I had to toggle the blank field (?) and then it worked. Thanks! -JS-
  14. expressions in Material SOPs?

    hmm weird! your file works for me, but I try the exact same thing in my file and it doesn't do anything, the parameter field doesn't even turn green. SOP flakyness? Oh well, I got around it by using an attribute create SOP (which didn't work at first, but then started working when I tried it again 10 minutes later) -JS-
  15. This seems like it should be simple: I'm trying to use an expression (python) to assign a material named after the object, by putting an expression in a Material SOP like this: hou.node("../../shopnet/" + hou.node("../").name()).path() ( /obj/geo1 should get assigned the full path to ../../shopnet/geo1 ) but it's not evaluating, I get a warning: The node "hou.node("../...." was not found or was the wrong type for this operation. I've tried this same expression in an Attribute Create SOP and it works, how can I force this to evaluate for the Material SOP? Thanks for any help! -JS-
×