Search Issue Tracker
Fixed
Fixed in 2022.3.18f1, 2023.2.6f1, 2023.3.0b3, 7000.0.0a1
Votes
0
Found in
2022.3.14f1
2023.2.1f1
2023.3.0a15
Issue ID
UUM-57053
Regression
No
Tilemap.RefreshAllTiles does not call StartUp function when tiles have an Instanced GameObject attached
How to reproduce:
1. Open the attached “tilemap_issue” project
2. Open the “DemoScene” (Assets > BugExample > Scene > DemoScene)
3. Enter Play mode
4. In the console, take note that the StartUp function is called on both tiles (A and B)
5. Clear the console and press the “RefreshAllTiles” button
6. Observe how only tile B will have its StartUp function called
Expected result: Both tiles will have their StartUp function called
Actual result: Only the tile without an Instanced GameObject attached has its Startup function called
Reproducible in: 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Could not test with: 2021.1.32f1 (feature does not exist)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Also reproducible in Player
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 7000.0.0a1):
Fix for this issue will be available on Unity 7000.0.0a1 and above
Resolution Note (fix version 2023.3.0b3):
Fix for this issue will be available on Unity 2023.3.0b3 and above
Resolution Note (fix version 2023.2.6f1):
Fix for this issue is available on Unity 2023.2.6f1 and above
Resolution Note (fix version 2022.3.18f1):
Fix for this issue is available on Unity 2022.3.18f1 and above