Jump to content

tagosaku

Members
  • Content count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tagosaku

  • Rank
    Peon

Personal Information

  • Name
    tagosaku sky
  1. use sourceVolume node as collsion for flip and pyro sim

    To jamesr, Yes, I did. That's why I can see correct collsion shape in visualizer. Hopefully someone provides me a collision sample file of either flip or pyro sim...
  2. use sourceVolume node as collsion for flip and pyro sim

    hi, Peon Do you mean VDB surface won't work as collision with sourceVolume node? I tried pyro sim and FLIP sim with sourceVolume node using as static collsion, and I clearly see collision shape by FLIP/pyro object > Guides > visualization > collision, but it's not colliding very well. I guess a visualizer shows the exact collision shape but actual collision sim does not happen.
  3. hi, I tried to use sourceVolume node as dynamics collision. So far, I tried the both of FLIP sim and pyro sim and can see a little bit influence, but it's almost not colliding at all. For instance with FLIP sim, I set: 1 - source volume > initialize > collision. 2 - check binding is correct. 3 - FLIP object > Guides > visualization > collision. I can confirm collision exists in viewpoint. The result looks almost zero collision. I knew this method is not accurate compared to staticObject method, but I could ignore a little lower precision. In fact, it's absolutely NOT acceptable result. On the other hands, when using staticObject, it always works perfect. Is this the exact reason that people combine to use staticObject node for collsionSurface and sourceVolume to add collsionVelocity? In conclusion, Have anyone succeed to use volumeSource as dynamicCollsion? What's differences of colliding mechanism between staticObject and sourceVolume?
  4. hi, I have a question about pyroshader in houdini16. There are fire shading and smoke shading parameters separately. That's why I was thinking we could control alpha of fire and smoke separately, too. However, when I change general > smoke > Density Scale value, it influences to fire alpha, too. Then if I set the density scale to zero, actually fire alpha also becomes zero although fire's RGB shows red-yellow color. Thus questions are: 1 - what's the reason/concept we don't have a separate "fire density(alpha) scale" parameter? (Of course, we can separate fire and smoke by AOV with smoke_mask and fire_mask.) 2 - Let's say I need to create a custom shader for it. What kinds of two volume fields should I use for fire and smoke's alphas? Also, inside of pyroshader, there is a pyroshadercore node, which is an essential node but cannot be unlocked.
  5. apply boolean twice problem

    it sounds boolean node is really designed to use once. Thanks for your tip. I will check it out!
  6. Yes, I installed SP1, but it happened. The solution was to reinstall windows from reformat again. The second round worked out. Thanks, guy!
  7. substep settings for dopnetwork

    Hi, I have substep setting questions when an object(emitter and collider) moves very fast. I am expecting to change 3 points: 1 dopnetwork > simulation tab > substeps 2 pyroSolver > advanced > min/max substeps I am not sure which one I need to change the above?? 3 emitter (collider) should be produced substep volume(denisty/SDF). From the volume/VDB, can we produce inbetween volume/SDF objects with timeBlend and/or attributeInterpolate? Or actually houdini will automatically handle all the substep sources?? I guess if meshes which are before converting to volume are able to create substep, FluidSOurce and VDBfromPoly nodes could create substep volume. But what if mesh is cached, what's happen? Ultimately, I believe ex-colleague showed me that he made a pyro tiny smoke, and created 4x slower motion post-smoke by somehow interpolating. Thus, if anyone knows substep settings and post-slowmotion voxel anim, I really appreciate it!
  8. apply boolean twice problem

    hi, when I try to use a boolean node twice, second boolean result is always broken because I guess a connectivity issue. Houdini cannot understand the connectivity from first boolean result. I know some people says to cut together with many cutters, but I have a certain situation to cut separately. For instance first boolean produces 500 pieces, and keep 300 pieces and use second booleans for other 200 pieces, and so on. Some artist do after-1st-boolean > loop start > delete all pieces(groups) except one favorite piece > do-2nd-boolean > loopEnd > merge together. Or, I do translate and separate each other of pieces in order to make spaces between each pieces, then apply 2nd boolean, and it works I wonder if anyone knows smarter methods, instead of translating or looping booleanTwice.hipnc
  9. Because I needed to reformat Windows7, I also reinstalled Houdini, and got strange UI. The node info is broken. Does anyone have ideas how to fix? OS, hardware, videocard, and houdini version should be also same as before. I tried houdini 16.0.600,630, 504, but all same strange result.
  10. Because I needed to reformat Windows7, I also reinstalled Houdini, and got strange UI. The node info is broken. Does anyone have thought how to fix? OS, hardware, videocard, and houdini version should be also same as before. I tried houdini 16.0.600,630, 504, but all same result.
  11. expression for cache path

    umm, the result is not right..
  12. create auto-activation for source volume DOP

    I solved it by F1's help, thanks activation> (strcmp(prims("../../IN_coll", 0, "name"), "density") == 0) || (strcmp(prims("../../IN_coll", 0, "name"), "surface") == 0)
  13. nCloth's input mesh attract for houdini cloth

    that's great. I will test it out, thanks!
  14. prim expression for source volume activation

    Oh, I am sorry too that I just knew there are TWO expressions, "prim" and "prims" !! I completely misunderstood them. Thank you, f1, so much for providing a sample file. I am checking it out right now!
  15. Hi, I am looking for auto-activation for source volume node in DOP based on an input object(VDB, houdiniSDF). This is because sim is broken, if the sourceVolume set to collision and there is no SDF primitive(@name=density or surface). So far, I tried 2 methods, but not working. A - use expression in activation, but something not right. B - use enableSolver, but probably it needs to place inside of the sourceVolume. If anyone has better ideas, please let me know, thanks sourceVolumeActivation.hipnc
×