Error GLSL link error: The number of vertex shader storage blocks

I am working on Unity 2019.4.8f1

 

Sorry for the very late reply to this, yes it did fix the issue. Not sure exactly but I think that there was also a very old texture that was somehow corrupted and was actually bringing this issue up. Thanks for the help!

 

I am experiencing the same issue in 2019.4.14f1 for the Standard Unlit Particle shader on an android development build.

Unfortunately it doesn't seem possible to search for a bug report by ID so I can't find the status of 1255008. If anyone has it, could they post a link to that bug report? Is there a plan to backport the fix? I can also file my own bug report, although it would presumably be better not to file known duplicate bugs.

The log output is this:

Code (CSharp):

1.  
2. E Unity   : -------- GLSL link error:  The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
3. E Unity   : (Filename: ./Runtime/GfxDevice/opengles/ApiGLES.cpp Line: 645)
4. E Unity   :
5. D Unity   : Note: Creation of internal variant of shader 'Particles/Standard Unlit' failed.
6.  

 

Thanks a lot for letting me know @richardkettlewell, the update is much appreciated. I have submitted a new bug report (Case 1292832) with a minimal reproducible project attached of the issue. The error is reported after adding a default particle system to a default project, so it's about a minimal as it gets in terms of reproducibility. Thanks a lot for the help!

 

Thanks! Yes I did so. Just for the record of this thread the device is a Samsung Galaxy A50 device running Android 9 (Kernel version 4.14.62-17426515)

 

For anyone else who finds this, I was referred to an existing canonical bug report for this issue which is here: https://issuetracker.unity3d.com/issues/android-a-glsl-error-occurs-when-using-the-unity-particle-system

Unfortunately that bug report states the issue has been resolved in 2020.1 whereas I can still reproduce the error as of 2020.1.17f1. I have commented and voted accordingly.

 

Oh I see, it's a different bug. Thanks a lot for the update Richard, that's good to know, and glad to hear there is a fix coming!

 

when i turn off the multithreaded rendering, i met the same error, the game is running well. my unity version is 2018.4.2f

 

We met the exact the same error but have no idea how to resolve it:

Code (CSharp):

1.  
2. 01-21 11:21:28.888 E/Unity   (30739): -------- GLSL link error:  The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
3. 01-21 11:21:28.888 E/Unity   (30739):
4. 01-21 11:21:28.888 E/Unity   (30739):
5. 01-21 11:21:28.888 E/Unity   (30739):
6. 01-21 11:21:28.888 E/Unity   (30739):  #0 0x7724277e98 (libunity.so) ? 0x0
7. 01-21 11:21:28.888 E/Unity   (30739):  #1 0x7724ae6fcc (libunity.so) ? 0x0
8. 01-21 11:21:28.888 E/Unity   (30739):  #2 0x77245bd6bc (libunity.so) ? 0x0
9. 01-21 11:21:28.888 E/Unity   (30739):  #3 0x77245c4afc (libunity.so) ? 0x0
10. 01-21 11:21:28.888 E/Unity   (30739):  #4 0x77245c317c (libunity.so) ? 0x0
11. 01-21 11:21:28.888 E/Unity   (30739):  #5 0x77245c2610 (libunity.so) ? 0x0
12. 01-21 11:21:28.888 E/Unity   (30739):  #6 0x7724742930 (libunity.so) ? 0x0
13. 01-21 11:21:28.888 E/Unity   (30739):  #7 0x7724250818 (libunity.so) ? 0x0
14. 01-21 11:21:28.888 E/Unity   (30739):  #8 0x7724268320 (libunity.so) ? 0x0
15. 01-21 11:21:28.888 E/Unity   (30739):  #9 0x772426e5d4 (libunity.so) ? 0x0
16. 01-21 11:21:28.888 E/Unity   (30739):  #10 0x77242659d0 (libunity.so) ? 0x0
17. 01-21 11:21:28.888 E/Unity   (30739):  #11 0x772444b498 (libunity.so) ? 0x0
18. 01-21 11:21:28.888 E/Unity   (30739):  #12 0x77c7887108 (libc.so) __pthread_start(void*) 0x40
19. 01-21 11:21:28.888 E/Unity   (30739):  #13 0x77c7826ae8 (libc.so) __start_thread 0x44
20. 01-21 11:21:28.888 E/Unity   (30739):
21. 01-21 11:21:28.888 E/Unity   (30739): (Filename:  Line: 645)
22. 01-21 11:21:28.888 E/Unity   (30739):
23.  

Is it mean I can't enable instance on these devices?

 

I think I found a problem. We 'Enable Mesh GPU Instancing' on ParticleSystem. Will it cause to use the DrawMeshIndirect and compute buffer?
So we should avoid using this feature on devices not support target 4.5?

 

I have similar error, but not sure if the same or not:

