Is there an existing issue for this?
Description
Current Behavior
When using a custom publish template for usd product in Houdini, it breaks the contribution workflow.
I checked the published files and found they were pointing to the other layer as if they were published using the default template.
examples:
here's a published assembly layer.
#usda 1.0
(
defaultPrim = "hou_component_builder"
metersPerUnit = 1
subLayers = [
@\\storage\work\ayon\RnD\features\hou_component_builder\publish\usd\usdSimpleCube\v010\rnd_hou_component_builder_usdSimpleCube_v010.usd:SDF_FORMAT_ARGS:layer_id=usdSimpleCube@
]
upAxis = "Y"
)
According to my publish template, it should be
#usda 1.0
(
defaultPrim = "hou_component_builder"
metersPerUnit = 1
subLayers = [
@\\storage\work\ayon\RnD\features\hou_component_builder\publish\usd\usdSimpleCube\v010\componentoutput1.usd:SDF_FORMAT_ARGS:layer_id=usdSimpleCube@
]
upAxis = "Y"
)
Expected Behavior
Contribution workflow should get the correct file names.
Steps To Reproduce:
- use a different publish template, steps.
- publish with contribution enabled.
Additional context:
Version
Version of the server, ayon-core and the addon that's affected
What platform were you running when you found the bug?
Windows
You can also provide any additional information relevant to the issue.
Relevant log output:
Is there an existing issue for this?
Description
Current Behavior
When using a custom publish template for
usdproduct in Houdini, it breaks the contribution workflow.I checked the published files and found they were pointing to the other layer as if they were published using the default template.
examples:
here's a published assembly layer.
According to my publish template, it should be
Expected Behavior
Contribution workflow should get the correct file names.
Steps To Reproduce:
Additional context:
Version
Version of the server, ayon-core and the addon that's affected
What platform were you running when you found the bug?
Windows
You can also provide any additional information relevant to the issue.
Relevant log output: