Jump to content

ChazS

Members
  • Content count

    32
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ChazS

  • Rank
    Peon

Personal Information

  • Name
    Chaz Sutherland
  • Location
    California
  1. Path following disparity

    It's obvious now that I was really overthinking it. Splitting after a dopio hadn't occurred to me to even try. That is what you mean, correct? I only ask since this is still new to me and I don't want to make any assumptions. I split the forces in the dopnet (which is where the disparity happened) but your solution was to kill one of those streams and split it after the dopio node. Your solution is so simple and elegant.
  2. Path following disparity

    What a simple and embarrassingly obvious fix *face palm*. It's so good that (despite my curiosity about my posted issue) I'm going to call it done for now and move on. Thanks Jesper.
  3. Path following disparity

    I hope a particles issue qualifies as an effect, so you have my apologies if this is the wrong sub-forum. However, if I'm in the right place my dilemma is as follows... ...In the attached file is a simple double helix curve and a dopnetwork pulling the particles upward on it. What's curious is why the particles move up the curves at different speeds. Especially considering that the two curves are using the same POP Curve Force & popstream nodes... how is this possible?? I've tried multiple things, like switching the poplocation inputs that feed its appropriate helix and turning off the gravity to no avail. The best result was adjusting the Pop Curve Force node >> Global Forces tab >> FORCE ALONG PATH ramp. This adjustment brings them close but still not quite right. Anyway, thanks in advance. followPath.hipnc
  4. The latest version of the source volume dop has a new name (sourcevolume >> volumesource) but more so, tabs have been consolidated into one... I think?? At least it looks that way since the volume operation and mask components seem to reside in this new, single volume tab. Anyhow, here's a snip of both versions and my attempt to translate from version 16 to 17. Am I doing this right?
  5. Looks like I had the wrong nodes visible. Anyway, answered here ::
  6. Oh wow... that's just awesome, thank you. I think I get it now, the geo is being channeled into the dops purely for the sim, so the geo remains visible to coincide with what the dop does. However now I'm wondering about the sop that creates the surface of the water from the particle field. It has a fluidcompress & particlefluidsurface node in it (which I understand) but it also has a dopimport node in it. Even when bypassed, the sim still works and renders. What is the dopimport for? Anyway, thanks for the assist.
  7. I believe I do... at least a little. In the render tab of the sop is a Material parameter, right? At least that's what worked before running it through the dop. If I shut off the dop and make the sops visible, they render fine, so I'm at a loss about why.
  8. When pumped through a dop network, a basin, floor (terrain objs) and a cup (static obj) lose their textures and appear white in the scene view and renders as such. Might be worth mentioning this has a flip pour out of the cup into the basin that doesn't appear at all. Anyone?
  9. Oops, realized this should be in the lighting and rendering section. Anyway, consider this thread dead. I'm re-posting in the correct place.
  10. When pumped through a dop network, a basin, floor (terrain objs) and a cup (static obj) lose their textures and appear white in the scene view. Might be worth mentioning this has a flip pour out of the cup into the basin. Btw, the entire scene won't render either. It gets hung up on "Generating Scene.....". Anyone?
  11. I just used 'recuva' to unearth an accidentally deleted hipnc files—and despite the files appearing in excellent health—Houdini won't open them. "Unexpected end to hip file" is all that pops up. The files were recovered off an extended drive (original location) the moment the deletion occurred. I didn't do anything else until the recovery process could be started. The newly recovered files were written to a different drive to ensure that the old files weren't being clobbered. Anyway, I don't have any type of extended support with sidefx, so it appears I'm on my own. After much futility, I recreated the file structure, and opening from the former folder location, but that isn't working either. Setting the scene to manual has also failed. I've used the open file command and also double-clicking the file to initiate the opening process. Nada. Strange enough; even after the error appears, when the file is being shut down, Houdini prompts me to save or discard the file that couldn't be opened...? I was wondering if anyone else has successfully dealt with this issue and how they managed to do it? I've used recuva to great success in the past, but this time... blah. At this point I'm wondering how to rescue the files that have been recovered (if possible). Thanks in advance.
  12. Bezier handle wonkiness

    You are now officially family. Many thanks!
  13. I've a simple anim on my camera so that it rotates on an offset Y-axis to keep the subject center frame. In the Animation Editor is the expected default z-curve, however, I want to invert the slopes so that it's shaped more like an s-curve, but the handles go nuts when I try to move them. They twitch like mad and want to snap to the key rather than be pulled away or rotated off the horizontal axis. Swinging them above or below the key is impossible. I've been selecting different buttons in and about the editor but nothing is working. My thought that untie would do the trick but it didn't work. Is the key in some state I don't know about? I've love to know... Thanks in advance.
  14. @Noobini:: Wow, that was fast, thank you. I can see what you did, but have to get my head around it now. Thanks again.
  15. Hello, I'm currently messing around with sop solvers and have two questions that I hope you can help me with: I have 5 spheres in a scene being spun by popaxisforce node which also transfer their colors to a floor grid—and that part is working—but I can't see the spheres. When the solver is selected, they disappear despite their attributes being visible (middle-clicking the solver node). How do I get them to appear when the solver is selected? Second is how to cause the spheres to translate the points in minus-Y instead of transferring the colors (causing a rut in the grid)? Since the spheres are already affecting the point color, I figured that captured point data could be translated instead...?? I've tried creating groups and such but nothing I've done so far has worked. Any suggestions on how to approach this? Many thanks. missingSpheres.hipnc
×