Summary
The issue at hand is an isometric tilemap sorting order problem in Unity, where the sorting breaks when using multiple sprites, even with identical Pixels Per Unit (PPU) and pivot settings. This results in a “layer soup” effect, where background tiles render on top of foreground tiles.
Root Cause
The root cause of this issue is due to the following factors:
- Transparency sorting: When using multiple sprites, Unity’s transparency sorting system can become confused, leading to incorrect sorting orders.
- Custom pivot: Although the custom pivot is identical for all sprites, it can still affect the sorting order, especially when combined with transparency sorting.
- Sprite asset differences: Despite having identical dimensions and PPU settings, the different sprite assets can still cause sorting conflicts due to their unique characteristics, such as texture and color.
Why This Happens in Real Systems
This issue occurs in real systems because of the complexities of isometric rendering and transparency sorting. When dealing with isometric layouts, the sorting order is not as straightforward as it is with traditional 2D or 3D rendering. The combination of custom pivots, transparency sorting, and multiple sprite assets can lead to unexpected sorting conflicts.
Real-World Impact
The impact of this issue can be significant, leading to:
- Visual glitches: The “layer soup” effect can be distracting and immersion-breaking, affecting the overall gaming experience.
- Performance issues: Incorrect sorting orders can lead to increased rendering times and decreased performance, especially in complex scenes.
- Development delays: Resolving this issue can be time-consuming, delaying the development and release of the game.
Example or Code
// Setting up global sorting for isometry
GraphicsSettings.transparencySortMode = TransparencySortMode.CustomAxis;
GraphicsSettings.transparencySortAxis = new Vector3(0, 1, -1);
// Using a custom sorting order for the tilemap renderer
tr.sortOrder = TilemapRenderer.SortOrder.TopRight;How Senior Engineers Fix It
To resolve this issue, senior engineers can try the following approaches:
- Use a single sprite atlas: Combining all sprites into a single atlas can simplify the sorting process and reduce conflicts.
- Implement custom sorting logic: Writing custom sorting code can provide more control over the sorting order and help resolve conflicts.
- Adjust the transparency sorting settings: Experimenting with different transparency sorting modes and axes can help find a solution that works for the specific use case.
- Use a different tilemap renderer mode: Switching to a different renderer mode, such as TilemapRenderer.Mode.Batch, can help improve performance and reduce sorting conflicts.
Why Juniors Miss It
Junior engineers may miss this issue due to:
- Lack of experience with isometric rendering: Isometric rendering can be complex, and junior engineers may not be familiar with the unique challenges it presents.
- Insufficient understanding of transparency sorting: Transparency sorting can be tricky to grasp, and junior engineers may not fully comprehend how it affects the sorting order.
- Overreliance on default settings: Junior engineers may not think to adjust the default settings, such as the transparency sorting mode and axis, which can lead to sorting conflicts.