kgoossens Posted September 30, 2013 Share Posted September 30, 2013 Hi I'm looking for Idea's on how to increase modeling performance for my courses I teach. There are many things that come to mind. -Using wrangle nodes. -Building custom versions of some existing nodes with limited functionality such as a vop's ray node. -Using attribute transfer instead of ray sop -Using point clouds. -Avoiding foreach nodes. -creating a minimalistic representation of the final result for fast turnaround times. -unloading of nodes Any other things, techniques for a specific solution, like the "Group in Mesh" on Orbolt from Sergei Bolisov. would be very welcome to hear about. Cheers, Kim 1 Quote Link to comment Share on other sites More sharing options...
yongbin Posted September 30, 2013 Share Posted September 30, 2013 Recently I found foreach with variatioin attribute usually make it way faster (so, make it possible to use ) than just iterating all prims/points. It doesn't always work. But if you know when you can use it, it can be really powerful. Example file and otl attatched. foreach_with_vari_attrib.hipnc yb_curve_tools.otl yb_timeshift_pp.otl Quote Link to comment Share on other sites More sharing options...
yongbin Posted September 30, 2013 Share Posted September 30, 2013 Hi, kgoossens. thank you for many tips. I am especially curious of your last suggestion. How can I unload a node? What does it mean? Quote Link to comment Share on other sites More sharing options...
magneto Posted October 1, 2013 Share Posted October 1, 2013 You have to right click a node and click Unload. A different flag is shown on the node. 1 Quote Link to comment Share on other sites More sharing options...
yongbin Posted October 1, 2013 Share Posted October 1, 2013 Hi magneto, I tested it, and it works! Thank you. But still didn't get what it actually mean. So.. give me more hint, please? Quote Link to comment Share on other sites More sharing options...
magneto Posted October 1, 2013 Share Posted October 1, 2013 So when you unload it, the memory of the node will not be cached AFAIK. Imagine a very expensive operation that stores copies of the meshes to calculate a final result. You don't necessarily want to keep them in memory after it's done cooking. Quote Link to comment Share on other sites More sharing options...
yongbin Posted October 1, 2013 Share Posted October 1, 2013 Unload after cooking! Now I got it! Thank you~ 1 Quote Link to comment Share on other sites More sharing options...
hyperforce Posted October 16, 2013 Share Posted October 16, 2013 To my knowledge unloading is only really effective if you are not doing a recursive or manual operation on or from an unloaded node. Otherwise it will have to recook the node constantly and with recursive nodes it can increase cooking time significantly. Starting from Houdini 13 you'll be able to create polygonal geometry using Wrange nodes. Things like making curve connections between points based on distance is really neat, and it can be made 100x faster & memory efficient with a wrangle node then doing it with a for-each node. Quote Link to comment Share on other sites More sharing options...
yongbin Posted October 16, 2013 Share Posted October 16, 2013 Starting from Houdini 13 you'll be able to create polygonal geometry using Wrange nodes. Things like making curve connections between points based on distance is really neat, and it can be made 100x faster & memory efficient with a wrangle node then doing it with a for-each node. That's great! Thank you for letting me know! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.