Search Issue Tracker
Fixed
Fixed in 2022.3.18f1, 2023.3.0b2
Votes
0
Found in
2022.2.22f1
2022.3.1f1
2023.1.0a25
2023.1.17f1
2023.3.0a10
Issue ID
UUM-54590
Regression
No
Editor log shows confusing variant info when "optimize mesh data" is enabled
Steps:
- Open attached project (ShaderKeywordTest.zip)
- Make a player build
- Open Editor.Log and observe the lines of Compiling shader "Test/ShaderKeywordTest" (see attached image EditorLog.png)
OR observe console for error:
ShaderVariantTool error #E08. Shader Test/ShaderKeywordTest has 6 variants after ScriptableStripping, but Internal Program Count is not having same number: 4.
- Make a player build again
- No more ShaderVariantTool error #E08. Observe Editor.Log you can also see 2 variants are being stripped after built-in stripping.
- (optional) Edit the Test2.shader and change keyword name to _FANCYB, make build again you will get the same behavior.
Reproducible:
- 2023.3.0a10_c9b099e3345e
- 2023.1.17f1.3067.9210
- 2023.1.0a25.2386
- 2022.2.22f1.112
Tested on Win DX11 editor
Original slack thread: [https://unity.slack.com/archives/CQVLWNFDF/p1698162913396909]
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2023.3.0b2):
Fix has landed in trunk - Unity 2023.3.0b2
Resolution Note (fix version 2022.3.18f1):
Fix landed in Unity 2022.3.18f1