
Taylor Petrick
tpetrick
About Me
Connect
LOCATION
Canada
WEBSITE
Houdini Skills
Availability
Not Specified
My Badges
SideFX Staff
Since May 2014
Recent Forum Posts
How to inspect existing global attributes? Feb. 12, 2025, 5:21 p.m.
If you want the global attribute to be deleted when the work item that created it is deleted, then you should create the attribute using the Graph (Bound) type instead of the Graph (Global) type as described here: https://www.sidefx.com/docs/houdini/nodes/top/attributecreate.html#stringscope [www.sidefx.com]
Truly global attrbutes are saved as part of the graph if the Save Graph Attributes to .hip toggle is enabled on the network manager node. The purpose of unbound global attributes is provide a persistent place that work items can score key/value data, for example if you wanted to output file versions between multiple consecutive cooks of the same TOP network.
Truly global attrbutes are saved as part of the graph if the Save Graph Attributes to .hip toggle is enabled on the network manager node. The purpose of unbound global attributes is provide a persistent place that work items can score key/value data, for example if you wanted to output file versions between multiple consecutive cooks of the same TOP network.
How to inspect existing global attributes? Feb. 12, 2025, 4:58 p.m.
Global attributes are supposed to appear in the MMB window on the TOP Network manager itself, but it looks like that was broken with the introduction of the new MMB info window across all contexts in Houdini. Please log a bug for that.
No output path parameters found on target ROP node Feb. 10, 2025, 10:20 a.m.
The ROP Fetch TOP looks for an output file parameter on the target ROP in order to determine where the ROP writes its files. That's necessary for e.g. caching support, so that TOPs can know what outputs already exist before cooking any of the work items.
When the ROP Fetch isn't able to determine which parameter on the ROP defines the output path(s), it issues a warning. It is just a warning though -- not an error -- and TOPs will still cook the ROP. It just can't providing caching functionality or output file reporting since it doesn't know what file paths are going to be produced.
If this used to work before, and doesn't in newer versions, it sounds like the Vray ROP has changed it's parameter interface and renamed the parameter it uses to define output paths. By default, TOPs checks the ROP node for any of the following file parameters: vm_picture, sopoutput, dopoutput, lopoutput, picture, copoutput, filename, usdfile, file, output, outputfilepath, outputimage, outfile#.
You can explicitly tell TOPs which parameter on the ROP node defines the output file path by setting the Output Parm Name on the ROP Fetch TOP, as described in the docs here: https://www.sidefx.com/docs/houdini/nodes/top/ropfetch.html#customoutput [www.sidefx.com]
I don't have Vray installed, so I can't check myself. But double check the name of the output parm on the Vray ROP, and set that as the Output Parm Name on the TOP node.
When the ROP Fetch isn't able to determine which parameter on the ROP defines the output path(s), it issues a warning. It is just a warning though -- not an error -- and TOPs will still cook the ROP. It just can't providing caching functionality or output file reporting since it doesn't know what file paths are going to be produced.
If this used to work before, and doesn't in newer versions, it sounds like the Vray ROP has changed it's parameter interface and renamed the parameter it uses to define output paths. By default, TOPs checks the ROP node for any of the following file parameters: vm_picture, sopoutput, dopoutput, lopoutput, picture, copoutput, filename, usdfile, file, output, outputfilepath, outputimage, outfile#.
You can explicitly tell TOPs which parameter on the ROP node defines the output file path by setting the Output Parm Name on the ROP Fetch TOP, as described in the docs here: https://www.sidefx.com/docs/houdini/nodes/top/ropfetch.html#customoutput [www.sidefx.com]
I don't have Vray installed, so I can't check myself. But double check the name of the output parm on the Vray ROP, and set that as the Output Parm Name on the TOP node.