Search Issue Tracker
Fixed in 2018.1.X
Votes
3
Found in
2017.1.0b9
2017.2.0p3
Issue ID
974500
Regression
Yes
Graphics Raycaster returning wrong object if the distance between two rays is too small
Steps to reproduce:
1. Open user attached project
2. Start play mode
3. Click on the "Floor" object that has an above "Bottom" object
4. Notice that "Floor" game object is returned if the raycast distance between "Bottom" and "Floor" objects is too small
Expected result: "Bottom" object should be returned
Actual result:"Floor" game object is returned
Reproduced in: 2017.2.0p4, 2017.1.2p3, 2017.1.0b9
Not reproduced in: 2017.1.0b8, 5.6.4p3
Regression since: 2017.1.0b9
Fixed in: 2018.2.0a3, 2018.1.0b10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Add comment