Search Issue Tracker
Active
Votes
0
Found in
1.4.3
Issue ID
UUM-107655
Regression
No
Unexpected closest distance results happen when using Physics Collider Queries
How to reproduce:
1. Open the attached “IN-100928” project
2. Open the “Query - Closest Distance” scene (Assets >7. Queries > Query - Closest Distance)
3. Open the “Query - Closest Distance SubScene” and enter Play mode
4. Observe the result in the Scene View
Expected result: The green line ends at the same point as the closest distance marks
Actual result: The green line extends through one of the cubes
Reproducible with: 2022.3.13f1, 2022.3.62f1, 6000.0.49f1, 6000.1.4f1, 6000.2.0b3
Could not test with: 2022.1.0a1, 2022.3.0f1 (material issues with downgrading)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment