Search Issue Tracker
By Design
By Design in 2023.1.X
Votes
0
Found in
2021.3.12f1
2022.2.0b11
2023.1.0a14
Issue ID
UUM-22226
Regression
No
Some local and global shader keywords are wrongly reported
Reproduction steps:
1. Open user attached project “MissingShaderKeywords.zip”
2. Open Window > Analysis > Frame Debugger
3. Select Enable in the Debugger
4. Select Camera.Render > Drawing > Render.OpaqueGeometry > RenderForwardOpaque.Render > RenderForward.RenderLoopJob > Draw Mesh Cube
5. Observe Keywords
6. Enter Play mode
7. Observe Console
Expected result: “All keywords: DIRECTIONAL LIGHTPROBE_SH SHADOWS_SCREEN” written in the Console
Actual result: “All keywords: SOFTPARTICLES_ON|BILLBOARD_FACE_CAMERA_POS” written in the Console
Reproduced with: 2021.3.12f1, 2022.2.0b11, 2023.1.0a14
Could not test with: 2020.3.40f1 (due to script errors), 2022.1.20f1 (Frame debugger doesn’t show any important information)
Reproducible on: Windows 11
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
FrameDebugger is showing the final keywords that are used for rendering. These are composed from globally enabled shader keywords, shader keywords enabled on the material, and keyword that the engine enables automatically for rendering.
In the given example, there are no keywords enabled on the material and some keywords (SOFTPARTICLES_ON and BILLBOARD_FACE_CAMERA_POS) are enabled globally.
The keywords that the FrameDebugger shows are all setup internally by the engine.
Resolution Note (2023.1.X):
FrameDebugger is showing the final keywords that are used for rendering. These are composed from globally enabled shader keywords, shader keywords enabled on the material, and keyword that the engine enables automatically for rendering.
In the given example, there are no keywords enabled on the material and some keywords (SOFTPARTICLES_ON and BILLBOARD_FACE_CAMERA_POS) are enabled globally.
The keywords that the FrameDebugger shows are all setup internally by the engine.