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

Exporting in newer versions of UniVRM cause issues with blendshapes and scaling #2236

Closed
Harrison-B opened this issue Feb 2, 2024 · 4 comments · Fixed by #2240
Closed

Exporting in newer versions of UniVRM cause issues with blendshapes and scaling #2236

Harrison-B opened this issue Feb 2, 2024 · 4 comments · Fixed by #2240
Labels
bug Something isn't working mesh

Comments

@Harrison-B
Copy link

Environments (please complete the following information):

  • UniVRM version: 0.118.0
  • Unity version: Unity-2022.3.6
  • OS: Windows 10

Describe the bug

Exporting the avatar with a newer version of UniVRM causes the Mesh Bounds to increase in size and the blendshapes to be out of whack. I suspect this is due to the scaling on the avatar being weird.

For some reason on older versions of UniVRM it exports just fine. Version 0.107 exports correctly. Not sure exactly which version causes the issue though.

Adjusting the blendshapes after exporting then re-importing the VRM:
image

Scaling and bounds pre-export
image

Scaling and bounds after export and re-import with UniVRM 0.118
image

@ousttrue
Copy link
Contributor

ousttrue commented Feb 5, 2024

I confirmed the reproduction.
A SkinedMesh without bone weights might be the condition to reproduce this.

@ousttrue
Copy link
Contributor

ousttrue commented Feb 5, 2024

  • root (scaling 100)
    • hips
      • spine
        • head(SkinnedMesh without bone weight but with blendshape)

@ousttrue
Copy link
Contributor

ousttrue commented Feb 8, 2024

👆 Latent bug

I reconfirmed it.

👇 new bug

  • root (scaling 100)
    • mesh(SkinnedMesh with bone weight and blendshape)~~

@ousttrue
Copy link
Contributor

ousttrue commented Feb 8, 2024

It seems to be a regression bug caused by the processing order during normalization from v0.116.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working mesh
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants