Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2
2021.2.0f1
Issue ID
1392288
Regression
No
Terrain detail meshes do not receive the correct lighting when using Light Layers in 2021.2
How to reproduce:
1. Open the user attached "HDRP 12.1 Grass Bug.zip" project
2. Open the "BugGrass" Scene found in the "BugGrass" folder
Expected result: Objects used as details on the Terrain GameObject receive proper lighting
Actual result: Details on the Terrain do not receive proper lighting
Reproducible with: 12.0.0 (2021.2.0b15), 12.1.2 (2021.2.7f1), 12.1.3 (2021.2.8f1)
Not reproducible with: 12.0.0 (2022.1.0a10), 13.0.0 (2022.1.0a12), 13.1.4 (2022.1.0b3)
Couldn't test with: 7.7.1 (2019.4.34f1), 10.8.1 (2020.3.26f1), 11.0.0 (2021.1.28f1) - HDRP does not support Detail shaders on those versions
Note:
- The issue seems to be caused by the Light Layers setting, turning it off fixes the issue
- The Light Layers setting can be turned off in the "DefaultHDRPAsset.asset" file
- Some versions of HDRP are very specific to the Unity Editor version, preventing consistent testing
- Reproducible on a new project in 2021.2
- Not reproducible with URP
- On a new project Light Layers setting can be found in "HDRP High Fidelity.asset" in the "Settings" folder
-
benjmitch
May 12, 2022 12:11
I've been tracking this issue since it affects my URP project, waiting for 2022.1 to become tech stream, which it now has. I've tried the upgrade, and the problem remains. I wonder if someone with access to the test project can check whether 2022.1.0f1 still has this issue in HDRP? If it's fixed in HDRP, it may not be fixed in URP - I can put together a test case if so.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This issue seems to have been fixed in 2022.1, so it would be preferred for user to upgrade to this version for the fix, so that the HDRP team can focus their efforts fixing existing issues.