Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2021.3.28f1
2022.3.4f1
2023.1.3f1
2023.2.0a23
Issue ID
UUM-42696
Regression
No
AnimationClip files are too large when they are created
How to reproduce:
1. Open the attached “AnimationClipBug.zip“ project
2. Open the Memory Profiler (Window>Analysis>Memory Profiler)
3. Select the Screenshot on the left of the Memory Profiler window
4. Select the “Object and Allocations“ tab
5. Go to the Object list view and sort descending by size
6. Find an AnimationClip named “IdleBase”
Expected result: Size of the AnimationClip is around 0 bytes
Actual result: Size of the AnimationClip is 4.7 kilobytes
Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23
Reproduced on: macOS 13.4.1 (Intel, M1)
Note: If creating a new AnimationClip, the size of it may change depending on the minimum block size of your computer's disk format
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
- "WebGL Template" icons disappear when building the project with the Project Settings opened
- Variant Family window UI issues when Prefab title is long
- Player crash when switching focus in Exclusive Fullscreen mode with DirectX 12
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
Resolution Note:
The animation clip also contains more data than just the curves, there is a basic cost of 3.7 kb just for the animation clip class and all the aggregated data inside the animation clip. So an empty clip with no curve still cost 3.7 kb.
Resolution Note (2023.2.X):
The animation clip also contains more data than just the curves, there is a basic cost of 3.7 kb just for the animation clip class and all the aggregated data inside the animation clip. So an empty clip with no curve still cost 3.7 kb.