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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment