Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.4.X
Votes
0
Found in
2017.2.0a1
2018.2.2f1
Issue ID
1070614
Regression
Yes
Frame Debugger does not display all additional Shader keywords when debugging a built player
How to reproduce:
1. Open the user-submitted project(ShaderKeywords)
2. Build the project as a Development Build and open it
3. Back in the Editor open the Frame Debugger window
4. Enable the Frame Debugger for the Editor, find Draw Mesh Cube event and check its keywords
5. Attach the Frame Debugger to the build, find the 'Draw Mesh' event for the Cube and check its keywords
Expected result: _METALLICGLOSSMAP keyword is among the keyword list
Actual result: _METALLICGLOSSMAP is missing from the keyword list
Reproducible with: 2017.2.3p2, 2018.4.9f1, 2018.1.9f2, 2018.2.6f1, 2018.3.0a10
Not reproducible with: 2017.1.5f1
Notes:
Additional keywords are still listed if using Debug.LogError to list the keywords in the player
Different versions of Unity may produce different keyword results when debugging the build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Buttons in the Overlay Menu in the Scene View are all gray even if they're activated when Game View is maximized and minimized
- NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
- Editor crashes on PrepareSpriteTilingData when exiting Play mode
Add comment