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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Add comment