Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
2
Found in
2018.1.0f2
2018.2.0b6
Issue ID
1044235
Regression
Yes
Shadergraph no longer works with the light weight render pipe
DESCRIPTION
Errors and warnings spewed when using the light weight render pipeline, and shadergraph. The shader graph window is incorrectly rendered.
Steps to Reproduce
- Create a new project with the light weight RP template.
- Add Shadergraph from package manager (Version 0.1.17)
NOTICE ISSUE >> Errors and warnings appear in log.
- Project window > right click > create > shader > PBR Graph.
- Open the created shader.
NOTICE ISSUE >> Menu is incorrect.
Image ShaderGraphIssue.png attached.
Warnings.
GUID [ca91dbeb78daa054c9bbe15fef76361c] for asset 'Packages/com.unity.shadergraph/Editor/Data/LightweightPipeline/LightWeightPBRSubShader.cs' conflicts with:
'Packages/com.unity.render-pipelines.lightweight/LWRP/Editor/ShaderGraph/LightWeightPBRSubShader.cs' (current owner)
We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.
Errors
Assembly has reference to non-existent assembly 'Unity.ShaderGraph.Editor' (Packages/com.unity.render-pipelines.lightweight/LWRP/Editor/com.unity.render-pipelines.lightweight.Editor.asmdef)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
Add comment