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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.