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
- Template is opened in Isolation when opening it in Context and users Save the UI Document when prompted to do so in UI Builder
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
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.