Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Gigglebooster

  • Rank

Personal Information

  • Name
    Zach Henry
  • Location
    Denver, Co
  1. Redshift smoke issue

    Hi. Could someone please help me with rendering this smoke in Redshift. I'm able to render the smoke correctly on the 1st frame, but then as the render goes it starts to cut parts of the smoke like it's being clipped, but it looks correct in the viewport. I've tried changing the settings in the material and light but can't figure it out. I watched the Entagma video on rendering volumes but he didn't appear to run into this issue. I attached my hip file on this, any help would be appreciated, thx. PyramidSmoke.hiplc
  2. Color disappears after adding instancefile

    Nvm figured it out, it's answered at the end of this video in case anyone else is wondering -
  3. Hi, sorry if this has already been asked haven't been able to figure it out. Is there a way to keep your color after creating an @instancefile attribute? To clarify, I'm using Redshift and when I create an @instance attribute and point it to my object the objects @Cd will come through in the render, as long as the object the @instance attribute is pointing to is using a shader that has an RS point attribute node plugged into it. However, if I create an @instancefile attribute instead and point it to the .rs file I exported to my harddrive it will not show this color. Is there a trick to getting this color to show? thanks.
  4. Ah gotcha. What I meant was that I didn't realize you needed a loop at all for this, I was just trying to reference the null without one and it wouldn't work. Good to know too tho thx!
  5. That's exactly what I needed Noobini ty! I didn't realize you had to add the node you are referencing to a for loop like this
  6. Hi thanks for the reply. I understand what you are doing now, but I'm still not getting how to reference the parameter of the the geo being copied. I understand that pscale can be adjust on the points before it's being copied to effect the overall size, but for what I'm trying to do I only want to effect the y radius or y scale of the torus and not the entire size. Also, I want to plug that into a point VOP and setup a ramp so that I can control the attribute that is effecting the radius size. That's why I wanted to create the test attribute and use that, so that I could then use @test in a VOP and control that. Is there no way to directly reference the attribute of a point it's being copied to?
  7. Yes, that's what I'm doing for. How did you do that? Basically, I'm trying to make the radius change based on the float attribute of the point it's being copied to. The float attribute in my scene is called @test, so I'm trying to set the radius y as the @test attribute so that one would have a radius of 0, and then the next .1, and the next .2.
  8. Hi, I've been stuck on this issue for awhile. I have a line and I'm giving each point a float attribute called test, it goes from 0-1. Then, I'm copying torus on to those points, but I want to make the y radius of the torus equal to the @test attribute of the point it's being copied to. So one end would have a radius of 0 and the end would have. I'm trying to use a point function to do this but can't get it to work, here's the function I'm using in the radius y parameter of the torus - point("../OUT_POINTS/", 0, "test", 0) Any help would be appreciated, thanks. question.hiplc
  9. Ah cool! Glad you figured it out. I'm the one who responded to you about this in the houdini reddit thread on this. Didn't know how to fix it exactly but figured it had something to do with triplanar textures. My textures from Quixel were coming through as triplanar and I had a bunch of issues with them sliding when my objects moved, once i got it off triplanar to a normal texture it fixed the issue but wasn't sure how to fix it in your situation.