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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.