Clayton Krause


About Me

Not Specified
Not Specified


Recent Forum Posts

Instant Meshes Bridge Sop Feb. 27, 2019, 7:04 p.m.

Houdini by default should be looking for the instantMeshes EXE in your user preferences folder (“$HOUDINI_USER_PREF_DIR” = environment variable for it). This is usually located in your documents by default - “C:\Users\%USER%\Documents\houdini17.0”

Drop the EXE in there and it should pick up. To see where it is pointing to or change the location the SOP points to, check out the “settings” tab of the SOP.

Python "toolutils.testTool" issue Jan. 4, 2019, 1:41 p.m.

Alright, letting this sit with the community for a while, I'm going to open up a RFE/bug report on this.


Instead of using execfile() to fire off a .py I use as a dev/sandbox I am not actually importing it and locals and globals seem to be handled correctly-

here is what I'm not using in my shelf tool to comply better with toolUtils. Bit long winded, but works all the same. No bug submission as long as there is a work-around that probably is less hacky anyways.

import os
import sys

path = os.path.join(hou.getenv('HOUDINI_CLOUD_PREF_DIR'), 'python2/utils')

if not path in sys.path:
    sys.path.insert(0, path)

import hExec

Python "toolutils.testTool" issue Dec. 24, 2018, 2:19 p.m.

Why not add ‘$HOUDINI_CLOUD_PREF_DIR’ to your houdini path? Then you wouldn't need to use execfile, and you could store shelf tools and otls there too.

As to your problem, I don't know why testTool() would produce different results, but I suspect it runs slightly different context than clicking a tool.

‘$HOUDINI_CLOUD_PREF_DIR' is appended into the Houdini Path. I only use execfile for my Python dev .PY file. Like a sandbox.

If testTool's purpose is to execute a shelf tool via python, then the results should not deviate from hte user manually clicking on the shelf button. I figure this is a bug, but wanted to check the forums before submitting a report.

Thank you for the reply.