Search Issue Tracker
By Design
Votes
0
Found in
2019.2
2019.2.19f1
2019.3
2020.1
2020.2
Issue ID
1233682
Regression
No
Raycast made on UI with multiple graphic Raycasters sort strangely when being on the same sorting layer and order
Steps to reproduce:
1. Open user-supplied project ("GraphicRaycaster2019.zip")
2. Enter Play mode in the Sample Scene
3. Notice the Console
Expected: the "Input Blocking Overlay" is called after "Front Button"
Actual: the order is reversed
Reproduced in: 2019.2.21f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a5
Note: User claims that this bug does not reproduce in 2018.4, you can check it with the attached project ("GraphicRaycaster2018.zip")
However, I cannot confirm that, since the 2019 project breaks when backported to 2018.4
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
- Crash on DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Resolution Note (2020.2.X):
2018 project and 2019 project are not the same. The root canvas in 2018 has a GraphicRaycaster 2019 does not. The system requires the root raycaster as it uses that to determine which raycasters belong to one grouping of events. Without the root it counts each raycaster as its own hierarchy of objects and it will fall back to distance to object/ no sorting if everything is the same.