Please describe the feature you have in mind and explain what the current shortcomings are?
SideFX Houdini is completely capable of authoring a USD asset from one Houdini file, including authoring variants, model with proxies, materials and is capable of collecting all the resulting USD files into one folder (including localizing the asset resources like textures).
There is a use case where one may want to rely solely on that, build on that Houdini-native functionality whilst still allowing to track the assets through AYON.
To do so we must:
Be able to publish the output of a component builder
Be able to also 'localize' the assets relative to the published component builder product (likely just a USD product)
Since the builder relies on Houdini USD ROP output processors if we were to detect the paths manually we'd need to take those processors into account instead of acting on the local scene file and its paths. Hence, we should use the generated USD ouput file from the ROP instead of the local scene one; that way we'd support whatever Houdini would be doing.
(Optionally) be able to publish it as one product only - instead of a product per USD layer so that the exact Component Builder output hierarchy could be maintained on publish. We would then ONLY track the core "asset" usd output file as a representation - the remainder of files would be separate untracked 'files' for the time being (however they are still registered as "files" on the version for site sync to work, etc.)
How would you imagine the implementation of the feature?
No response
Describe alternatives you've considered:
No response
Additional context:
link to discussion on Discord(might be a private channel)
This issue was automatically created from Clickup ticket AY-7047
Please describe the feature you have in mind and explain what the current shortcomings are?
SideFX Houdini is completely capable of authoring a USD asset from one Houdini file, including authoring variants, model with proxies, materials and is capable of collecting all the resulting USD files into one folder (including localizing the asset resources like textures).
There is a use case where one may want to rely solely on that, build on that Houdini-native functionality whilst still allowing to track the assets through AYON.
To do so we must: Be able to publish the output of a component builder Be able to also 'localize' the assets relative to the published component builder product (likely just a USD product) Since the builder relies on Houdini USD ROP output processors if we were to detect the paths manually we'd need to take those processors into account instead of acting on the local scene file and its paths. Hence, we should use the generated USD ouput file from the ROP instead of the local scene one; that way we'd support whatever Houdini would be doing. (Optionally) be able to publish it as one product only - instead of a product per USD layer so that the exact Component Builder output hierarchy could be maintained on publish. We would then ONLY track the core "asset" usd output file as a representation - the remainder of files would be separate untracked 'files' for the time being (however they are still registered as "files" on the version for site sync to work, etc.)
How would you imagine the implementation of the feature?
No response
Describe alternatives you've considered:
No response
Additional context:
link to discussion on Discord (might be a private channel)
This issue was automatically created from Clickup ticket AY-7047