Search Issue Tracker
Fixed in 2020.1.X
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Add comment