Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.3.0b1
Issue ID
1080330
Regression
No
[Continous] Sometimes relativeVelocity returned in OnCollisionEnter2D is zero
Steps to reproduce:
1. Open attached project
2. Run scene SpheresTest
3. Wait for 4th collision against left wall
4. Notice that instead of bouncing like in three previous collisions, this time ball falls straight to the ground. This is because bounce is calculated using relativeVelocity and this time it's zero.
Reproduced with: 2017.4.11f1, 2018.2.8f1, 2018.3.0b1
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 PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Add comment