Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


Atom last won the day on February 8

Atom had the most liked content!

Community Reputation

843 Excellent

About Atom

  • Rank
    Grand Master

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location
    Columbus, Ohio

Recent Profile Visitors

9,543 profile views
  1. Just use two wrangles. Wrangle #1: vector thePos = point(0, "P", 0); // Input point's pos is {0,0,0} thePos += {1,2,3}; setpointattrib(0, "P", 0, thePos); Wrangle #2: thePos = point(0, "P", 0); printf("%d ", thePos); // Prints {0,0,0} instead of {1,2,3}
  2. ocean + ripple solver setup

    You might want to take a look at some of the options on Tokeru. http://www.tokeru.com/cgwiki/index.php?title=HoudiniExperiments#Bow_vectors
  3. Carve Contour Lines In Car Body

    Nice setup Konstatin, I have taken the result from your file and symmetrically re-fractured it, adding displacement to the newly fractured pieces. Here is it with another scatter seed and a different UV projection type.
  4. Better GPU for work

    It's nice to stick with nVidia in case you decide to jump into GPU rendering.
  5. FLIP smorganic/sheeter effect?

    Nice work, does this make use of the new H17 retime node?
  6. Better GPU for work

    Just do your homework and google it. 1080 vs 1080ti. https://gpu.userbenchmark.com/Compare/Nvidia-GTX-1080-Ti-vs-Nvidia-GTX-1080/3918vs3603 You get 26% more computing power for 28% more cost.
  7. Learning redshift

    Many of the gotchas, I experienced when I first started using Redshift have been ironed out with the continued development of the plug-in. Mainly an object that does not have the ObjParms applied to it can cause some problems. If they are not present, attributes will not be automatically forwarded to the material section. This can happen if you open old files and try to adapt them to Redshift. However, newly created objects do have ObjParms added by default, so just double check that if things seem like they are not working correctly. Another gotcha that I still run into is not experiencing glow from material emission on surrounding objects. This is because GI is turned off by default. You need to turn on one of the methods (typically Brute Force) to get some kind of emission bounce. But this is often the case with other render systems as well. Balancing density and temperature values in the volume shader can take some time too. I have adopted the workflow where I don't push density at all in the guides, and this helps get a better 1:1 match from viewport to render. Push your density values at the attribute or scale level, instead of guides. There is the 16 bounce limit on reflections as well. If you need more than that, you have to leverage the sprite cutout node instead of just relying on the standard material. Meshlights don't inherit v@Cd from points so you have to bake maps for multi-colored meshlights, but single colored meshlights work fine.
  8. It would be nice if these toggles were available under MPlay preferences. I can't tell you how many times I have flipbooked something which generates a completely valid cache only to have the cache disappear when I close MPlay to reset my view. The clearing of the cache might be related to jumping back to frame #1.
  9. Pyro clustering problems

    The problem I see with your setup is that your cluster areas are changing size. The approach that worked for me, in pre H17 was to create a line out of the points in motion. Then use that line to create cluster segments. Then generate points along the line as single frame bursts to activate the cluster when the fuel enters the boundary region. Here is an old H16.5 setup that show particles leveraging clusters. Maybe this setup can help you fine tune yours? ap_particle_cluster_020719.hiplc
  10. Curve parallel offset

    Check out the node PolyExpand2D, it might help in certain situations.
  11. Forest campfire rendering in Houidini Mantra

    It look nice, good job!
  12. Houdini 18 Wishlist

    I wish SideFX would not change the work flow so I have to learn everything I already know all over again.
  13. Save as text

    You mean the scene? Check out .asCode(). http://www.sidefx.com/docs/houdini/hom/hou/Node.html
  14. I don't think you can create a final merged mesh via instancing. With instancing, all that exists is points. Just use the standard CopyToPoints and wait for it to generate the large poly count of meshes. Then use a FileCache to write it out as a single .bgeo.sc. I did a video tut on leveraging instancing with Redshift's .rs file format, including how to get the copies to show up in the viewport. There have been some updates to the process, but the basic workflow is still valid.
  15. Sure, drop down an instance node then transfer what is inside the FOREST node into the instance1 node and choose Full Point Instancing. Remember to add ObjParms under the Redshift shelf to your nodes. ap_RS_forest_001.hiplc