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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
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.