chrispriscott
chrispriscott
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Ambient Occlusion Maps for material exports ? Sept. 4, 2019, 5:53 a.m.
I'm also interested to here if there is any update on this (in particular for GLTF export). Seems the standard is to add AO into the red channel of the metalroughness map but doesn't like there is the option to do this with the principle shader and the current GLTF exporter.
Setting Environment Variable from Detail Attribute? Aug. 13, 2019, 6:59 a.m.
Thank you for the really quick fix (and workaround)!
Setting Environment Variable from Detail Attribute? Aug. 12, 2019, 10:58 a.m.
I've also come across the same issue with Houdini freezing in TOPS and narrowed it down to the attached scene and an interaction with the Python SOP.
In the attached scene I’ve got a simple wedge that changes the sub divs on a box at SOP Level and a Geometry Import TOP node that should read the results of this. However, everytime I run the TOPs network with the local scheduler Houdini hangs and I have to force kill it.
The Python SOP has only the default code but something here looks to be causing the issue as when I bypass the Python SOP the TOPS networks cooks successfully. It also works if I toggle off ‘Evaluate with Work item attributes’ but in our use case we need this on. Removing all the default code from the Python SOP also seems to fix the issue (but has obvious limitations).
I've logged the bug with Support (ID# 98564) but no workaround or ETA for a fix yet. @tpetric - Are you able to provide an update at all?
In the attached scene I’ve got a simple wedge that changes the sub divs on a box at SOP Level and a Geometry Import TOP node that should read the results of this. However, everytime I run the TOPs network with the local scheduler Houdini hangs and I have to force kill it.
The Python SOP has only the default code but something here looks to be causing the issue as when I bypass the Python SOP the TOPS networks cooks successfully. It also works if I toggle off ‘Evaluate with Work item attributes’ but in our use case we need this on. Removing all the default code from the Python SOP also seems to fix the issue (but has obvious limitations).
I've logged the bug with Support (ID# 98564) but no workaround or ETA for a fix yet. @tpetric - Are you able to provide an update at all?