Search Issue Tracker

Fixed in 2022.2.X



Found in







Issue ID




"Shader not supported on this GPU" error is thrown when stripping a Shader that calls the UsePass command

Shader System


How to reproduce:
1. Open the user's attached "UsePassStripping" project
2. Build and Run the "SampleScene" Scene
3. Observe the Cubes in the Player

Expected result: Both Cubes are white
Actual result: The left-side Cube is pink. In the Player.logs can be seen, that "ERROR: Shader BugReport/ShaderUsePass shader is not supported on this GPU (none of subshaders/fallbacks are suitable)" is thrown

Reproducible with: 2019.4.35f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a3

  1. Resolution Note (fix version 2022.2):

    This seems to be working as intended.
    If a use pass fails to find the used shader pass then the entire sub-shader is intentionally removed.

    If you're trying to do a fallback mechanism, you should be using sub-shaders, not passes. All passes will end up running (in this case, the 1st one runs and sets the color to red then the 2nd one runs and overwrites that to white). You can get a similar effect to your example by moving each pass to a sub-shader (same for the use passes). When you do this, the first sub-shader will run, but when you strip the pass the 2nd sub-shader will run for both shaders.

    If you're attempting to use this to achieve some variant behavior, then we'd recommend using other solutions, such as preprocessor directives.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.