Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment