Search Issue Tracker
By Design
Votes
0
Found in [Package]
6.9.0
Issue ID
1203306
Regression
No
Shader Graph Master Node unsupported render pipeline error message is not informative enough
How to reproduce:
1. Create a new project
2. Install Shader Graph
3. Create a Shader Graph asset (either Unlit or PBR)
4. Double click it to open Shader Graph window
5. Mouse over the red exclamation error notification in Shader Graph
Expected result: The error gives you information, with either telling you what Master Nodes are supported in current Renderpipe, or by naming Renderpipelines which are available for the Master node
Actual result: "The current render pipeline is not compatible with this master node."
Reproducible with: 6.9.0, 6.9.2 (2019.2.17f1), 7.1.1, 7.1.6, 7.1.7 ( 2019.3.0f4, 2020.1.0a17)
Couldn't test: 2017.4.35f1 Shader Graph is not introduced, 2018.4.15f1 Shader Graph is not supported on the built-in pipeline
Notes:
- Reproducible on macOS, Windows
- Screenshot of reproduction result is attached in EditD
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
The documentation pages for each master node found in either the Shader Graph or the respective render pipeline package documentation lists the compatible render pipelines for each node. It will also tell you to check if a render pipeline is assigned in your graphics settings.