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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment