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
- [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
Add comment