Search Issue Tracker
Fixed in 2020.1
Votes
1
Found in
2018.4
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1198442
Regression
No
RaycastResult.sortingLayer always returns the default Layer when Raycast hits a GameObject with a Tilemap Renderer
How to reproduce:
1. Open the user-submitted project "RaycastHit.sortingLayer.zip"
2. Open the SampleScene
3. Enter Play mode
4. Click on the Tilemap GameObject
Expected result: "My Sorting Layer" is printed as RaycastResult.sortingLayer
Actual result: "Default" is printed as RaycastResult.sortingLayer
Reproducible with: 2018.4.13f1, 2019.2.14f1, 2019.3.0b12, 2020.1.0a14
Notes:
Could not test on Unity 2017.4, due to a fatal error being thrown when opening the project.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [2D Path] Box selection for objects inheriting GenericScriptablePath is offset on the Y-axis
- [Linux] Unity licensing command on Linux doesn't complete when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
Add comment