Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.38f1
2021.3.9f1
2022.1.14f1
2022.2.0b5
2023.1.0a6
2023.2.0a1
Issue ID
UUM-13017
Regression
No
AssetPostprocessor Mesh modification does not save after initial project import when applying changes to Mesh via OnPostprocessModel
Reproduction steps:
- Open the user’s attached project
- Open Assets/Scenes/SampleScene
- Notice how the characters in the scene appear properly skinned in T-pose
- Save the project and close the Editor
- Reopen the project
- Look at the characters
Expected result: Characters are still properly skinned
Actual result: The meshes are stretched
Reproducible with: 2020.3.38f1, 2021.3.9f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a6
Reproducible on: Windows 11
Notes:
- reimporting the FBX assets permanently fixes the issue
- opening the project with ‘-consistencyCheck’ command line arg also fixes the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.