captainhammy / houdini-toolbox Goto Github PK

The strings for editable nodes and message nodes could contain wildcards. It should use hou.Node.glob() on each path instead.

Call mantra.setproperty("object:displace", []) in filterInstance and filterMaterial

When matching against operator type names it should probably match against the actual operator name component rather than the full on name.

Currently node type names match against the full name:
foo::bar::4

We should use hou.NodeType.nameComponents()[2] to match against just
bar

Need to add wildcard support for matching definitions

Hey there,
I went to try this out but was greeted by this over and over when starting Houdini:

Error running event handler:
Traceback (most recent call last):
  File "E:/GitHub/Houdini-Toolbox/houdini/scripts/OnInstall.py", line 8, in <module>
    from ht.events import NodeEvents, run_event
ImportError: No module named ht.events

Error running event handler:
Traceback (most recent call last):
  File "E:/GitHub/Houdini-Toolbox/houdini/scripts/OnInstall.py", line 8, in <module>
    from ht.events import NodeEvents, run_event
ImportError: No module named ht.events

Error running event handler:
Traceback (most recent call last):
  File "E:/GitHub/Houdini-Toolbox/houdini/scripts/OnInstall.py", line 8, in <module>
    from ht.events import NodeEvents, run_event
ImportError: No module named ht.events

I also received this as well:

Traceback (most recent call last):
  File "Mouse Event Handler", line 1, in <module>
  File "C:/PROGRA~1/SideFX/HOUDIN~1.348/houdini/python2.7libs\nodegraph.py", line 25, in <module>
    import nodegraphhooks as hooks
  File "E:/GitHub/Houdini-Toolbox/houdini/python2.7libs\nodegraphhooks.py", line 8, in <module>
    from ht.ui import paste
ImportError: No module named ht.ui

Thanks,
-MH

Hello, I am trying to install the Houdini Toolbox via the packages method, but am a scripting novice.

I have managed to setup the packages method for things like Redshift before, but I have extremely limited knowledge of scripting.

I wonder if you have an example .json package file I could use to help me install the toolbox?

Thank you!

• Glenn

Hi Captain,

First of all, a huge thanks for making this repository public, It helped me a lot to do my own setup.

I'm writing a C++ library based on HDK to use in other DCCs (I have a working integration in Nuke, Gaffer, Blender powered by HDK, LibGL(using Eigen) and PyBind11 for now)

Some parts of the HDK are still obscure and being able to live compile inside Houdini and seeing the result in the viewport would be a huge productivity boost.

Here comes my question, do you have a working sample of your C++ Wrangle? From all the integrations I've seen it seems to be the one who best fit my use case.

I tried to use it but did not really understand how it's written (first time I see this PythonCook magic) and so how to debug it.

Thanks

When copying attributes to the centroids it should also copy the local variables so they don't need to be recreated.

Remove use of old SIGNAL() on like 889

When the point/primitive internal offsets don't match the entity numbers you can get bad behavior when calling merge[Points/Prims]

On Windows when attempting to view the help for the AOV manager things it will throw an exception about badly formed paths.

When we construct a help path on line 1856 in python/ht/ui/aovs/widgets.py it should NOT be trying to do any os level path magic because we need a valid url path, not a valid file path. Since Windows uses ''s in paths and the code uses os.path to join the paths this causes breakage due to escape characters and whatnot. We should form the path manually as expected for a url

The copy/paste dialogs don't automatically refresh their views when they pop up. This isn't a problem for one person working locally in a single session but is annoying when you have multiple users or sessions.

Since H12 changed the way string attributes work you can no longer add variable mappings but setting values to the varmap so some sort of HDK magic is necessary.

The base implementation of PyFilterOperation.processParsedArgs() is static which it should not be. This causes an exception if you attempt to create an operation that does not need to parse args

When getting the destination point/prim the code is incorrectly trying to get an offset from the source detail. This can cause bad things to happen:

destOff = src_gdp->pointOffset(dest_pt);

should be

destOff = dest_gdp->pointOffset(dest_pt);