Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.41f1
2021.3.13f1
2022.1.23f1
2022.2.0b15
2023.1.0a18
Issue ID
UUM-19901
Regression
No
The point value of RaycastHit is output incorrectly after the Physics.BoxCast when the halfExtents parameter is between 0.11 and 0.992
Steps to reproduce:
1. Open the “BoxCasterTesterZip” project
2. Enter Play Mode
3. Observe the Console
Expected result: Log “raycastHit.point = 3.5, -0.333, 0”
Actual result: Log “raycastHit.point = 0.11, 0, 0”
Reproducible with: 2020.3.41f1, 2021.3.13f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a18
Reproduced on: macOS Monterey 12.5.1 (Intel)
Note:
- Only reproducible when the “Caster” GameObject x position is [0.11; 0.992]
- Also reproducible in the Player
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
The halfExtends parameter is not set as per the documentation instructions:
https://docs.unity3d.com/ScriptReference/Physics.BoxCast.html
HalfExtends requires half the size of the box in each dimension. On the example only the X axis complies with that requirement.