Search Issue Tracker
Fixed
Fixed in 2022.1.18f1, 2022.2.0b9, 2023.1.0a11
Unknown (hidden) 2019.4.X, 2020.3.X, 2021.3.X
Votes
0
Found in
2019.4.39f1
2020.3.36f1
2021.3.5f1
2022.1.7f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-6574
Regression
No
Relative Velocity spikes when there are a lot of RigidBody2D GameObjects with Collision Detection set to Continuous
Reproduction steps:
# Open the attached project
# Open the SampleScene.unity Scene, located in the /Assets/Scenes folder in the Project window
# Enter Play Mode
# Observe the warnings logged in the Console window
Expected result: there shouldn’t be any Relative Velocity spikes and no warnings logged
Actual result: there are multiple Relative Velocity spikes and there are multiple warnings logged
Reproducible with: 2019.4.39f1, 2020.3.36f1, 2021.3.5f1, 2022.1.7f1, 2022.2.0a17, 2023.1.0a1
Reproducible on: MacOS 12.4 (21F79)
Notes:
* Setting the Collision Detection property on the GameObject’s RigidBody2D Component to Discrete fixed the issue
* The issue is reproducible on both Apple Silicon and Intel Editors
* If the spikes did not occur and no warnings in the Console window are logged, exit and enter the Play Mode again
{*}Forum Post{*}: [https://forum.unity.com/threads/impact-damage-after-multiple-hits.1274072]
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
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
- Crash on VFXMemorySerializer::StoreObjects when converting to Subgraph Block
Resolution Note (fix version 2023.1.0a11):
Fix for this issue will be available on Unity 2023.1.0a11 and above
Resolution Note (fix version 2022.2.0b9):
Fix for this issue will be available on Unity 2022.2.0b9 and above
Resolution Note (fix version 2022.1.18f1):
Fix for this issue will be available on Unity 2022.1.18f1 and above