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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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.