Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.18f1
2022.2.0b9
2023.1.0a12
Issue ID
UUM-17799
Regression
No
Physics behave differently between Windows and macOS platforms
How to reproduce:
1. Open the user-attached “FloorIsLava.zip“ project
2. Build the project
3. Run the Build and observe the falling objects
4. Build for a different Target Platform
5. Open the second Build on the other OS and observe the same objects
Expected result: In both of the Builds objects end up in the marked areas.
Actual result: Depending on the Build's Target Platform, the objects end up in different places.
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b9, 2023.1.0a12
Reproducible on: macOS 11.6.5 (Intel), Windows 11
Note: The same differences in behavior can be seen in the Editors for different platforms when entering Play mode.
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
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
- Selection highlight is drawn in an Animation Window when clicking in another Animation Window after highlighting items in the first one
Resolution Note:
Regarding WebGL build issue, it cannot be resolved because WebAssembly does not enable fine-grained control of numerical accuracy in physics simulations, so simulation consistency (compared to other platforms) will unfortunately not be possible to guarantee. If you want to get a more detailed explanation, please visit https://github.com/WebAssembly/design/issues/1429.
Thank you!
Resolution Note (2023.1.X):
Regarding WebGL build issue, it cannot be resolved because WebAssembly does not enable fine-grained control of numerical accuracy in physics simulations, so simulation consistency (compared to other platforms) will unfortunately not be possible to guarantee. If you want to get a more detailed explanation, please visit https://github.com/WebAssembly/design/issues/1429.
Thank you!