Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2018.3.5f1
2018.4.6f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1177698
Regression
Yes
Rigidbody Collision Detection mode cannot be updated after setting the isKinematic field to true then false during runtime
How to reproduce:
1. Open user's attached project ("RigidBodyCollisionDetectionChange.zip") using the EnvIronman VM (more information in Edit)
2. Open the sample scene
3. Enter Play mode
4. Observe where the green Cube GameObjects collide
Expected result: Green Cube GameObjects collide exactly like the red Cube GameObjects
Actual result: Green Cube GameObjects collide exactly like the blue Cube GameObjects
Reproducible with: 2018.4.7f1, 2019.1.14f1, 2019.2.2f1, 2019.3.0a12, 2020.1.0a1
Notes:
The Inspector window displays the Collision Detection mode as expected.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 2021.1):
CCD type is restored to specified Collision Detection type in Rigidbody Inspector when isKinematic is toggled from true to false