Please describe the feature you have in mind and explain what the current shortcomings are?
It seems that HDA publishing only works from /obj or at least from object level. Publishing a network in /obj/geo1 seems to fail for one of our artists and reading the documentation he's not sure why. It doesn't mention anything about only being able to publish object level networks.
How would you imagine the implementation of the feature?
Allow any subnet to be published as HDA maybe, like e.g. from SOPs context? Or at least improve the documentation to explain from where you are able to generate an HDA and improve the error message too.
It also feels slightly weird maybe that it's failing during Create?
Are there any labels you wish to add?
[X] I have added the relevant labels to the enhancement request.
1.
We loosing the additional parameters added on HDA when publishing, Is it possible to keep the parameters same when publishing?
If some nodes inside HDA's will depend on obj level nodes, loading them in AVALON CONTAINER, might break, also the naming of HDA changing when loaded, can we lock the HDA name just like when it created( we got a trouble when we used light linking and published)
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
It seems that HDA publishing only works from
/obj
or at least from object level. Publishing a network in/obj/geo1
seems to fail for one of our artists and reading the documentation he's not sure why. It doesn't mention anything about only being able to publish object level networks.Here are the errors and documentation:
How would you imagine the implementation of the feature?
Allow any subnet to be published as HDA maybe, like e.g. from
SOPs
context? Or at least improve the documentation to explain from where you are able to generate an HDA and improve the error message too.It also feels slightly weird maybe that it's failing during Create?
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
[cuID:OP-5762]