Search Issue Tracker
Fixed
Votes
0
Found in [Package]
Issue ID
1352527
Regression
Yes
Selecting a child object of a Tilemap is very slow
Repro:
- download this project
- open cats_test_scene
- in the scene Hierachy, select the Background object
- in the child of that object called Walkable (a tilemap), there are 2 bunnies
- try to switch between the Bunny and the Bunny baby
- for me, it takes a few seconds for the selection to work and the secene to update
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
- [Android][Vulkan] Crash on /system/lib/libandroid.so (ANativeWindow_setBuffersGeometry+4) when the Vulkan Graphics API is used
- Event handlers are preventing operations when trying to copy or paste HTML text in the WebGL Player
- [macOS] Crash on __pthread_kill when Exporting a Package while another export is in progress
- Crash on TransformAccessDestroyCallback when removing a URP Decal Projector component from a parent GameObject that had a URP Decal Projector child GameObject
- [ShaderGraph][URP Sample] Shader error in 'Shader Graphs/Screen_Graph': 'SHADERGRAPH_BAKED_GI'
Resolution Note:
Performance regression fixed in: 2022.1.0a12.1571
Workaround for versions without the fix:
The problem performance problem stems from using a Prefab instance with a Tilemap that contains a lot of modifications.
While Prefabs with Tilemaps is not in itself a problem, a Tilemap contains a lot of data and every single changed tile is individually saved in the scene as modifications to the prefab. In the example, there is almost 90.000 modifications to the Prefab instance in the scene.
To work around the problem you can do:
- Often apply the modifications to the Prefab
- Unpack the prefab
- Only do small adjustments to the Prefab Instance