Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0b3
Issue ID
866749
Regression
No
RaycastHit.textureCoord always returns a zero vector against GameObjects with meshcollider
Reproduction steps:
1. Open my attached project.
2. Open the scene
3. Enter Play mode
4. Press on the rectangle object a few times in different locations
Result: a zero vector is returned from RaycastHit.textureCoord, this behavior is only expected when the collider is NOT a mesh collider. In this case it shouldn't return a zero vector.
Reproducible on: 5.4.4f1, 5.5.0p3, 5.6.0b3
Tested on Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
Add comment