Chris Rydalch

goldleaf

About Me

Expertise
Technical Director
Location
United States of America

Connect

My Tutorials

obj-image Quick Tips
Keyframe Functions, Extrapolations, and Box Handles
obj-image Intermediate
IFD Workflow Basics
obj-image Beginner
Mantra Light Instancing Basics

Recent Forum Posts

Python command to list all nodes in houdini? July 14, 2018, 8:27 p.m.

You can also list all of the node types from a version of Houdini with this command:

hython $HFS/houdini/python2.7libs/opnode_sum.py > all_nodes.txt

If you run that from two different versions of hython, you can diff the results. For example, this compares 16.5.323 and 16.5.473:


And if you need to, you can add this flag to get all of the parameters and values, and diff those too:

hython $HFS/houdini/python2.7libs/opnode_sum.py -p > all_nodes_and_parms.txt



The version of hython being run is was really matters; you'll need to run the hython in each version of Houdini you wish to print out the list for.

Hope that helps!

16.5.496 DSO ERROR July 13, 2018, 4:10 a.m.

If you are getting DSO errors when launching, make sure you are using the correct (latest?) release of Redshift for your build of Houdini, that might be the problem. If you are uninstalling Redshift, but you are leaving the references to ProgramData/Redshift in houdini.env, that might cause a crash; try commenting out the PATH/HOUDINI_PATH lines in houdini.env and see if that lets you launch Houdini again.

Good luck!

Faster launch times? July 9, 2018, 8:29 a.m.

Hey Brian! Here are a few ideas to try:

- Load with a desktop that doesn't have a Scene Viewer (but keep a Geometry Spreadsheet so everything still cooks)
- Double-check that any disk-loading HDA's aren't doing something strange, that may have been necessary a long time ago (or made certain assumptions which are slow to check now)
- Try bypassing File SOPs, to see if certain network drives are making things load slower; if you know certain groups of File SOPs are all mounted in the same network drives, try disabling/enabling in groups
- Other idea for checking network drives, try saving the hip file + all dependencies to local workstation's /tmp dir, and opening it from there (may not be possible if loading lots of crazy stuff)
- See if there are nodes copying cache-cruft somehow by saving nodes to disk via opscript, then loading them back into a fresh Houdini session
- Try loading versions from the backup folder, see if any load faster and find out what's different if you do

Also, I know hip file load times are the question, but in Studios/environments which use a wrapper I try these:

- Try launching vanilla houdini without the wrapper, but still from the network-installed location (i.e. cd /location/on/network/hfs16.5.476;source houdini_setup;cd -; houdinifx -foreground)
- Check on network affects, by installing to the local machine's temp directory, and launching it vanilla style like above (i.e. cd /tmp/houdinitest/hfs16.5.476;source houdini_setup;cd /tmp; houdinifx -foreground)

Either of those are nice to narrow down crashes or other bugs that might be environment-related.

Hope that helps!