Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.5.0f4
Issue ID
608511
Regression
Yes
Description of Rigidbody.AddExplosionForce uses wrong parameter names in description
-e: see title
-repro:
--open /Documentation/html/en/ScriptReference/Rigidbody.AddExplosionForce.html
--NOTICE the description doesn't make a lot of sense using the explosionRadius way too often
-----------
This is how it reads in 4.3.4:
If radius is 0, the full force will be applied no matter how far away position is from the rigidbody. upwardsModifier applies the force as if it was applied from beneath the object. This is useful since explosions that throw things up instead of pushing things to the side look cooler. A value of 2 will apply a force as if it is applied from 2 meters below while not changing the actual explosion position. explosionPosition is the position from which the explosion force is to be applied. explosionRadius is the radius of the explosion. Rigidbodies further away than explosionRadius will not be affected.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
- Mixers do not have "Rename" in the right-click context menu when a Mixer is right-clicked in the Audio Mixer window
Add comment