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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment