Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0f3
Issue ID
1009394
Regression
No
RaycastHit.TextureCoord returns incorrect values if object has a negative scale
Steps to reproduce:
1. Open attached "QuadTextureCoord.zip" Unity project
2. Open "Main" scene
3. Enter Play mode
4. Observe Console log
Expected results:
RaycastHit.TextureCoord returns (0.5, 0.5) when the ray hits in the center of the Quad
Actual results:
RaycastHit.TextureCoord returns (0.5, 1.0) when the ray hits in the center of the Quad
Reproduced in: 2018.2.0a3, 2018.1.0b10, 2017.3.1p3, 2017.2.2f1, 2017.1.3p2, 2017.1.0a1
Note: Issue happens when either X or Y scale is negative
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