Crash on ScriptableBatchRenderer::ApplyShaderPass when opening specific Project

6.7.X

Third Party Issue

Thank you for reporting a bug to Unity. Our investigation indicates the issue originates from a third-party asset, plugin, or service, rather than Unity itself. Because the problem lies outside our codebase, we're unable to address it directly. We will close this case as a third-party issue. We recommend contacting the vendor or maintainer for support. If you have evidence that the issue is within Unity, please share it and we will re-open the investigation. More info: Some of the shaders in your project failed to compile. You can find details in the logs, but many of the "lilToon" shaders seem to fail. ScriptableBatchRenderer::ApplyShaderPass() crashes later when shader parameters are applied to one of these failed shaders. From the logs: 1) -------- Shader Hidden/lilToonFurCutout -------- GLSL link error: error: vertex shader output `vs_TEXCOORD0' declared as type `vec3', but fragment shader input declared as type `vec4' error: fragment shader input `vs_POSITION_CS_NO_JITTER0' with explicit location has no matching output error: fragment shader input `vs_TEXCOORD6' with explicit location has no matching output error: vertex shader output `vs_TEXCOORD3' declared as type `uint', but fragment shader input declared as type `vec4' error: fragment shader input `vs_TEXCOORD4' with explicit location has no matching output 2) "Shader 'Hidden/lilToonRefractionBlur' uses 53 texture parameters, more than the 32 supported by the current graphics device." 3) "Note: Creation of internal variant of shader 'Hidden/lilToonFurTwoPass' failed. -------- Shader Hidden/lilToonMultiFur -------- GLSL link error: error: vertex shader output `vs_TEXCOORD0' declared as type `vec3', but fragment shader input declared as type `vec4' error: fragment shader input `vs_POSITION_CS_NO_JITTER0' with explicit location has no matching output error: fragment shader input `vs_TEXCOORD6' with explicit location has no matching output"