Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b1
Issue ID
629242
Regression
Yes
Collider.raycast from a non-convex mesh collider causes crash
MeshCollider.Raycast causes a crash, when called by a non-convex mesh collider with a dynamic rigidbody.
To reproduce:
1. Open repro2.unitypackage
2. Open scene repro. It contains a directional light with a mesh collider and a rigidbody. There is also a script attach that calls a raycast from the mesh collider on start
3. Enter play mode
4. Unity crashes
Though non-convex meshes + dynamic rigidbodies are not supported, unity should not crash.
Regression since 5.0.0a16
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment