John Kent
JohnKentFX
About Me
Senior VFX Technical Artist @ High Moon Studios
EXPERTISE
Technical Director
INDUSTRY
Gamedev
Connect
LOCATION
United States
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Trouble with using wedge TOP variables in COP network Feb. 1, 2021, 5 p.m.
Just really wanted to bump this to see if anyone can help here.
Seems like you can't really use top variables to drive COP networks efficiently.
It seems you can drive a switch node in COPS using these variables but that still means creating a bunch of unnecessary file import nodes by hand.
Seems like you can't really use top variables to drive COP networks efficiently.
It seems you can drive a switch node in COPS using these variables but that still means creating a bunch of unnecessary file import nodes by hand.
Trouble with using wedge TOP variables in COP network Jan. 25, 2021, 1:37 p.m.
Hi,
I am having trouble importing image sequences named with wedge TOP variables into COP networks.
After writing image files to disk using wedge TOP's I have a series of image sequences that I need to turn into mosaics. When using a File COP, the file parameter cannot seem to evaluate the wedge variables in the file name.
For example: $HIP/render/`$HIPNAME`.`$OS`_`@seed`.png
returns: folderstructure/filename.nodename_ _ _.png
The hscript expression above and referencing the TOP mantra ROP's parameter give the same result.
Do wedge variables not exist until the top network is executed?
If so, is there a different way to evaluate these variables that would allow me to test the COPs network without hardcoding the filename?
I am having trouble importing image sequences named with wedge TOP variables into COP networks.
After writing image files to disk using wedge TOP's I have a series of image sequences that I need to turn into mosaics. When using a File COP, the file parameter cannot seem to evaluate the wedge variables in the file name.
For example: $HIP/render/`$HIPNAME`.`$OS`_`@seed`.png
returns: folderstructure/filename.nodename_ _ _.png
The hscript expression above and referencing the TOP mantra ROP's parameter give the same result.
Do wedge variables not exist until the top network is executed?
If so, is there a different way to evaluate these variables that would allow me to test the COPs network without hardcoding the filename?