Tomas Slancik
tamte
About Me
INDUSTRY
Advertising / Motion Graphics
Connect
LOCATION
New York,
United States
WEBSITE
Houdini Skills
Availability
I am currently employed at Method Studios
Recent Forum Posts
Multiparm Button script question Nov. 16, 2025, 5:23 p.m.
Multiparm button instance question Nov. 16, 2025, 5:22 p.m.
like any parm callback script, the info is in the kwargs dictionary
specifically
for example to print button parm name and index you can use this as callback script:
or just:
to see what info you can work with
specifically
kwargs["script_multiparm_index"]
for example to print button parm name and index you can use this as callback script:
print( f"button name: { kwargs['parm'].name() }\nbutton index: { kwargs['script_multiparm_index'] }" )
or just:
print( kwargs )
Polysplit Node Nonsense Nov. 14, 2025, 10:52 a.m.
traileversePolySplit is very sensitive to the input geo as it needs to do split on exact prim number, exact edge, etc.
tons of errors and all pointing to polysplit nodes
so it's likely to error out if for example is expecting to cut 10e5:0.5, but suddenly prim 10 doesn't have 6 edges anymore
so all I'm saying is that because Poly Split errors out it doesnt necessarily mean that polysplit is the issue
however if you stash the geo on node before in working build and then plug it to next PolySplit in non working and it still errors out, then you can assume it's the PolySplit, since on the same geo it should work
when I have time I'll check your file on 684 to see where the geo changes between builds