Jump to content

jamesr

Members
  • Content count

    120
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    1

jamesr last won the day on August 7

jamesr had the most liked content!

Community Reputation

23 Excellent

About jamesr

  • Rank
    Initiate

Personal Information

  • Name
    James
  • Location
    Los Angeles
  1. How to see pyro field values

    In the dop i/o sop, you can check out "Compute Min/Max Values", which will create a couple of extra primitive attributes. Alternatively, you can see the same values in the intrinsics of each field. volumeavgvalue, volumemaxvalue, volumeminvalue are all good ones.
  2. Grouping points from array

    Ohh yeah this is much better, thanks!
  3. Grouping points from array

    Here's a solution: the left side does it one wrangle, the right side groups, colors and deletes raycollisionTest_jr.hip
  4. Tools --> Show Grid --> Grid Lines
  5. If you MMB on the IsoOffset, you'll see the number of voxel on each axis, as well as "size".
  6. object node name

    `opname("..")`
  7. create pod exhaust wash

    In sphere_object1, you should check your collision source. Since you are deleting the faces at the bottom and leaving a hole, the VDB is not being created correctly. You can bypass the file cache sop and check it out. This will help keep your fluid from pushing through the top. Also, try giving your fluid source a little bump of velocity in -Y edit: I also think you would benefit from splitting this into two separate sims - one for the downward thrusters with fast velocity and a lot of dissipation, and another for the wash on the ground. @eetu has a fantastic wash example on his site.
  8. relative reference without value return

    What paths are you trying to change? You're just trying to put parameters into the slots on a wedge ROP right? But you don't want to write them each manually? I guess you could try `opfullpath("/path/to/pyrosolver") + "/parameter"` and swap "parameter" with the name of the part you wanna change. Is this what you mean?
  9. Expression removes the points ?

    @CinnamonMetal I just picked an arbitrary range as an example Edit: whoops you were replying to the other
  10. Expression removes the points ?

    To expand up Noobini's reply, you should put the result of the rand() into a fit01() function and you'll get results that range between your desired amounts. Can throw a floor() on there to force an integer while you're at it too, but not really necessary in this case (but maybe others in the future....) floor(fit01(rand(detail("../m", "iteration", 0)), 2, 10))
  11. Access NodeA-Paramter in NodeB

    I think I have an idea of what you're trying to do, but having sort of a hard time understanding your terminology. Could you post quick hip with an example of what you're trying to do ? Otherwise, if you're trying to link parameters 1:1, you want to right click the parameter, and select "copy parameter". then in the destination parameter right click and again do "paste relative references". This will make the parameter drive the other one.
  12. disturbance when velocity

    This is the technique they're talking about. I highlighted the nodes in yellow with an explanation for each. Thanks to Stephen Knipping for the trick Velocity is not the same as speed. What you're looking for is to control the disturbance in areas of greater speed. Speed is the same as the magnitude (length) of the velocity vector. The reason you put "vel" into the control field, is because inside the vop we will tweak it to calculate the length instead, and use that. You cannot only enter "vel" to make it work how you want. Gas disturb by default affects the temperature field. Temperature can play a major role in the look of your sim because it affects velocity. But it doesn't do any good if you're not using temperature in the sim, or if you want to affect the velocity field directly. You turn on "control field is vector" in order to get the switch to switch to the correct gas field vop inside. gas_disturb_velocity.hiplc
  13. Oh yeah I see that. I guess that sort of works, but I'd stay away from doing it that way since it's not really working as expected. You shouldn't actually need to put the v@ in the second wrangle in this case.
  14. static gas turbulence?

    Here's a quick hip with the stuff to change in red static_gasturb.hiplc
  15. static gas turbulence?

    If all you want is a static noise field for the pyro to swim through, you can just use a curl noise in a gas field vop. If you want, you can just copy and paste the one inside the Gas Turbulence microsolver inside "compute_turbulence". Inside the gas turb, it uses a vec4, with the fourth component after the position vector being time. So it doesn't matter if the pulse duration is off, it's still moving through time by default, because pulse duration is connected just to the offset parameter. You can unhook this and just use pos (vec3) to drive the position of the noise and run your pyro through it.
×