-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UV's missing when exporting to USD #1202
Comments
Obvious question perhaps but did you set the "exportUVs" tag (if you're doing it in python/mel) or make sure the box is checked next to "UV Sets" in the export dialog? In general, we get UVs when we export to USD. There are some gotchas in some situations (mostly around multiple UV sets) that you may find yourself needing to be aware of but otherwise, your UVs should be there. |
Sorry, i didn't word the issue correctly. Below is a link to a video showing the problem |
I wonder if it's related to #876. Did you try using MAYAUSD_EXPORT_MAP1_AS_PRIMARY_UV_SET and MAYAUSD_IMPORT_PRIMARY_UV_SET_AS_MAP1 to bring back the renaming behavior we had before? |
Hi. As kxl said. By changing the settings as above I can now get UV's in other apps. Best Mark |
@swamiforlife did you have a chance to try it? If env variables solved your problem, I suggest we close this issue. |
@kxl-adsk yes it is working now with the env variables. So, you can close this issue. |
It's too early to make any plans for removing it. Other USD consumers (importers, renderers) will have to follow and stop using hardcoded "st" name for UV. |
When i export some geometry to USD the UV's are missing.
Is this feature yet to be implemented? or is it a bug?
The text was updated successfully, but these errors were encountered: