Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2017.4.0f1
2018.2.0f2
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1108989
Regression
No
AddExplosionForce()'s added force to Rigidbody's velocity is not relative to expected direction
Reproduction steps:
1. Open the project inside "case_1108989-AddExplosionForce_Problem.zip"
2. Open and Play "TestRigidbodyExplosiveForce2" scene
Expected: The circle will follow the predicted blue trajectory line
Actual: The circle flew not according to the trajectory line
Reproduces on: 2017.4.20f2, 2018.3.6f1, 2019.1.0b4, 2019.2.0a6
Note: Velocity relative change after explosion can be seen in "Cube" GameObject's "RigidbodyAddExplosion" component
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
- 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
Resolution Note (fix version 2019.1):
The issue was due to documentation being out of date. The documentation previously mentioned, that the explosion was towards the center of body. However, in reality it was towards the point on the surface of the body that is closest to the explosion location. The documentation was updated to reflect this.