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

Unity Save Crash After "Freeze T-Pose" #2412

Open
Iplay4u opened this issue Aug 24, 2024 · 3 comments
Open

Unity Save Crash After "Freeze T-Pose" #2412

Iplay4u opened this issue Aug 24, 2024 · 3 comments
Labels
bug Something isn't working help wanted stale
Milestone

Comments

@Iplay4u
Copy link

Iplay4u commented Aug 24, 2024

Environments (please complete the following information):

  • UniVRM version: 0.123.0_f812
  • Unity version: Unity-2022.3.22f1
  • OS: Windows 11

Describe the bug

I am using an avatar that is 146k Polygons, 1x Skinned Mesh Renderer, 15 materials and 165 bones
When I use the "Freeze T-Pose" feature, it does what it should normally but when I save the scene, it crashes Unity every time. It is saved before the "Freeze T-Pose" but doesn't save afterwards since it crashes.

While freezing: (took 07:15 to execute the code)
HF4 0319 23hr 24 08 24

Nothing in the console before saving:
EJK 0320 23hr 24 08 24

Seconds before the crash: (took 05:45 to execute the code)
ZxE 0321 23hr 24 08 24

If anyone wants to reproduce the issue and are having problems doing it, it may be the avatar thats the issue. DM me on Discord and ask for it and I will provide: phederal_phoenix

@Iplay4u Iplay4u added the bug Something isn't working label Aug 24, 2024
@Iplay4u Iplay4u changed the title Sample Scene - Unity Crashes After "Freeze T-Pose" (temporary fix found until devs fix it) Unity Save Crash After "Freeze T-Pose" Aug 24, 2024
@Iplay4u
Copy link
Author

Iplay4u commented Aug 24, 2024

Edited cause what I thought fixes it indeed doesn't fix it

@ousttrue ousttrue added this to the v0.999 milestone Sep 5, 2024
@github-actions github-actions bot added the stale label Sep 15, 2024
Copy link

This issue has been labeled as "stale" due to no response by the reporter within 1 month (and 7 days after last commented by someone). And it will be closed automatically 14 days later if not responded.

@Anna-Spanner
Copy link

Hi, I haven't gotten round to checking it again yet (I am Iplay4u on an alt account)

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

No branches or pull requests

3 participants