Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1315032
Regression
No
Shader.PropertyToID returns the same ID when Shader's properties have the same name but different type
How to reproduce:
1. Open the attached "ShaderPropertyToID.zip" project
2. Go to Test -> Material Test
3. Select the "TestShader" in the MaterialTest window
4. Press the "Perform Test" button
5. Observe the Console log
Expected result: _Glossiness property of type Range and Float have different ID
Actual result: _Glossiness property of type Range and Float have the same ID
Reproducible with: 2019.4.20f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a5
Could not test with: 2018.4.31f1 ('Shader' does not contain a definition for 'GetPropertyCount' and no accessible extension method 'GetPropertyCount')
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 (fix version 2021.2):
Removed duplicated property _GlossMapScale in urp shaders.
Fixed in: 12.0.0 (2021.2.0a9)