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
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- Threads dropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
Resolution Note (fix version 2021.2):
Removed duplicated property _GlossMapScale in urp shaders.
Fixed in: 12.0.0 (2021.2.0a9)