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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment