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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment