Search Issue Tracker
Fixed
Fixed in 2020.3.37f1, 2021.3.7f1, 2022.1.7f1, 2022.2.0a18, 2023.1.0a1
Votes
0
Found in
2020.3.35f1
2021.3.4f1
2022.1.2f1
2022.2.0a13
2023.1.0a1
Issue ID
UUM-1671
Regression
Yes
Instantiating Tilemap that has Rule Tile with "Default GameObject" set, creates extra copy of GameObject at (0,0,0) in builds
Reproduction steps:
1. Open "RuleTileTest" project
2. Open the "SampleScene" scene
3. Go to File -> Build and Run
4. Press on the "SpawnTileMap" button
Expected result: One white circle appeared
Actual result: Two white circles appeared
Reproducible with: 2020.3.25f1, 2020.3.34f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a15
Not reproducible with: 2019.4.39f1, 2020.3.24f1
Reproduced on: Windows 10
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
- “Baking ReferencedPrefabAuthoring!” errors are thrown when creating or deleting unrelated GameObjects in a SubScene that references prefabs
- Cannot scroll down to see all UI Builder Inspector items after content is resized
- Crash on SceneTracker::SetObjectDirty when entering Play mode on a project with specific Assets
- UI Toolkit's TextInput element does not inherit layout parameters from the TextField element when TextField.multiline is true
- The TileMap grid in the Tile Palette is not visible when Screen Space Ambient Occlusion is enabled
Resolution Note (fix version 2023.1.0a1):
Fix for this issue will be available on Unity 2023.1.0a1 and above
Resolution Note (fix version 2022.2.0a18):
Fix for this issue will be available on Unity 2022.2.0a18 and above
Resolution Note (fix version 2022.1.7f1):
Fix for this issue will be available on Unity 2022.1.7f1 and above
Resolution Note (fix version 2021.3.7f1):
Fix for this issue will be available on Unity 2021.3.7f1 and above
Resolution Note (fix version 2020.3.37f1):
Fix for this backport will be available on Unity 2020.3.37f1 and above