Search Issue Tracker
Fixed in 2019.3
Fixed in 2020.1
Votes
0
Found in
2017.4
2018.4
2019.3
2019.3.0f1
2020.1
Issue ID
1218373
Regression
No
TilemapRenderer.bounds are offset when a Tilemap's prefab is Instantiated in the Scene
How to reproduce:
1. Open the attached project named "Case_1218373"
2. Open the Sample Scene and enter Play mode
3. Double click the Tilemap gameObject to focus it
4. Zoom out in the Scene view a deselect the Tilemap
5. Observe the cyan Tilemap bounds and the actual Tiles in the Scene
Expected result: Tilemap bounds match the Tiles
Actual results: The bounds of the Tilemap are offset from the tiles
Reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.3.2f1, 2020.1.0a23
Notes:
1. When 2017.4 and 2018.4 the Tiles are not rendered at all, only their bounding box which is still offset when compared to the Debug bounds(Track_1218371_V2)
2. The bounds are calculated correctly when in Prefab mode
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
- [instability] assetBundleVariant YAML parse issue in HDRP package: DebugDisplayLatlong.sha
- Native object references for some object types are always 0 in the memory profiler
- [Android] InputField.onEndEdit is not called when turning off the TouchScreenKeyboard on an Android device
- Acute shadow acne when using two overlapping spotlights
- Raycast made on UI with multiple graphic Raycasters sort strangely when being on the same sorting layer and order
Resolution Note (fix version 2019.3):
Fixed in Unity 2020.2.0a2
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b2