Search Issue Tracker
Fixed in Unity 2018.3
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
- Windows High DPI scaling breaks Graphics.DrawTexture
- Particle system billboard particles are invisible when specific "3D Start Rotation" with "Random Between 2 Constants" is applied
- Preview Camera has wrong CameraType when Camera preview is present on Scene View
- Scaling the box in Events Example of ExtOSC plugin causes Unity to crash
- [HDRP] The Game Object is invisible in the Scene and Shader Graph prieview when the Transform node set World to Object position
Add comment