Jump to content

Skybar

Members
  • Content count

    1,144
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    31

Skybar last won the day on March 22

Skybar had the most liked content!

Community Reputation

343 Excellent

2 Followers

About Skybar

  • Rank
    Grand Master
  • Birthday 11/28/1991

Personal Information

  • Name
    David
  • Location
    Sweden

Recent Profile Visitors

8,926 profile views
  1. Bullet Heightfield collision

    It's something with transforms. If you look inside the HeightField File SOP, it samples the COP in the XY Plane and then transforms it to ZX. If you do that too it will work.
  2. Pyro: Match vdb source and sim grids

    Not exactly sure what is going on, but if you unlock the smokeobject and change the Voxel Sampling to Edge XZ on the flame field it will match. Thats the only thing I changed. Or you can transform your source field with half a voxelsize in X and Z (0.015 in this case), seems to have the same effect pretty much.
  3. It's usually easier (and more inviting for people to help) if you share a hipfile showing where you are stuck, it can be difficult trying to decipher what you are trying to do let alone fix it through text.
  4. Sparse pyro solver temperature and buoyancy

    Yeah seems a bit weird. Probably an attempt to solve something with math (tying it gravity?) instead of just exposing the correct parameters. Which is weird if it's supposed to make it simple, because we get a few more parameters that are harder to understand for buoyancy - instead of just having the 3 well known ones (direction, amplitude and ambient). Delete that expression in Bouyancy Lift on the Gas Buoyancy DOP and use it normally seems to work well.
  5. Depends on what you mean exactly. In your example you can create a detail attribute and grab it in the parameter with expression, for example: detail(opinputpath(".", 0), "amount", 0) That will grab the value of detail attribute called "amount" from the node that is connected in the input.
  6. Game of Life Algorithm - Open CL vs VEX

    The OpenCL node errors in your scene for some reason (im on 18.0.416), so can't test. But your problem is most likely reading and writing to the same attribute in the same kernel. You want to use a Write Back Kernel for this. If you hover over the "Use Write Back Kernel" it explains a bit what happens.
  7. How to get correct Motion Blur

    For most volumes you will need a velocity volume and use velocity blur. For this case you could also create the volume -> pack it (Pack SOP) -> then move it with a Transform SOP. The transformation data will then be on the packed object and it will blur correctly.
  8. smoke has a hairy look

    I think the main problem is that you are adding disturbance everywhere all the time. A popular method is to use the speed of the velocity field as a control field for example, so you scale the disturbance amount with how fast the smoke is moving.
  9. How to get correct Motion Blur

    For Deformation Motion Blur (stuff happening in SOPs), you have to set "Geo Time Samples" to at least 2 on the Mantra ROP.
  10. smoke has a hairy look

    Too much disturbance probably.
  11. Procedural Potion Bottle Tool

    It's because the ramp is a float. You are saying that vector = float. If you skip the ramp and do vector hillProb = rand(seed+2); you will get a random vector.
  12. You mean you are flipbooking while simming? You could try the "Leave Playbar at Last Frame" on the flipbook options.
×