Search Issue Tracker
In Progress
Fix In Review for 2021.3.27f1, 2022.2.22f1
Fixed in 2023.1.0b18, 2023.2.0a16
Votes
0
Found in
2020.3.47f1
2021.3.23f1
2022.2.16f1
2023.1.0b13
2023.2.0a13
Issue ID
UUM-35085
Regression
No
Tilemap.SetTile() instantiates twice when called in Player
Reproduction steps:
1. Open the attached Project “BugRepro”
2. Enter the Play Mode
3. Press the tiles with Mouse button
4. Observe the Console and how LogWarning only sets tile once
5. Build and Run the Project
6. Connect the Console to the Player and tap the tiles
7. Observe the Console
Expected result: Tile gets instantiated once in built Player on tap
Actual result: Tile gets instantiated twice per tap
Reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a13
Rperoducible on:
MacOS 13.3.1 (Intel)
Google Pixel 3 (Pixel 3), CPU: Snapdragon 845, GPU: Adreno 630, OS: 12.0.0
Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
iPhone 14 Pro Max, 16.3.1 iOS
iPhone 12, 14.1 iOS
iPad (9th generation), 15.0 iOS
iPad Pro 12.9", 13.4.1 iOS
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
- Sprite Asset changes are unsaved after updating sprite atlas
- Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
- [Quest 2] Running Entities Graphics/BatchRendererGroup under Vulkan results in a frame rate drop compared to OpenGLES 3 and causes Tile Binning to cost more
- Filters dropdown: Window doesn't rescale on items collapse
- Sprite Preview is broken when the Sprite is too tall or too wide
Resolution Note (fix version 2023.2.0a16):
Fix for this issue will be available on Unity 2023.2.0a16 and above
Resolution Note (fix version 2023.1.0b18):
Fix for this issue will be available on Unity 2023.1.0b18 and above