Search Issue Tracker
Fixed in 2.2.5
Fixed in 4.0.0
Votes
0
Found in [Package]
4.0.0-pre.2
Issue ID
DANB-362
Regression
Yes
[2D][Tilemap] Brush tools produce incorrect transormation when using GameObject Brush
How to reproduce:
1. Open the attached Project "TIlemap_SamplesTest" and load Scene "SampleScene"
2. Open the Tile Palette window (Window -> 2D -> Tile Palette)
3. Change the Brush to GameObject Brush
3. Paint the yellow circle in the Scene
4. Press the counter-clockwise rotation button in the Tile Palette window
5. Paint the yellow circle again
Expected result: the circle is rotated counter-clockwise
Actual result: the circle is rotated clockwise
Reproducible with: 2023.1.0a18, 2023.1.0a26
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a17
Reproduced on:
- MacOS (Intel) Editor
Notes:
- Prior to 2023.1.0a18 the buttons for transformation were not available in the Tile Palette window and were accessible through shortcuts (such as "[" and "]" for clockwise and counter-clockwise rotation respectively). It appears like the shortcuts were reversed with the addition of the buttons which is reflected in the Default Brush and the tooltips for the buttons, however, the GameObject Brush still uses the old rotations
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Fix for this issue is available on 2D Tilemap Extras package 4.0.0 and above
Resolution Note:
Fix for this issue is available on 2D Tilemap Extras package 3.1.0 and above
Resolution Note:
Fix for this issue is available on 2D Tilemap Extras package 2.2.5 and above