Search Issue Tracker
By Design
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)
-
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)
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:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as As Designed. If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as As Designed. If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.