04/22 10:47:35.560 27954 28049 Error Unity -------- GLSL link error: The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
04/22 10:47:35.560 27954 28049 Error Unity
04/22 10:47:35.560 27954 28049 Error Unity
04/22 10:47:35.560 27954 28049 Error Unity
04/22 10:47:35.560 27954 28049 Error Unity (Filename: Line: 673)
04/22 10:47:35.560 27954 28049 Error Unity
04/22 10:47:35.700 27954 28049 Error Unity -------- GLSL link error: The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
04/22 10:47:35.700 27954 28049 Error Unity
04/22 10:47:35.700 27954 28049 Error Unity
04/22 10:47:35.700 27954 28049 Error Unity
04/22 10:47:35.700 27954 28049 Error Unity (Filename: Line: 673)
04/22 10:47:35.700 27954 28049 Error Unity

Using Unity 2019.4.21

 

Latest patch would be which one? 2019.4.25?

I have to wait for Easy Mobile Pro to update their asset because their is a conflict with Unity IAP, but if this is the case that's awesome.

 

And it's interesting, I got rid of all reference to Particles/Standard Unlit in my project but the error with the same debug log is still appearing... (still on version 2019.4.21)

 

Ok I just updated to latest Unity 2019.4.25 and the bug is still there.


How can I submit a bug report?

 

Thanks, bug report case 1332225

 

Hi @richardkettlewell. How's the progress for this case? I get similar GLSL link error: The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0) error at Unity 2020.3.8. I believe Unity 2020.3.9 still have the same issue.

 

I'm joining to this bug thread from another bug thread.
I'm receiving "GLSL link error: The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0)." error on my Android build.
My current Unity version is 2019.4.26f1.

 

@prawinb I see you are using UFE. I am having the same error and I am unable to find the error shader. Were you able to solve this issue?

 

Receiving same error I am using 2019.4.15f1.. did you find any solution yet?

 

I'm having this error on a Samsung Galaxy S20 5G fully updated (Android 11). The app works correctly in a Samsung A8 (Android 9) tho.
Using Unity 2020.3.12f1

 

As yuanzhuti mention this is happening for us when Multithreaded rendering is off on Mali GPU, we are using 2020.3.17f1
Is this still being investigated?

 

(Filename: Line: 683)
2021-09-23 15:13:01.278 18844-22212/? E/Unity: -------- GLSL link error: The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
i have this this type of error

 

App crash after launch. This what i get from logcat:

Background music keeps running until i remove the app from the recent opened apps.

 

i get the error

Code (CSharp):

1. 11-29 I/stereoWidening_frame(761): SwsParamsSetFloat volumeDb = -49.999889
2. 11-29 E/Unity(2271): -------- GLSL link error:  The number of vertex shader storage blocks (1) is greater than the maximum number allowed (0).
3. 11-29 E/Unity(2271):
4. 11-29 E/Unity(2271): (Filename:  Line: 645)
5. 11-29 E/Unity(2271): [ 11-29 14:47:40.113  2271: 2759 D/         ]
6. 11-29 E/Unity(2271): addLayerName, tid:2759
7. 11-29 I/stereoWidening_frame(761): SwsParamsSetFloat volumeDb = -49.999889

i find the cause of error 4 my problem（using Unity2019-3-7f1）。that is the scene use Reflection Probe (Type is Realtime)。I hide the
Reflection Probe’s GameObject (Realtime's Reflection Probe),It's Solved。maybe can help u。

 

Hi Richard, I noticed a few of our players run in this error too:

The game is using Unity 2019.4.20f1, shadermodel target 3.0 for custom shaders, built-in forward renderer, no post-processing and no Standard shaders, but Legacy and Custom surface shaders.

My question is, is this error triggered by using Legacy Particle shaders too? What option in a Particle System would cause this problem? I'm trying to narrow down the things I need to look into and right now I'm a bit lost where to start.

PS: Issue occurred on a "Google/jacuzzi/jacuzzi_cheets (Mali-G72, OpenGL ES 3.2)" for example.

 

Thank you for the reply.

If I understand you correctly, it could be a ParticleSystem that uses the Mesh render mode and has "Enable Mesh GPU Instancing" option turned on?

I just checked our project and we do have a few PS that use GPU Instancing, but custom shaders don't have any instancing implemented, unless it's magically substituted by Unity somehow.

I'll turn off "Enable Mesh GPU Instancing" in all Particle Systems. I'll see in the next update if this issue keeps popping up in Unity Cloud Diagnostics.

That could workaround it I assume?

 

These statement easily read on error line. told some solution......

 

Later in the thread folks realized it's caused by Unity's standard particle shaders - it's nothing to do with post-processing.
particle effect default shaders issue.

 

also getting this from ARFoundation 4.1.3 with 2020.2.2f1, opengles3.0.

 

Hey,
I had the same problem after adding a new particle effect. I just disabled "Custom Vertex Streams" in that specific Particle Effect -> Renderer Settings and now it is gone (opengles3.0)

 

Did "turn off "Enable Mesh GPU Instancing"" work?