Jump to content

redpaw

Members
  • Content count

    32
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About redpaw

  • Rank
    Peon

Contact Methods

  • Website URL
    http://www.redpawfx.com

Personal Information

  • Name
    redpaw
  1. Digital Assets and the Tab menu

    Any idea how to query that "Tab Submenu path" string on an HDA using python? cant' seem to find that bit of data anywhere?
  2. Hi, I was wondering if there is any way that I am not aware of to cache or precalculate the collision data that gets calculated at the beginning of a packed Bullet simulation. I've got a scene with approx 11,000 rbd objects from a shatter as a packed fractured bullet rbd, and it takes approx 5 minutes to get thru the first frame where it is I assume, building the collision convex hulls for the geo. I would assume there's some way to cache that and re-use it? but I don't see anything. The startup time on a sim is killing me. Any ideas? thx -redpaw
  3. I've got a particle sim I'm meshing with openVDB, I would like to export this with motion blur to an alembic cache to render in maya/arnold. simple example, not using particles, but yeilding the same results.. make a torus, and add rotation animation xform node. convert to VDB using vdbFromPolygon convert back to polygons with convertVDB node. add a trail sop to compute velocity. export using alembic rop. If I skip the convert to vdb and back and just export the rotating torus, I get subframe motion based on vertex velocity in the alembic file without exporting extra motion blur steps in the alembic file... however with the openVDB stuff I end up with static geo inbetween frames. even though it seems to be creating proper vertex velocity. I can export this as a realflow mesh and it will pass the velocitiy correctly so is this a problem with the houdini alembic exporter? or user error on my part? I'm writing out 20+ mil poly meshes so I'd rather not have to subsample them and write out the data 2-3x just to get motion blur.. at that point I might as well go back to realflow meshes instead. any help would be appreciated. thanks in advance -johnc redpawfx
  4. Sorry, its been about a half a year since I read this topic.. it may not be a perfect solution, but basically, what I did was inside the solver itself where it splits and generates the new fracture geometry, it holds the inside/outside groups... I inserted a uv texture node on the inside section so on creation, it applies the tex coords.. main issue is that the projection is not perfect , there will be some stretching etc.. but if you just need tex coords to be able to map a 2d noise or something it should work pretty well. I'll have to dive into houdini later and see if I can't export something to share, but this hopefully might put you on the right track. -redpaw
  5. HOT in MR for Maya

    I'm trying to get this to compile using the latest source, slightly modified for proper linux compiles, but I'm running across a problem. I get a full compile on the deformer without errors, however it seems that libImath.so is needed in addition to libblitz.so and libfftw.so when I compile it, it links and seems ok, but if I run ldd on the plugin, it shows me that its looking for libblitz and libfftw3 but libImath is nowhere in the list.. thus when I load it into maya I am getting an undefined symbol error, I know its finding the .so when linking, because if I change the name it errors out at compile time but for the life of me I cannot figure out why I can't get it to work. I'm compiling in fedora 15 with a custom gcc version for maya (4.1.2), could that be the problem? anybody with a little more experience debugging stuff? help! thanks -johnc
  6. is there RealFlow-houdini11?

    I just got the official word that the latest and greatest houdini-11.0.658 plugin is being uploaded to nextlimits servers today. Hopefully this should be for all platforms, but at least Linux 64 -johnc
  7. New autodesk product features announced...

    As a mainly maya user concentrating on FX stuff, This update makes me just want to use houdini more. Especially if all the dynamicss plugins aren't available for linux. Oh well.. we'll have to wait and see.. -redpaw
  8. Hi guys, quick question. Is there a way to set up and use an attribute to flag a piece of geometry for only a certain number of frames? in code, I'm thinking like add an attribute called separated, set it to 0, then modify it with some expression to set separated to 1. then for every frame after that, if separated is already 1, it should always stay as 1, even if the original modification expression would evaluate it back to 0 again. basically a one way switch attribute. I know the nature of sops may not handle this, so is this a case for a sop solver within dops? if it would be possible to do it in sops tho that would be ideal. if anyone has any ideas that'd be awesome. thanks in advance -johnc
  9. Yes!, actually this afternoon I got back to this problem and after watching a video or two from peter Quint on houdini UV stuff, he showed exactly the same problem I was having, and the solution was to be using vertex uv's, so I gave it a shot and after a little fooling around with the placement of the nodes again, I got it working now. so to change the file I submitted earlier I added a vertex sop to the input of the dopImport, put another vertex sop before the texture sop in the voroni fracture otl, and had to remove the switch sop after the texture I put in since it didn't work anymore. I was waiting to try it out on my actual non test file before I posted again to see if it fixed it in all cases, but it seems that it has for now. thanks ! -johnc
  10. I've got another bit of weirdness I'm hoping someone can help me with. Attached is a test file I've put together. What I'm trying to do is auto fracture at sim time with multiple iterations, and have the texture UVs stay "sticky" to the interior surfaces once they are applied. Ive accomplished this by inserting a UVtexture node right after the inside group creation point in the voroni fracture sop within the rigid body solver OTL. I tried a bunch of different ways to do this, but this was the most sucessfull except for one issue. It works with native houdini geo, or stuff you completely UV in houdini, but if you are trying to use an already uv'd OBJ from a file as the input, it seems to need the "uv" parameters explicitly set, like with a point sop the only way I have found to get the fracture time UV application to work is if i put a point SOP on the object before the dopImport However, the point sop, (with add texture on) ends up squishing the UV's at the borders and ruining the good uv layout in some cases. this is illustrated in the test file. I'm sure there's a way around this.. anyone? thanks in advance -johnc shatteringTexWeirdness.rar
  11. dopnumrecords impacts to sopSolver issue

    Hmmm, well I am still having a bit of a problem with this, I'm closer, but I still think I'm doing something wrong here. now it registers the dop impact and sets the group for true for all the objects and the sop solver then scales every object at the same time. what I want is for each object to scale as it enters the group, because it registers its own impact. I've attached a simple demo file, if anybody can point me in the right direction that'd be awesome. thanks -johnc sopSolverTest.hipnc
  12. I would like to use a simple sop solver setup to scale the pieces of a fracture object when they register an impact right now I'm trying to create an impact group with dopnumrecords(".", $OBJNAME", "Impacts", "Impacts")>=1 to activate the group and then pipe that into a multi solver with a sop solver that scales down everyting in the group "impact" but it doesent seem to work, the same setup works if I set it up with a single RBD object, and dopnumrecords(".", "realNameOfsingleRBDobject", "Impacts", "Impacts")>=1 but it seems to have to be different with a fracture/glue object and / or using $OBJNAME instead of the real string name of the object any help would be greatly appreciated thanks -johnc
  13. fracture animating object

    AWESOME, I knew there had to be a way to do it. :-) I will begin dissection.... now. thanks so much -johnc
  14. fracture animating object

    unfortunately, not yet, I'm still working on some ideas, but am currently working around the problem. there are some videos I've seen from Igor Zanic that sorta does what I want to try to achieve. Igor? you out there? -j
  15. fracture animating object

    Knowing the way houdini users are, I know there must be some way to pull this off, I just don't know how complicated it could get. I have a walking figure geo cached. Is there a way to pipe that animated cache into the fracture system, so that it breaks off pieces and they turn into RBD's but the main chunk still stays animated? I'm thinking this may end up being some sort of cyclic nightmare where it may be impossible to plug the result of a fracture back into its own input. I think it should at least be possible tho to latticeSOP the pre-broken geom as non solving RBD objects until they "kick off" and then when that happens, turn them into breakable objects so that when they fall and collide, they can sub-crack recursively. if anybody has some tips as to the workflow I'd have to try out to make this work, that'd be awesome. thanks in advance -johnc redpawFX
×