Search Issue Tracker
By Design
Votes
0
Found in
4.3.0f4
Issue ID
576378
Regression
No
Object behave in an incorrect way when intersecting with a collider
Steps to reproduce :
- import the project attached
- open the scene "sc1" and press play
- press "w" to jump and notice the behavior of the player
*Note :
In order to emphasize this more select Chain in the Hierarchy and set the force to 470 in the Playertest script
Explanation :
The user is ignoring collisions between the player and the platform when the velocity shows that it is moving up. Given then velocity in the default project, this ends when the player is in the middle of the platform i.e. the player and the platform are forced to be overlapping.
Box2D solves overlaps by applying an impulse to solve this overlap through the nearest exterior point which is at an angle.
It seems the user somehow expects that all overlaps are solved by moving an object upwards and whilst that may be what the user wants, this simply isn't the case.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Add comment