Search Issue Tracker
By Design
Votes
0
Found in [Package]
11.0.0
Issue ID
1304362
Regression
No
The Receive Shadows property is displayed in the Inspector under the Mesh Renderer component when the Debug mode is enabled
How to reproduce:
1. Open the attached '1304362.zip' project
2. Open 'SampleScene'
3. In the Hierarchy window select 'Cube'
4. Click on the three dots located in the upper right corner of the Inspector and select 'Debug'
5. Observe the Mesh Renderer component in the Inspector
Expected result: The Receive Shadows property is not displayed
Actual result: The Receive Shadows property is displayed
Reproducible with: Universal RP 7.5.2 (2019.4.18f1), 8.3.1 (2020.1.17f1), 10.2.2 (2020.2.2f1, 2021.1.0b2, 2021.2.0a1), 11.0.0 (2021.1.0b2, 2021.2.0a1)
Cannot test with: 2018.4.30f1 (the Universal RP package is not supported), Universal RP 11.0.0 (2020.1.17f1, 2020.2.2f1) (the package version is not supported)
Notes:
- The Receive Shadows property is not displayed under the Mesh Renderer component when the Inspector is in the 'Normal' mode
- The Receive Shadows property can be found in the Material properties under the Surface Options
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
Resolution Note:
The option is hidden from UI because URP doesn't support receive shadows in the mesh, it instead support in the material allowing meshes with multiple materials to select individually whether to receive shadow or not.
When the inspector is in Debug mode it shows all serialized properties. The receive shadows appear because we can't remove the serialized property as it's used in built-in and will need to remember it's state in case the pipeline is switch to built-in RP.