Search Issue Tracker
By Design
Votes
0
Found in
5.4.0b21
Issue ID
813456
Regression
No
Barycentric coordinates are not correctly reported as part of RaycastInfo when using volumetric/swept collision tests
Steps to reproduce:
1. Open my attached project "Example - 813456".
2. Open "BarycentricTraceReportage" scene.
3. Enter play mode.
4. Observe "CylinderMeshTrace" objects inspector while you move it.
--- Note that while you move this object his script displays barycentric values.
Expected result: All three values should approximately show the same value.
Actual result: Only raycast displays right results, while Sphere and rigidbody displays value of (1,0,0).
Reproduced with: 5.4.0f1, 5.4.0b25, 5.3.5p8, 5.3.5f1, 5.2.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment