Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.18f1
2023.2.7f1
2023.3.0b4
Issue ID
UUM-61107
Regression
No
Shader error in Builds when changing Keyword names in Shadergraph after switching on Strict shader variant matching
Reproduction steps
1. Open the attached project “ReproProject”
2. Ensure “Strict shader variant matching” is enabled at (menu: Edit > Project Settings > Player > Other Settings > Shader Settings)
3. Open “Assets/StripOnlyTest.shadergraph”, In the ShadeGraph Window, change the keyword (e.g. ColorMOde to ColorMOdeVH) and save the asset
4. Build the Project
5. Observe the app screen
Expected result: A black cube is displayed
Actual result: Either a cube is not rendered at all, or it is rendered with the pink visual artifact with some debug shader errors “Shader Shader Graphs/StripOnlyTest, subshader 0, pass 3, stage vertex: variant <no keywords> not found.”
Reproducible with: 2022.3.18f1, 2023.2.7f1, 2023.3.0b4
Couldn’t test with: 2021.3.34f1 (There is no Strict shader variant matching option)
Reproducible on: macOS (Intel) 14.2.1, Windows 10 (10.0.19045) 64bit (by user)
Note: Reproducible on Android devices
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
After much internal deliberation and investigation, we have decided not to fix this issue, since the fix would break a lot of existing projects.
As a compromise, a custom fix has been provided to the customer. We will properly address this issue in future versions of the engine.