Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a17
Issue ID
1338333
Regression
No
[2D][Tilemap] TileBase.StartUp not being called when a different Tile with the same instantiated GameObject is set
[2D][Tilemap] TileBase.StartUp not being called when a different Tile with the same instantiated GameObject is set
Repro steps:
1. Open attached project, open SampleScene
2. Open tile palette window, select Circle Tile 2 and paint on Tilemap in scene, observe "Ran StartUp" output in console
3. Select Cross Tile 1 and attempt to paint over Circle Tile 2 in scene, observe tile is not overridden and "Ran StartUp" output does not appear in console
Expected result: TileBase.StartUp is called when a different Tile with the same instantiated GameObject is set over a current one
Actual result: TileBase.StartUp is not called when a different Tile with the same instantiated GameObject is set over a current one
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.2):
A fix for this issue is available on Unity 2021.2.0a20 and above