Jump to content

jujoje

Members
  • Content count

    59
  • Joined

  • Last visited

Community Reputation

9 Neutral

About jujoje

  • Rank
    Peon

Personal Information

  • Name
    Julian
  • Location
    Berlin
  1. Also it takes point groups / expressions. E.g.: // Set Cd @Cd=0; // pcfind float radius = ch("radius"); int maxpoints = ch("max_points"); // Mask string string mask = "@P[0]>0.5"; int pointcloud[] = pcfind(1, mask, "P", @P, radius, maxpoints); foreach( int point ; pointcloud){ @Cd = {0,1,0} ; } Will only look at the points whose x position is greater than 0.5 pcfind_mask.hiplc
  2. From my understanding the Pc find is a convenient way to iterate over a point cloud; it returns an array of the points and then, typically, you run those points through a foreach. This is roughly equivalent to doing a pc open and using a while loop to iterate over the points. Which makes your code/vop network much shorter and cleaner
  3. Use pcfind and a foreach? So something like: //Set color to black @Cd = 0; // Pc find float radius = ch("radius"); int maxpoints = ch("max_points"); int pointcloud[] = pcfind(1, "P", @P, radius, maxpoints); foreach( int point ; pointcloud){ @Cd = {0,1,0} ; } I think that's what you were looking for... pcfind_example.hiplc
  4. Pyro Shader in houdini 16

    Have a look in /mat rather than /shop. SHOPs are heading towards depreciation so you should probably err towards /mat and material networks when creating new shaders.
  5. Not sure about 1, but on the FEM front: 2. There are a few attributes to control FEM; the relevent ones for making it follow an animation are tagetP, targetv, targetstiffness and targetdamping. There is also pintoanimation, which would be the logical choice, but from what I hear it's giving some weird results at the moment, so I'd try the target attributes first. For a list of all the attributes check out this page in the docs: http://www.sidefx.com/docs/houdini15.5/nodes/dop/finiteelementsolver 3. I'm thinking that some combination of targeting the skin to the collision geometry might work. From my doomed attempt to create a FEM muscle system I discovered that the soft body constraint is broken with FEM (or was last time I checked), which is kinda annoying as that would have been the obvious choice. That said FEM appears to be both a lot more stable and faster these days, so could prove really powerful for rigging. Just wish I had more time to look into it myself at the moment. Be curious to hear how you go!
  6. Bake texture ROP outputs black...

    Just to say you're not going mad I've been having a look at baking textures out in 15.5 and if I add displacement everything goes black. Prior to adding displacement, everything was just dandy with mantra spitting out diffuse, spec etc. On the subject of baking , I can't seem to write out ptex files either (rat, tga etc using UDIMs are fine), so wondering whether I'm doing anything wrong. Shall hopefully post a .hip later...
  7. My laptop is so not going to handle the scene and away from workstation so can't check your scene, but remember having the same issue with trees from speedtree. I came to the same conclusion as Marty with pretty much the same solution; ended up creating an LOD on the trees and rendering the leaves as points when they're a ways off and blending which fixed the problem (well not so much fix as workaround...).
  8. Houdini 15.5

    Awesome update The modelling tool improvements in particular are much appreciated (it was a long wait for the bevel, but totally worth it)!
  9. Dry Lights

    Really stunning work
  10. Hi everyone, Having a look at stylesheets and having a bit of difficulty with them, and was hoping someone could point me in the right direction What I’m looking to do is bind the intrinsic:indexorder at one level and then use this value to randomise an attribute at a lower (group) level. This should be relatively straightforward if I'm understanding this paragraph from the docs right: Higher target levels in a targeting hierarchy can also bind the value of attributes at that level. You can then make those bound data available as arguments to the CVEX script. So I’ve got a sop object containing 7 packed objects. Inside those packed objects is a primitive attribute, @tag, which I want to control a material parameter (basecolor). SOP Level Geometry - Target (Packed Objects) Bind id here (intrinsic:indexorder) - Subtarget (Prim Group, e.g. @tag=tank) Apply override using id from higher level Since an example is probably better than my explanation, I’ve attached an example scene. The scene has got two stylesheets, one using the path attribute, which works fine and one is attempting to use the @tag attribute, which doesn't. The stylesheet ui looks like this: I’m relatively certain I’m missing something obvious (style sheets being an exciting new world), but can’t seem to work out what it is (I keep moving the bind around to no avail...). odforce_packed_example.hiplc
  11. Just to check, but you are unpacking it before adding the crease weight right? Perhaps it would be a better to do the crease weight before you pack the geometry and send it to dops. This would save the unpacking and be a bit more efficient.
  12. Wiki!

    I voted no; as with others I found the wiki really useful back in the day, but now the Houdini docs are improving at a fair clip I haven't used it for a while. That said, one of the things I have found useful is the list of studios using Houdini (as I was looking for work recently). It would be nice rescue that page in some form, although perhaps it would be better as a pinned thread on the forums?
  13. Link to cached geo in ifd files

    One thing you should check is that you are loading the sim's caches back in as a packed object. That way the ifd generation should be super fast as it's just pointing to the file on disk rather loading the actual geometry.
  14. If you're using packed geometry you could possibly use the Packed Disk Edit node to change the disk path to point to the highres object: http://www.sidefx.com/docs/houdini15.0/nodes/sop/packeddiskedit
  15. Also updated; working pretty good on my MacBook (GeForce 650m). Another nice thing is that you can preview obj and alembic files in finder (and open them in Preview) Fullscreen would be awesome. Was using Maya 2016 fullscreen in split screen mode; it was pretty nifty.
×