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
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
- [Linux] Top left corner of the screen is unresponsive when the Editor recompiles
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
Add comment