Skip to content
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

Egg2Maya: Named UVs Unsupported #1

Open
BartGunshot opened this issue Feb 21, 2021 · 2 comments
Open

Egg2Maya: Named UVs Unsupported #1

BartGunshot opened this issue Feb 21, 2021 · 2 comments

Comments

@BartGunshot
Copy link

BartGunshot commented Feb 21, 2021

Converting an egg with named UV fields to maya produces a maya binary with broken UVs. For instance the top tag will convert with broken UVs but the bottom one will convert correctly.

<UV> UVMap { 0.802775084972382 0.206263214349747 }

<UV> { 0.802775084972382 0.206263214349747  }

Tested with maya 2018 and 2017.

@rdb
Copy link
Member

rdb commented Jul 2, 2021

Could you elaborate what you mean by "broken UVs"?

@BartGunshot
Copy link
Author

BartGunshot commented Jul 12, 2021

On closer inspection there seems to be two separate issues here.

  1. Eggs with multiple UV fields will only import their first UV, not subsequent UVs. Only the first UV map will show up in Maya's UV sets editor as "map1"
    image

  2. Eggs with named UV fields will import and have a UV set in Maya (named "map1" regardless of the name in the egg), however the UV layouts will have all verts situated at 0,0.

Example: 1 unnamed UV/1 named UV on the left and 2 named UVs on the right.
image
What this should look like: (two textures overlapping with a multiply)
image

Video showing the UV at the origin:
https://i.gyazo.com/216cdcb3225a4107e1286b44428c2d3f.mp4

@rdb rdb transferred this issue from panda3d/panda3d Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants