Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.2.0a4
2017.3.1f1
Issue ID
1004443
Regression
Yes
Rigidbody not affected by Rigidbody.AddExplosionForce immediately after changing object’s transform position
Steps to reproduce:
1. Open attached “AddExplosionForce.zip” Unity project
2. Open “Main” scene
3. Enter Play mode
4. Observe the Cube object in Game view
Expected results:
AddExplosionForce force is applied to the object and the object is moved
Actual results:
AddExplosionForce force is not applied to the object and the object remains stationary
Reproduced in: 2018.2.0a1, 2018.1.0b8, 2017.3.1p2, 2017.2.2f1, 2017.2.0a4,
Didn’t reproduce in: 2017.2.0a3, 2017.1.3p1, 2017.1.0a1
Regression introduced in: 2017.2.0a4
Note: This issue does not reproduce if you instantiate the object directly at the desired position
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment