Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
10.10.0
12.1.7
13.1.8
14.0.3
15.0.1
Issue ID
SGB-298
Regression
No
Shader Graph's preview can't compile when the first output is not a Vector, Matrix, or Boolean type
How to reproduce:
1. Open the attached “ShaderGraphIssue” project
2. Open the “New Shader Sub Graph” asset
3. Observe the area around the Output node
Expected result: There is no exclamation mark near the Output node
Actual result: An exclamation mark near the Output node produces this error when hovering the cursor over it: "Validation: Preview can only compile if the first output is a Vector, Matrix, or Boolean type. Please adjust slot types". A preview with missing textures is also present
Reproducible with: 10.10.0 (2020.3.39f1), 12.1.7 (2021.3.11f1), 13.1.8 (2022.1.20f1), 14.0.3 (2022.2.0b10), 15.0.1 (2023.1.0a12)
Reproducible on: Windows 10
Note: The same issue can be observed if the Output slot is Texture2D, Texture2D Array, Texture3D, Cubemap, or Gradient
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
- 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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This is working as intended. Sub Graph will use the first output, regardless of type, to compile the preview. However, the preview will only successfully compile if it is a numeric type (as seen in the error message).
In the example project provided, the error shown is valid because the first input is a Sample State and it's expecting a Vector, Matrix, or Boolean.