Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.5f1, 6000.2.0b2
Votes
0
Found in
6000.0.47f1
6000.1.0b15
6000.2.0a9
Issue ID
UUM-103933
Regression
No
The LayerMask parameter is ignored when using Physics2D.GetRayIntersection method
How to reproduce:
1. Open the attached “IN-99321” project
2. Open the “SampleScene“
3. Enter Play mode
4. Hover the mouse over the “Triangle“ GameObject
5. Press the Spacebar on the keyboard
6. Hover the mouse over the “Circle“ GameObject
7. Press the Spacebar on the keyboard
8. Observe the results in the Console window
Expected result: The Raycast detects only the “Triangle“ GameObject with the “UI“ layer
Actual result: The Raycast detects both the “Triangle“ and “Circle“ GameObjects with different layers set
Reproducible with: 2023.1.0a19, 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Couldn’t test with: 2022.3.61f1, 2023.1.0a18 (GetRayIntersection method is different from newer Unity versions)
Reproducible on: MacOS 15.3 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Resolution Note (fix version 6000.2.0b2):
Fix for this issue is available on Unity 6000.2.0b2 and above