Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2019.4
2019.4.3f1
Issue ID
1267052
Regression
No
Raycast sometimes misses a GameObject when continuously hitting it after previously hitting other GameObject
How to reproduce:
1. Open the attached "Selection-Debug" project
2. Open the "Selection" Scene (Assets->Game->Engine->Selection->Tests)
3. Enter the Play Mode
Expected results: No "Entity.Null" message is logged after the Raycast switches to hitting another GameObject
Actual results: "Entity.Null" message is logged after the Raycast switches to hitting another GameObject
Reproducible with: 2019.3.1f1, 2019.4.7f1
Could not test with: 2018.4.26f1, 2019.3.0f6, 2020.1.0a1, 2020.1.1f1, 2020.2.0a20 because of the namespace errors
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
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
Resolution Note (2020.2.X):
Customer indicated the problem may be in their code, and asked us to put the ticket on hold for the time being.