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
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment