Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
1
Found in
2020.3.39f1
2021.3.10f1
2022.1.17f1
2022.2.0b8
2023.1.0a11
Issue ID
UUM-15944
Regression
No
GameObject bounces differently in Player compared to Play Mode
How to reproduce:
1. Open the project “IN_14124”
2. Open “SampleScene” in Scenes
3. Enter Play Mode
4. Observe the ball
5. Press File → Build And Run
6. Observe the ball
Expected result: The ball behaves the same on different platforms compared to Play Mode
Actual result: The ball behaves differently on different platforms compared to Play Mode
Reproducible with: 2020.3.39f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a11
Reproducible on: Windows 10 Pro
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Collisions in WebGL behave differently than in Editor and the Windows build which is a totally different perspective considering cross-compilation into JS.
Resolution Note (2023.1.X):
Collisions in WebGL behave differently than in Editor and the Windows build which is a totally different perspective considering cross-compilation into JS.