Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.3.8f1
2023.1.9f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47817
Regression
No
"Shader Standard" errors in Player when "Strict shader variant matching" is enabled
Reproduction steps:
1. Open the “SSVM_Stripped“ project
2. Open the “Sample” scene
3. Enable Development Build in Build Settings
4. Build And Run
5. Observe the bottom left of the Player
Expected result: No errors
Actual result: A Console appears with two “Shader Standard” errors
Reproduced in: 2022.3.8f1, 2023.1.9f1, 2023.2.0b7, 2023.3.0a3
Could not test in: 2021.3.30f1 (“Strict shader variant matching” setting not found)
Reproduced on: macOS 13.4.1 (Intel), Windows 10
Not reproduced on: No other environment tested
Full errors:
1. Shader Standard, subshader 0, pass 2, stage vertex: variant <no keywords> not found
2. Shader Standard, subshader 0, pass 2, stage fragment: variant <no keywords> not found
Notes:
1. Not reproduced in Play Mode
2. Errors are also thrown in non-Development Builds (in Player.log)
3. Not reproduced when “Strict shader variant matching” is disabled in Project Settings > Player > Other Settings > Shader Settings
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.