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, geo meshes are always exported. It would be nice to have an option to exclude them from export.
Two potential use cases for this are:
exporting the materials and bindings, without the meshes. This would be useful when exporting the material portion of a component asset to be layered over the geometry portion.
exporting the animated point cache without the meshes. This would likewise be useful to manage the size of animation caches.
Describe the solution you'd like
Add the option to exclude geometry/ meshes from the USD export. This should however still include material bindings and animated point data.
Describe alternatives you've considered
Currently, we code this with the API. This involves exporting everything and then stripping out the mesh data. Having an option to not write mesh data in the first place would of course be more efficient.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, geo meshes are always exported. It would be nice to have an option to exclude them from export.
Two potential use cases for this are:
Describe the solution you'd like
Add the option to exclude geometry/ meshes from the USD export. This should however still include material bindings and animated point data.
Describe alternatives you've considered
Currently, we code this with the API. This involves exporting everything and then stripping out the mesh data. Having an option to not write mesh data in the first place would of course be more efficient.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: