Search Issue Tracker
By Design
Votes
0
Found in
2021.2
2021.2.0b5
2022.1
Issue ID
1356219
Regression
No
Modifiable Contact Pair order is swapped when in build
How to reproduce:
1. Open the user's attached project
2. Press the Play button
3. Observe the sphere movement in the Game view
4. Build and Run the project
5. Observe the sphere movement in the build
Expected result: the direction of the sphere's motion is consistent between the Editor and the build
Actual result: the direction of the sphere's motion is different between the Editor and the build
Reproducible with: 2021.2.0b11, 2022.1.0a7
Could not test with: 2019.4.30f1, 2020.3.17f1, 2021.1.20f1 (error CS0246: The type or namespace name 'ModifiableContactPair' could not be found)
Comments (1)
-
PandaArcade
Jun 02, 2024 02:36
Please update the docs to say 'One cannot rely on the order of Colliders in a pair'.
Add comment
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 __pthread_kill when initializing Vuplex WebView while entering the Play Mode
- Crash on FindSurface when adding a custom Renderer Feature to a 2D Renderer Data Asset
- [Android] [Vulkan] [UI Toolkit] Application crashes when the device is rotated when it has UI Toolkit TextField on Vulkan devices
- Crash on DualThreadAllocator<DynamicHeapAllocator>::TryDeallocate when opening a specific project
- Crash on memset_repstos when pressing a UI button while in Play Mode
Resolution Note:
The order of GameObject initialisation can be different Editor vs Player, and this shows here apparently. On closer examination, turned out the SphereCollider/MeshCollider order was different here, so that's why the behaviour didn't match. One cannot rely on the order of Colliders in a pair.