Please describe the feature you have in mind and explain what the current shortcomings are?
Preferably any loaded container comes in via an HDA that has all the nice bells and whistles to load and update natively in Houdini, even without needing access to the AYON Load/Scene Inventory UIs, like the Load Asset LOP and Load Shot LOP we then expose all the parameters on the node to pick what you want to load.
Now it'd be nice - if it would be trivial from within the scene to access parameters of the entity that you loaded - so that other nodes could potentially access this data (or even other parms on the node itself).
It could allow e.g. the Primitive Path for a Load Asset LOP to include e.g. the folder[type] to automatically categorize it inside the scene using the type so that you directly load it into e.g. Character/ or Prop/ depending on the type of the asset you loaded?
How would you imagine the implementation of the feature?
I was thinking of just on load dump the full representation context data (project, folder, product, version, representation) as some data on a parm of the node. However, I have my doubts about doing that as since that may increase the file's size heavily based on the size of the data being stored (also this data would likely be duplicated for EACH node in the scene).
Are there any labels you wish to add?
[X] I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
Have other nodes query it from AYON via the API itself - but that may mean many more calls to that - or we just expose a little local houdini cached equivalent of API calls that just cache the results locally. So that subsequent calls for the same data wouldn't suffer that slowness.
(This may actually be the best solution? Because it'd also allow to query data from arbitrary products or folders that aren't necessarily loaded on the container itself.)
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Preferably any loaded container comes in via an HDA that has all the nice bells and whistles to load and update natively in Houdini, even without needing access to the AYON Load/Scene Inventory UIs, like the Load Asset LOP and Load Shot LOP we then expose all the parameters on the node to pick what you want to load.
Now it'd be nice - if it would be trivial from within the scene to access parameters of the entity that you loaded - so that other nodes could potentially access this data (or even other parms on the node itself).
It could allow e.g. the Primitive Path for a Load Asset LOP to include e.g. the
folder[type]to automatically categorize it inside the scene using the type so that you directly load it into e.g.Character/orProp/depending on the type of the asset you loaded?How would you imagine the implementation of the feature?
I was thinking of just on load dump the full representation context data (project, folder, product, version, representation) as some data on a parm of the node. However, I have my doubts about doing that as since that may increase the file's size heavily based on the size of the data being stored (also this data would likely be duplicated for EACH node in the scene).
Are there any labels you wish to add?
Describe alternatives you've considered:
Have other nodes query it from AYON via the API itself - but that may mean many more calls to that - or we just expose a little local houdini cached equivalent of API calls that just cache the results locally. So that subsequent calls for the same data wouldn't suffer that slowness.
(This may actually be the best solution? Because it'd also allow to query data from arbitrary products or folders that aren't necessarily loaded on the container itself.)
Additional context:
No response