Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1228427
Regression
No
Uninformative error message is thrown when Property's Reference name is the same as the Property's Type name
How to reproduce:
1. Create a new HDRP template project
2. Create a PBR Graph (Right-Click in the Project Window, then Create->Shader->PBR Graph)
3. Open the Graph by Double-Clicking it
4. Create a Color Property by clicking the plus sign and selecting it from the context menu
5. Change Color Property's Reference name to "Color"
6. Drag the Property into the blackboard
7. Connect the Color Property to the Master Node
Expected result: An error informing the user about an incorrect Reference name is thrown
Actual result: An uninformative error is thrown
Reproducible with: 2019.3.6f1 (7.1.8, 7.2.1), 2020.1.0b2 (8.0.1), 2020.2.0a4 (7.1.7, 8.0.1)
Couldn't test with: 2017.4.38f1 (Package Manager does not exist), 2018.4.19f1 (4.10.0-preview, 0.1.8 - no options for Properties)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Workaround: please don't use names reserved for ShaderLab.
We use a bison-generated parser which is quite difficult to modify. We will replace it eventually (we have an item in the backlog), but right now it's impractical to fix.