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
Comments (1)
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
- Manual reference page for Grid Selection is missing
- Awaitable.NextFrameAsync causes GC Alloc 0.7 KB when using CancellationToken
- Prefab "Overrides" list item popups are overridden when navigating with keyboard arrow keys
- Alpha Tolerance setting does not affect generated outlines when generating Custom Physics Shape in the Sprite Editor
- The information/help message section misses a margin in the "Profiler" window
AllocTFP
Feb 16, 2025 12:02
Thanks for this getting fixed. Can the fix be backported to the LTS versions though (especially concerned about 2022.3)?