Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.0b10
2018.2.0f2
Issue ID
1064779
Regression
Yes
PhysX error is thrown when setting MeshCollider.isTrigger to true for a disabled GameObject
How to reproduce:
1. Open the attached "TestFor1064779.zip" project
2. Play the Scene
3. Observe the errors in the Console window
Expected result: no errors are thrown after setting MeshCollider.isTrigger to true
Actual result: PhysX error is thrown after setting MeshCollider.isTrigger to true
Reproducible with: 2017.3.0b10, 2017.4.8f1, 2018.1.9f1, 2018.2.2f1, 2018.3.0a4
Not reproducible with: 2017.1.5f1, 2017.2.3p3, 2017.3.0b9, 2018.3.0a5
Note: fixed in 2018.3.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment