Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0f3
Issue ID
977343
Regression
No
[Standalone] Wrong collision points with collider2D inside Canvas
How to reproduce:
1. Open the "CanvasColliderRepro" project
2. Open the "Hard" scene
3. Press Play
4. Input 200 and press "Apply", notice that the collider hits another collider (text changes)
5. Build & Run the project
6. Input 200 and press "Apply", notice, that the collider doesn't hit another collider (text doesn't change)
Expected result: The collisions should work the same in Standalone as in Editor.
Actual result: The collision points in Standalone are wrong.
Reproducible with: 2018.1.0b1, 2017.3.0f3, 2017.2.1p1, 2017.1.2p4, 5.6.5f1.
Notes:
The input field inputs the Y size of the box collider on the spaceship.
If the box collider Y size of the spaceship is bigger than 235, the collider hits another collider, but in the wrong location (in standalone build).
Tested with Windows Standalone.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "UnassignedReferenceException" is thrown when building the project and a scene is selected in the Project View
- Android Player freezes on some Mali GPU devices when Lighting Cast Shadows changed to OFF at runtime
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
Add comment