Jump to content

AustinW

Members
  • Content count

    4
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About AustinW

  • Rank
    Peon

Personal Information

  • Name
    Austin Wendenburg
  • Location
    Vancouver
  1. Redshift instancing issue

    I found the problem (and it's obvious in hindsight) but one of my 28 instances had no geometry, I removed it and error gone.
  2. Redshift instancing issue

    Just chiming in to say I'm having the same problem... Did you two ever figure it out?
  3. How to combine vellum and rigid body?

    Look up the "Shape Match" vellum constraint, should do exactly what you need!
  4. Thanks in advance for the help! I'm advecting a vdb so it grows over time. Once turned back into polygons, I'm hoping to stick UV's on it. The setup - I promote my uv's to point attribute and in the initial "VDB from polygons" I created a new surface attribute to store the uvs - I advect both vdb volumes in a sop solver, and then convert the vdb to polygons. - I then use an "attribute from volume" node to transfer the uv's from the volume onto the mesh. This works for the first frame, but as expected distorts and breaks down pretty quickly as the volume grows. I've researched and found examples of using the "dual rest fields" option in the Pyro and Flip Solver and then blending between the two rest states to "reset" the texture distortion as the mesh grows. There is a great example of this by Jesper Rahlff here (https://forums.odforce.net/topic/49461-lava-flow-question/?do=findComment&comment=227475). Great! I can create a rest field but... - What exactly is rest2? how is it different from rest1? - And how would I go about setting it up here without using the pyro or flip solver? If you have a better way to achieve this always open to that too VDB_Advect_UV_rnd_v02.hiplc
×