Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2019.4
2019.4.1f1
2020.2
Issue ID
1265033
Regression
No
[URP] Error "Shader Unsupported" appears in Player.log when Cast Shadows is disabled in Pipeline Asset
How to reproduce:
1. Create a new URP project with 7.0.0 or higher version
2. In the Project window select Create -> Rendering -> Pipeline Asset
3. Select the created Pipeline Asset and open Inspector window
4. In the Lighting section disable Cast Shadows option for Main Light
5. Navigate to Edit -> Project Settings and select the Graphics category
6. In the Scriptable Render Pipeline Settings field add the Pipeline Asset you created earlier
7. Build and run the project
8. Observe the Player.log
Expected result: No errors in the Player.log
Actual result: Error "Shader Unsupported" appears in the Player.log
Reproducible with: 2019.4.5f1(7.0.0, 7.4.1), 2020.1.0f1(8.2.0), 2020.2.0a19(9.0.0-preview.14)
Cannot test with: 2018.4.25f1(no URP)
Note: Editor throws errors when building the project with URP 9.0.0-preview.35 package
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b9
Resolution Note (fix version 2020.1):
Fixed in 2020.1.10f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1