Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.19f1
6000.1.0a7
Issue ID
UUM-80037
Regression
No
Asset import fails when importing the Shader Graph "Production Ready Shaders" sample
How to reproduce:
1. Create a new empty URP project
2. Open the Package Manager (Window → Package Manager)
3. In the “In Project” tab, select Shader Graph
4. Navigate to the “Samples” tab
5. Import the “Production Ready Shaders” sample
6. In the Project window, navigate to “Assets/Samples/Shader Graph/17.0.3/Production Ready Shaders/Lit”
7. Observe the “URPLit” shader
Expected result: The asset is imported correctly, showing a blue icon
Actual result: The icon appears white and when selected, the Inspector shows that import errors were generated
Reproducible in: 6000.0.19f1
Not reproducible in: 2022.3.46f1
Could not test with: 2021.3.43f1 (“Production Ready Shaders” sample does not exist)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
* Not a regression as the “Production Ready Shaders” sample was recently introduced (6000.0.5f1)
* The import errors (displayed in the Inspector) can be printed in the Console (see internal notes)
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
In order to fix this in your project, follow these steps:
1. Under the Edit menu, select Project Settings.
2. Select the ShaderGraph tab on the left side.
3. Set the Shader Variant Limit to 2048 (or anything higher than 512)
4. Reimport the shader asset.
This procedure is explained in both the sample scene where the shader is on display and also in the sample's documentation. The only way to automatically fix this would be to change the user's Shader Variant Limit in their project automatically, and we don't want to do that as it would be too heavy-handed a change that the user may not want.