You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently there seems to be no import translator functionality for a USD Point Instancer.
Additionally, even though you can "Duplicate as USD data" from a maya instancer you cannot convert back with "Edit as Maya data"
Describe the solution you'd like
Allow instancer to be converted with its prototypes to maya data, preferably also supporting animated point data.
Describe alternatives you've considered
Potentially a custom import chaser for mayaUSDImport or register a custom USD translator which would also allow the Edit as maya data functionality.
However, from a Maya perspective I'm still not sure how trivial that'd be since I don't know what nodetypes/datastructures are available to maya to have time samples point data with e.g. attributes, etc. that can be saved/embedded with the maya scene file.
Also, I believe custom USD import translators are C++ only?
Additional context
I assume the lack of this is mostly due to Maya's native tools to be lacking in regards to the Instancer (and its editability) of just point data that can also be animated since I believe by default there's no data structure in which one can interactively add/remove points with transforms easily other than particles which aren't meant for manual editing. MASH does provide some tools, but those as far as I know would still disallow trivial storage for animated data local to the scene.
The text was updated successfully, but these errors were encountered:
Points ideally would be translated as a nParticles with attributes per-particle and an alternative option for maya locators with attributes.
I'm not sure I'd totally agree since as far as I know there's no way for nParticles to storage point data per frame within the scene - as such the import would not be able to import animated particle data. If you know of a Maya node that is capable of storing that without requiring e.g. XML cache files on disk I'd be happy to learn about it and prototype a Python Import chaser.
Is your feature request related to a problem? Please describe.
Currently there seems to be no import translator functionality for a USD Point Instancer.
Additionally, even though you can "Duplicate as USD data" from a maya instancer you cannot convert back with "Edit as Maya data"
Describe the solution you'd like
Allow instancer to be converted with its prototypes to maya data, preferably also supporting animated point data.
Describe alternatives you've considered
Potentially a custom import chaser for
mayaUSDImport
or register a custom USD translator which would also allow the Edit as maya data functionality.However, from a Maya perspective I'm still not sure how trivial that'd be since I don't know what nodetypes/datastructures are available to maya to have time samples point data with e.g. attributes, etc. that can be saved/embedded with the maya scene file.
Also, I believe custom USD import translators are C++ only?
Additional context
I assume the lack of this is mostly due to Maya's native tools to be lacking in regards to the Instancer (and its editability) of just point data that can also be animated since I believe by default there's no data structure in which one can interactively add/remove points with transforms easily other than particles which aren't meant for manual editing. MASH does provide some tools, but those as far as I know would still disallow trivial storage for animated data local to the scene.
The text was updated successfully, but these errors were encountered: