Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
5.5.4p1
Issue ID
922674
Regression
No
The bounciness combine value of a physics material affects the colliding objects
The bounciness combine value of a physics material affects the colliding objects
Steps to reproduce:
1. Open attached project.
2. Press play.
3. Observe how all the objects keep bouncing although they have physics materials that have bounciness values different than 1 and "Maximum"
4. Change the Combine parameter of the plane material.
5. Observe how the objects' behaviour changes accordingly.
Expected behaviour: According to documentation, "When two bodies are in contact, bounciness and friction modes are applied individually to each agent. So, when body A has a friction combine mode of Average and body B has mode Multiply, then A is going to behave according to average parameters and B according to multiplied parameters". According to the above, the Bounce combine parameter of an object should not affect the objects that are colliding with it. Only the bounciness value should affect them.
Actual Result: The colliding objects with the plane are affected by the combine value of the plane
Reproduced with: 5.4.5p3, 5.4.0f3, 5.5.4p1, 5.5.3p4, 5.5.0f2, 5.6.1p4, 2017.1.0b10, 2017.2.0a4,
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