Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0f2
Issue ID
1035922
Regression
No
RaycastCommand gives incorrect results when direction vector is not normalized
How to reproduce:
1. Open given Unity project
2. Enter "SenseTest" scene
3. Enter Play Mode
4. Select scene window
5. Select "SenseManager" in the hierarchy
6. Check Use Jobs checkbox
7. Check Normalize Direction checkbox
8. Notice difference between in scene
Expected result: In both ways scene should remain the same
Actual result: When RaycastCommand is created with normalized vector result is different than the one which is created without normalizing the vector
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.0f2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Add comment