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
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
Resolution Note (fix version 2021.2):
A fix for this issue is available on Unity 2021.2.0a20 and above