Pierre L
pi-R
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Control over how Xforms are written in USD Dec. 7, 2020, 4:39 a.m.
Thank you for your answer!
As you suggested, I would rather have a post-process that converts all the Xforms generated by my LOP network right before it gets written down as USD layers.
Is there any mechanism that Houdini provides for calling custom code over a stage that is about to get ‘rendered’?
Ideally, I would look for something along the lines of the output processors that are used to process asset paths prior saving.
As you suggested, I would rather have a post-process that converts all the Xforms generated by my LOP network right before it gets written down as USD layers.
Is there any mechanism that Houdini provides for calling custom code over a stage that is about to get ‘rendered’?
Ideally, I would look for something along the lines of the output processors that are used to process asset paths prior saving.
Control over how Xforms are written in USD Dec. 3, 2020, 5:40 a.m.
Hi everyone!
I would like to control the way the operation stacks of my Xforms are written in my USD layers (the ‘xformOpOrder’ property).
More precisely, I would like Xforms to follow the assumptions surrounding the UsdGeomXformCommonAPI schema [graphics.pixar.com] and be correctly interpreted by it.
However, some LOP nodes directly work with matrix operations (e.g. the ‘Duplicate’ LOP node), thus producing transforms unrecognized by UsdGeomXformCommonAPI.
Is there any way of controling how the ops of the Xforms I create are described in the USD layers?
Could using a ‘Python script’ LOP node be a solution?
Thanks in advance for your help.
Pierre.
I would like to control the way the operation stacks of my Xforms are written in my USD layers (the ‘xformOpOrder’ property).
More precisely, I would like Xforms to follow the assumptions surrounding the UsdGeomXformCommonAPI schema [graphics.pixar.com] and be correctly interpreted by it.
However, some LOP nodes directly work with matrix operations (e.g. the ‘Duplicate’ LOP node), thus producing transforms unrecognized by UsdGeomXformCommonAPI.
Is there any way of controling how the ops of the Xforms I create are described in the USD layers?
Could using a ‘Python script’ LOP node be a solution?
Thanks in advance for your help.
Pierre.
Issue accessing context options inside a 'For each' block Sept. 10, 2020, 5:23 a.m.
Hi everyone !
I am having a hard time trying to use the ‘For each’ LOP.
In the attached example scene, I am trying to perform a nested iteration : over all the model variants of all the components present on my stage.
On both of the ‘For each end’ LOPs, I rename the iteration variables to prevent any conflict. The loop does occur, but I fail to correctly edit the current iteration's context options via a ‘Python script’ LOP. As the documentation suggests, I am trying to extract the current primitive's name from its full path.
To debug, I write some of the current context options as the metadata of a newly-created primitive from inside the loop.
Please help!
Cheers,
Pierre.
PS: I am running a Houdini Core Version 18.0.532 license.
I am having a hard time trying to use the ‘For each’ LOP.
In the attached example scene, I am trying to perform a nested iteration : over all the model variants of all the components present on my stage.
On both of the ‘For each end’ LOPs, I rename the iteration variables to prevent any conflict. The loop does occur, but I fail to correctly edit the current iteration's context options via a ‘Python script’ LOP. As the documentation suggests, I am trying to extract the current primitive's name from its full path.
To debug, I write some of the current context options as the metadata of a newly-created primitive from inside the loop.
Please help!
Cheers,
Pierre.
PS: I am running a Houdini Core Version 18.0.532 license.