Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.2.0a9
Issue ID
1139800
Regression
No
Isometric Tilemap is not being sorted properly when using a custom Cell Size and multiple chunks with different tiles
How to reproduce:
1. Open attached OC project
2. Inspect the Scene or Game View.
To reproduce the extra bug, probably related to this:
3. Open Window > 2D > Tile Pallete
4. Select any Tile
5. Draw some of it on a Tilemap
6. Move your mouse towards the top right corner of the Scene View
Expected result: Tiles are being sorted normally
Actual result: Some tiles are above others
Reproducible with - 2018.3.12f1, 2019.1.0b10, 2019.2.0a10
Could not test with - 2017.4.25f1 (no isometric tilemap)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
The Tiles used in this scene overlap in such a way that Chunk mode rendering by the TilemapRenderer will not work for this.
You could try Individual mode rendering with the TilemapRenderer with the Top Left Sort Mode together with the Custom Axis Sort mode for sorting the Tiles. Also, the ground tiles can be atlassed together using the Sprite Atlas. This will improve the rendering performance of this scene too.