Search Issue Tracker
Fixed
Votes
0
Found in [Package]
9.0.0-preview.14
Issue ID
1251456
Regression
No
[SRP Core] Exception thrown when placing a tile that's larger than the tilemap grid size
Reproduction steps:
1. Open attached project "TilemapTest.zip" and scene "SampleScene"
2. In Hierarchy window, select the "Grid" GameObject
3. In Tile Palette window, select the "Square" sprite
4. In Scene window, draw a single "Square" tile
Expected result: No exception is thrown
Actual result: "In order to call GetTransformInfoExpectUpToDate, RendererUpdateManager.UpdateAll must be called first." exception is thrown
Reproducible with: 2019.4.0f1 (URP 7.3.1), 2020.1.0b11 (URP 9.0.0-preview.14), 2020.2.0a13 (URP 9.0.0-preview.14,HDRP 9.0.0-preview.13)
Could not test with: 2018.4.23f1 (URP package unavailable)
Notes:
1. The issue reproduces with HDRP.
2. The issue reproduces with Tilemap Renderer "Mode" - Individual, and "Detect Chunk Culling Bounds" - Auto
3. The issue reproduces when placing an individual sprite initially, or when undoing the initial sprite. E.g. If working with two sprites, both will throw exceptions upon drawing their initial tiles and upon undoing them.
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note:
Fixed in 2020.2.0a15
Resolution Note:
Fixed in 2019.4.4f1
Resolution Note:
Fixed in 2020.1.0b14