Search Issue Tracker
Fixed in 2017.2.X
Votes
9
Found in
5.4.0f3
Issue ID
822307
Regression
No
[GraphicRaycaster] inconsistent behavior between 2D and 3D colliders behind Canvas
Reproduction steps(GIF attached):
1. Open "UI" project.
2. Open "scene" scene.
3. Check "1", "2", "3", "4" game objects collider types and their position relative to "Canvas" game object.
4. Play the scene.
5. Hover the mouse pointer over every quad ("1","2","3","4").
Actual result:
* 1st quad doesn't hit.
* 2nd quad hits.
Expected result:
* 1st and 2nd quad doesn't hit.
OR
* 1st and 2nd quad hits.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment