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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
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.