Search Issue Tracker
Fixed in 2018.3.5f1
Fixed in 2018.3.X, 2019.1.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.1f1
2019.1.0a1
2019.2.0a1
Issue ID
1119018
Regression
No
Static Circle and Dynamic Capsule 2D colliders do not collide when x coordinates are equal on both GameObjects
How to reproduce:
1. Open the "SampleScene_Track" scene in the attached "Bumper Cars Prototype 001.zip" project
2. Change the x coordinate to 0 on Playfield > Obstacle001
3. Constrain x Position and z Rotation on PlayerCar's RigidBody
4. Enter Play Mode
5. Press "w" or up arrow to move the PlayerCar until you reach the yellow obstacle
Expected Behavior: The PlayerCar collides with the obstacle
Actual Behavior: The PlayerCar moves through the obstacle like it is not there
Reproducible with: 2017.4.19f1, 2018.3.3f1, 2019.1.0b1, 2019.2.0a2
Note: Collision Events are called, but no collision happens. Both GameObjects must have equal x coordinates(it happens even when x is not 0). If you uncheck the constraints on the PlayerCar and do the same you will see that the PlayerCar collides with the obstacle but has a slight x Coordinate translation and the Rotation changes. The issue seems to only happen between Capsule and Circle Colliders.
--------------------------------
fixed in: 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment