Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.2
2019.4.6f1
Issue ID
1267509
Regression
Yes
Physics2D Multithreading not behaving as expected
Reproduction steps:
1. Open attached project "MT Physics2D.zip" and scene "SampleScene"
2. Enter Play Mode
3. When MT is ON observer that the boxes hitting the platforms cause the platforms to fall quite far. When the MT is OFF this doesn't happen. Note that turning off the XY position constraints on the Platform Rigidbody2D does the same proving it is related to this.
Expected result: The platforms react the same when the MT solver option is on or off.
Actual result: Platforms react differently when the MT solver is ON.
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
- [iOS] Mute Other Audio Sources is not muting background audio on a device when toggled on
- Local keywords can be overridden by global keyword state
- Material Constructor doesn't copy ShaderKeyword from material in Play Mode
- IL2CPP error at Unity.IL2CPP.HashCodeCache`1.GetUniqueHash(T value) when building on Android
- [URP] [Debug View] [Mobile] Lighting Features - missing “Everything” checkbox (editor panel has it)
Resolution Note (fix version 2020.2):
The multi-threaded solver didn't correctly handle contact masses for the XY position constraints. This was correct for the non-multi-threaded solver so only affects the multi-threaded mode. Note that turning off the XY position constraints in the multi-threaded solver stops the problem.