Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

iFight4theUser

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

1 Neutral

About iFight4theUser

  • Rank
    Peon

Personal Information

  • Name Ryan
  1. In case that is what you are looking for here is the setup. goosebumps_example.hiplc
  2. Like this?
  3. Hey, yeah that totally works. I don't know why I thought that didn't work in the past. Thanks!
  4. Thanks Konstantin, I pretty much ended up doing that. I just encapsulated the network into a VOP OTL so that they will both pickup changes. The only trouble now is that I have a ramp parameter on my shader and on my point vop and I can't get them to stay in sync.
  5. This sounds like a job for "point deform." transferDisplacement_02.hip
  6. I've run into this issue a few times now. I have a shader that generates several output variables for extra image planes. The variables that are generated would be really useful in SOPs. The only thing I can think of that would allow me to run the same calculation on each point, is to collapse the SHOP network into an OTL that I could also exist inside a VOP. But the parameters are being driven on the shader and it seems a bit messy to channel reference all the ramps and other parameters. Is there some way to apply the shop_materialpath and then compute and export a variable on a per point basis? Thanks!
  7. If the geo is too complex or thin for VDBs you can try using xyzdistance inside the solver to pull the nearest surface position. You'll need to recalculate your velocity vectors afterwards though, so not as elegant as the VDB solution. Nice example Sean the volume gradient idea is really clever. int primID; vector primUVs; xyzdist(1,@P,primID,primUVs); // get the primID and primUV of the nearest prim on input2 @P = primuv(1,"P",primID,primUVs); // move the P to the position on that primitive
  8. When I create rest using the rest SOP if I do a transform down the chain it will alter the rest position as well. But, if I create the rest attribute using any other method it won't be altered, maintaining it's value, as expected. Why does a transform SOP edit the restP? restTranslateTest.hip
  9. So... Does anyone know of the -SEGV equivalent in Windows..
  10. I have an issue. I was using 3 monitors. Now I'm down to 2. I've blown away my houdini settings. Still though, when I open new floating windows, they appear off screen and I can't reach them. How do you reset these floating window positions?
  11. Thanks everyone. Opt #1 from Luke solved the issue. Unfortunately the otl is changing pretty frequently, so the "saving it to the hip" option wasn't working out for me.
  12. I'm working in Windows. We've gotten HQueue running on 5 different machines. I've built a few OTLs that are stored on the server and accessible by the farm machines, but the farm doesn't seem to be seeing them. What's the proper workflow for this issue? I'm currently trying to figure out how to append there directory to the HOUDINI_OTLSCAN_PATH variable, but I can't find it listed anywhere. When adding the OTLs I'm "Adding to scanned OTL Directories", but on restart they are moved to a "Fallback Library" which sounds questionable... lol