Search Issue Tracker
Fixed
Votes
0
Found in
2019.4
2020.3
2020.3.6f1
2021.2
2022.1
2022.2
Issue ID
1381129
Regression
No
Editor performance degrades when adding more Sprites to the Tilemap and zooming out
How to reproduce:
1. Open the user attached "BugExample.zip" project
2. Enter the "SampleScene" Scene found in the Assets/Scenes folder
3. In the Scene zoom-in and zoom-out
Expected result: Stable editor performance
Actual result: Unstable editor performance
Reproducible with: 2019.4.36f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a3
Note:
- Reproducible on a new project
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The use of sprite mask is not scalable to use with tilemap. Each SpriteMask per tile is treated as a Renderer and incurs overhead for each instance. This performance issue is not a trivial fix to optimize, hence By Design for now.