Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
1
Found in
6000.0.56f1
6000.2.1f1
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-114976
Regression
No
Objects are hit in an unexpected order when casting using maxHits
How to reproduce:
1. Open the project “IN-111393_Raycasting Sample”
2. In the Game tab, make sure to enable Gizmos in the top right corner
3. Enter Play Mode
4. Click the button “Regenerate”, located in the top left corner to the Game tab
5. Observe the outlines on the cubes
Expected result: The second, third and fourth row cubes are highlighted due to the ray casting emitted from the first row of cubes
Actual result: Further away cubes are affected by ray casting while the closer cubes are unaffected
Reproducible with: 2023.1.0a1, 6000.0.56f1, 6000.2.1f1, 6000.3.0a5 (36d7e9fd6645)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- This issue is not specific to ray casting, any casting (Boxcast, Capsulecast etc.) using maxHits exhibits same funtionality.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reuse Collisions Callbacks is not enabled by default when opening a new project with HDRP template
- Bloom and Exposure Artifacting around GameObject appears when setting Scale of Z Axis to 0
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
Add comment