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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment