Search Issue Tracker
Fixed
Fixed in 2023.1.0a12
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b4
2023.1.0a6
Issue ID
UUM-12440
Regression
Yes
Raycasts fail to hit Collider when there is a different GameObject with a Collider very far away in the scene
How to reproduce:
1. Open the attached project "case_1136525-RaycastBug" and scene "TestScene"
2. Enter Play Mode
3. In the Hierarchy select the "OutOfBoundsObject" GameObject and make it active through the Inspector
4. Observe changes in the Console Window
Expected result: the Console Window keeps outputting "Hit == True" at all times in Play Mode
Actual result: Console Window starts showing "Hit == False" when "OutOfBoundsObject" is disabled
Reproducible with: 2018.3.0a5, 2018.3.9f1, 2019.1.0b7, 2019.2.0a8
Not reproducible with: 2017.4.23f1, 2018.3.0a4
Note: both "RaycastTarget" and "OutOfBoundsObject" have to have RigidBody Components. The "RaycastTarget" fails to be hit only when in certain configurations of its position and the raycast origin's position
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Assertion failed on expression 'success && actual == size' error is thrown when building project to another partition with a different file system
- Import Activity window shows "(None)" in the Asset field when changing the path of the asset
- Material setting changes when saving the Scene
- Sprite Mask's Alpha Cutoff value dragging is too sensitive
- Hover style remains on elements after the cursor is moved away when the 'transition-delay' property is used
Add comment