Creation of internal variant of shader 'Standard' failed

Unity Engine
1

Hey, I’m stripping a lot of stuff on my webgl build and since 2018.3, I have a lot of these messages showing up in the browser console:

Note: Creation of internal variant of shader 'Standard' failed. UnityLoader.js:4:9380
ERROR: 0:8: '' : No precision specified for (float) UnityLoader.js:4:9380
ERROR: 0:9: '' : No precision specified for (float) UnityLoader.js:4:9380
ERROR: 0:14: '' : No precision specified for (float) UnityLoader.js:4:9380
ERROR: 0:19: '' : No precision specified for (float)

I suppose these variants are empty and this is why i’m having all these messages. But isn’t there a way to avoid this ? And at the same time strip many variants ?

1 Like
2

I am having the exact same issue, got around 50 of them clogging my console.

Note: Creation of internal variant of shader 'Standard' failed. UnityLoader.js:4:9380
ERROR: 0:8: '' : No precision specified for (float) UnityLoader.js:4:9380
ERROR: 0:24: '' : No precision specified for (float) UnityLoader.js:4:9380
ERROR: 0:33: '' : No precision specified for (float)

Also have the following underneath it

Note: Creation of internal variant of shader 'Standard' failed. UnityLoader.js:4:9380
WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
UnityLoader.js:4:9380
WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
1 Like
3

I was having this same issue on my webGl Build.
I have solved it by changing “Graphics APIs” to webGL 1.0 (OpenGLES 2) as it was webGL 2.0 (OpenGLES 3) before.

Hope it helps

4

WebGL 1.0 is very limited and we mainly rely on WebGL 2.0 so we can’t disable it.

5

well if that’s the case, then u can use Both WebGL 1.0 and webgl 2.0

6

That’s what we do. Messages are showing up if you are running with WebGL 2.0 and it’s a problem.

7

thats there for me as well,
But everything is running good in my game
so it works that ways

8

Until you need to debug something, you open the console and BOOOOOOOOOOm ahah

1 Like
9

@kevin-masson_1 Have you updated from Unity 2018.1 to 2018.3 recently? Do you use AssetBundles in your project? I noticed this issue and it seems Unity renaming Standard Shader (Roughness Setup) to Autodesk Interactive may have had something to do with it. I had to reassign materials to my assets in the AssetBundle, delete the original AssetBundle, then recompile them in order to resolve this.

10

No I haven’t. But we don’t use Autodesk Interactive

11

I am seeing this in 2018.4.2 - bug Unity?

But it may be because I am loading older assetbundles

12

I’m surprised that no on from unity are responding on this. Anyone know how to solve this? or what causing it?

13

I wish I had an answer to this.

It seems like these are errors are not really a problem, but they are annoying.