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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
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.