Search Issue Tracker
Fixed in 2.2.1-preview.1
Votes
0
Found in [Package]
2.2.0 Preview 4
Issue ID
1174167
Regression
Yes
2D Animation package performance has degraded in newer (2.2.0 P4 and later) versions when entering Playmode
How it was tested:
1. Created a new project
2. Added assets from ("REPRO.zip")
3. Added 4 copies of ("agate.psb") asset to the Scene
4. Open the Game window and turn on Stats
5. Open Profiler window (Window->Analysis->Profiler)
6. Enter Playmode
7. Recorded data
Expected result: 2D Animation package performance is the same or better than the previous version
Actual result: 2D Animation package performance is worse than the previous version
Results collected when comparing to the best performing Unity version (2D Animation package version):
- 2020.1.0a4 - 0a5 (3.0.5): 15% slower
- 2019.3.0b4 (3.0.4 - 3.0.5): 69% slower
- 2019.3.0a12 (2.2.0 P4): 48% slower
- 2019.2.7f2 (2.2.0 P4): 48% slower
- 2019.1.14f1 (2.1.0 P7): Best performer, this version was used as a base line to measure performance
- 2018.4.10f1 (2.0.0 P3): 43% slower
Comments (1)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
skm451743
Oct 27, 2025 22:43
It might be related to changes in how the 2D Animation package handles rig initialization in newer versions. You could try profiling the scene to see which processes take longer in Playmode. Also, reverting to an earlier stable version (like 2.1.x) or disabling unnecessary editor scripts during Playmode might help narrow down the issue.