Search Issue Tracker
Fixed
Fixed in 1.8.4-preview, 2.2.4, 3.0.3, 4.0.0-pre.2
Votes
0
Found in [Package]
2023.1.0
Issue ID
DANB-231
Regression
No
There's a difference in positions when one Tile is placed with the "Default Brush" and the other one with "GameObject Brush"
Reproduction steps:
# Open the attached project
# Open the Tile Palette (Window > 2D > Tile Palette)
# Select the “Floor Grid” GameObject in the Hierarchy window (Board > Grid - Floor > Floor Grid)
# Select a Tile in the Tile Palette and place it in the Scene View
# Switch to “GameObject Brush” in the Tile Palette
# Place the Tile in the same place where the previous Tile was placed
# Observe the Tiles in the Scene view
Expected result: Both Tiles are in the same place
Actual result: There’s an offset between the Tile that was placed with the “GameObject Brush” and the one placed with “Default Brush”
Reproducible with: 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Couldn’t test with: 2020.3.39f1 (couldn’t downgrade, “GameObject Brush” not present)
Reproducible on: Windows 10 (21H2)
Note: The offset is proportional to the Cell Gap value set on the Grid Component (“Grid - Floor” GameObject)
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
- Spots of bad lighting appear on assets when the lighting is generated in a Scene
- Static Editor Flags dropdown list is cut off when Inspector Window is docked to the very right and UI Scaling is set to a higher value
- visionOS Players are minimized when Guided Access is turned on
- Licensing Client fails to launch when opening Unity Hub
- Sprite Atlas Inspector preview disappears when entering Play mode unless SpriteAtlasMode is set to "Sprite Atlas V2 - Enabled"
Resolution Note (fix version 4.0.0-pre.2):
Fix for this issue is available in Tilemap Extras package 4.0.0 and above
Resolution Note (fix version 3.0.3):
Fix for this issue is available on Tilemap Extras package 3.0.3 and above
Resolution Note (fix version 2.2.4):
Fix for this issue is available on Tilemap Extras package 2.2.4 and above
Resolution Note (fix version 1.8.4-preview):
Fix for this issue is available on Tilemap Extras package 1.8.4-preview and above