Troubleshooting

intermediate troubleshooting

Shader Control · Troubleshooting & FAQ

Troubleshooting

This page covers the most common issues users encounter with Shader Control and how to resolve them.

Build View shows no data

Symptom	The Build View tab is empty with no shaders listed.
Cause	No build has been performed since Shader Control was installed.
Solution	Click Quick Build in the Build View tab. Wait for the quick build to complete (it collects shader data without full compilation). The Build View will populate with all shaders and their keywords.

Visual artifacts after disabling keywords

Symptom	Materials display incorrectly (wrong colors, missing features) after disabling a keyword.
Cause	A keyword was disabled that is required by one or more materials in the scene.
Solution	Open Shader Control and navigate to the modified shader in Project View. Click Restore to revert the shader to its backup copy. Use List Materials to identify which materials depend on the keyword before disabling it again.

Keyword limit exceeded (256)

Symptom	Unity console shows warnings about exceeding the global keyword limit.
Cause	Too many unique shader keywords are enabled across all project shaders.
Solution	Open the Project View and click Scan Project. Sort shaders by keyword count to find the biggest contributors. Disable keywords you do not use and click Save. Use Clean All Materials to remove stale keyword references from materials.

Build size not reduced

Symptom	After disabling keywords, the build size has not decreased noticeably.
Cause	Changes in Project View only affect shaders with source code. Internal Unity shaders require Build View exclusions.
Solution	Switch to Build View and uncheck keywords on internal/hidden shaders. Use the Advanced button to specify exact variant combinations for large shaders. Rebuild and compare the build output size.

Still need help?

Visit the Kronnect Support to post your question. Our team will get back to you shortly.

Was this page helpful? |