Search Issue Tracker
Active
Votes
1
Found in
1.3.15
Issue ID
UUM-132649
Regression
No
Unity Physics: The NativeList<DistanceHit> randomly returns fewer hits than expected when using CalculateDistance in Edit mode tests
Reproduction steps:
1. Open the attached “IN-88319“ project
2. Open the Test Runner window (Window → General → Test Runner)
3. Run All tests
4. Observe the Test Runner window
Expected result: All tests are successful. The “Hit count” is always 2
Actual result: Tests randomly fail. The “Hit count” is sometimes 1 or 0
Reproducible with: 2022.3.52f1, 6000.0.26f1, 6000.1.0a3
Couldn’t test with: 2021.3.46f1 (Unity Physics is not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: May need to run the tests multiple times to reproduce the issue
Comments (2)
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 FindNearestVertex when objectsToSearch array contains a null transform
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
hrjunker
Nov 11, 2024 12:39
The issue is also present for CollisionWorld.CastRay(RaycastInput, out RaycastHit)
hrjunker
Nov 11, 2024 12:27
The issue is also reproducable on MacOS 15 (Sequoia)