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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment