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
We recently have tested the USD import/export and found some issues:
Import Does not import custom attributes (non-primvars)
Example:
See the example USD file with custom attributes and primvars below
Custom attributes, "my_int", "my_bool" etc. are missing after importing
Question:
Is it configurable for the import command?
If not, is it the only way by implementing custom adaptor / chaser?
Expectation:
Custom attributes can be imported as Maya attributes in Maya
Import Does not import color4f/float4f/vector4f and their array form, the plugin throws error saying "not supported"
Example:
See the notes in the example USD file with custom attributes and primvars below
Expectation:
Support importing color4f/float4f/vector4f and their array form
Import Does not have option to import displayColor and displayOpacity as combined RGBA color set (comparing with AL_USDMaya), these two special primvars are always created as separated color sets, separately
Example:
See the example USD file with constant displayColor and displayOpacity below
Expectation:
Provide configurable option to combine displayColor and displayOpacity as one RGBA color set
Import float[]/float3[]/color3f[] primvars are handled differently
Problems:
By default, float[] becomes alpha (A); float3[] and color3f[] become RGB channel
These primvars can be configured to not become 'color set' via import options 'excludePrimvar', but this is not ideal:
Those primvars would be ignored completely (missing after importing) if they are marked with 'excludePrimvar' option
User (or the pipeline tool) will need to know the list of exclusive names beforehand, otherwise the tool will need to traverse the hierarchy to collect the list of primvar names. this might not be practical: imaging if the tool needs to import a heavy scene with different kinds of meshes and those meshes have different custom primvars for different purposes.
Using 'excludePrimvarNamespace' might work for excluding a set of primvars but unfortunately it does not work for workflow that does not have namespaced primvars
Example:
See the example USD file with custom attributes and primvars below
Expectation:
Have option to import float[]/float3[]/color3f[] primvars as Maya custom attributes, just like other primvar types
Export The custom primvars are imported as Maya custom attributes (on the shape), but the exporter does not seem to export them back to USD except the ones that previously imported as 'color set'
Example:
See the example USD file with custom attributes and primvars below
@csyshing thank you for reporting this. since there are multiple cases here, and a lot of it are unsupported workflows, I will change the label on this to an enhancement.
I will bring this to the team for a larger discussion, but from an initial assessment/testing, I can answer some of your questions :)
import chasers would indeed be the way to handle this kind of data here, not entirely sure why the array attributes are not being imported, will need to investigate a bit deeper.
for custom attributes to be exported, there are a couple of ways of handling those, although they would require some work on defining the desired attrs. before exporting.
thank you for all the detailed usage and cases. I will see what i can find on more info.
Describe the bug
Hi,
We recently have tested the USD import/export and found some issues:
"my_int"
,"my_bool"
etc. are missing after importingcolor4f
/float4f
/vector4f
and their array form, the plugin throws error saying "not supported"color4f
/float4f
/vector4f
and their array formdisplayColor
anddisplayOpacity
as combined RGBA color set (comparing with AL_USDMaya), these two special primvars are always created as separated color sets, separatelyExample:
Expectation:
Problems:
Example:
Expectation:
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
See the individual expectations on each item above.
Attachments
Example USD file with custom attributes and primvars:
Example USD file with constant displayColor and displayOpacity
Specs (if applicable):
The text was updated successfully, but these errors were encountered: