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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment