Thread group count is above the maximum allowed limit. Maximum allowed thread group count is 65535

I'm trying to port my game to HDRP. It is something like Motorm4x, and im trying to reach real HQ rendering. Hdrp's advantage is that metallic, occlusion and other important detail maps are baked in separate RGB channels which is big advantage for me as a developer. Sadly, i have error spam in console, saying stuff as stated in title. I tried several things and it turns i have to disable every gameobject to make these stupid errors dissapear. Could someone clarify what this error tries to tell me? It doesnt even make sense to me. If any unity dev is reading this, please help. Im struggling with this longer than a month.

 

I use HDRP 7.2.1, because was too afraid to use 7.1.8. I was getting constant mem leaks from procedural sky and with huge scene with tons of assets it really becomes a huge paint in the a*s.

I use unity 2019.3f (i think first LTS canditate?)

i have really old i3 CPU 3220. Not integrated, dual core. Nvidia GTX 960 4GB TI from ASUS. RAM mem is 12 gigs

 

I have pretty big shader graph for vehicle skin. Something around 7-8 textures per car (normals included)
Some shaders are also missing. If this problem is related to vertex count limit i can ensure you that is impossible in this case. I dont use any vertex displacement with geometry generation on car bodies.

 

Important thing to report! After further investigation, i found out this is caused by render textures in my scene

 

I still cannot fix the issue. When i enable Gameobject holding render texture, i get brutal memory leak. From 6 gigs of ram to 10 gigs according to task manager (using win 7)

 

I did the same, hoping to get it resolved, and that's it after I reinstalled the system.



Unity 2019.3.4 does not have a 65535 error, unity 2019.3.7 will have a 65535 error.

 

This issue has just popped up for (again).

I'm using 2019.3 w/ HDRP 7.2.0.

Not sure what started it, but it's not happening in my old scenes, but when I create new scenes, it floods the console. All I have to do is create a new scene, press play and it will flood with this message in the console.

 

Not sure how I'd tell what shader it's coming from as this is all I see in the console:

GPU is a 2080ti

 

Is there no other way to get information on what shader is causing this than to create a new project and one by one add shaders to it? That would take a lot of time.

 

Update: created a new project, added all my VFX graphs and shaders from my main project into it. Cannot reproduce the thread count error.

Update 2: pulled a fresh copy of the project from the repo in hopes that it might stop if I just reimport a new copy of the project. It still happens. Then I progressively deleted every folder under Assets/ and it still persists. At this point, I can just send you a zip of the project since it's less than 30kb. All that's left is my HDRP default settings, the HDRenderPipelineAsset and an empty scene file.

Update 3: continued messing around, eventually discovered that it seems to be the OpenVR single pass and single pass instanced rendering. I've been using single pass instanced for several months without problems until now. If I switch it to multipass, the errors don't show up in play mode, but I really need the performance gains from single pass. And just to re-iterate, this only happens in new scenes. The old scenes continue to operate just fine. In fact, I just tried duplicating an old scene and deleting most of it and that also works. So uhh... idk man...

 

Ok that was the end of a long day... new scenes do NOT work... I'd deleted cameras... adding a camera breaks it again.

I tried switching to the new XR Plugin Management system, but now I'm finding that I don't even have the option of using single pass rendering with the WMR plugin? This is insane... every hoop i jump through there is a new problem.

 

Hmmm... I tried it on another computer with a Vive headset and it didn't have the problem so I don't know how easy it will be to reproduce...

Is there a way I could just suppress the message from the console?

 

Hi Seb, so through some strange coincidence, I'm also experiencing this error, and I'm actually experiencing it using your Hydraulic Erosion example (small world I guess, eh?). This is my first foray into compute shaders, and I'm attempting to port my own erosion solver to the GPU in much the same way you did. While trying to reverse-engineer yours, I ran into this issue right off the bat, in the TerrainGeneration stage. Things work as expected with a Map Size setting <249, but anything above that generates a flat plane and an 'Thread group count is above the maximum allowed limit. Maximum allowed thread group count is 65535.' error.

Code (csharp):

1. //Thread group count is above the maximum allowed limit. Maximum allowed thread group count is 65535.
2. UnityEngine.ComputeShader:Dispatch(Int32, Int32, Int32, Int32)
3. HeightMapGenerator:GenerateHeightMapGPU(Int32) (at Assets/Hydraulic-Erosion/Assets/Scripts/HeightMapGenerator.cs:52)
4. HeightMapGenerator:GenerateHeightMap(Int32) (at Assets/Hydraulic-Erosion/Assets/Scripts/HeightMapGenerator.cs:17)
5. TerrainGenerator:GenerateHeightMap() (at Assets/Hydraulic-Erosion/Assets/Scripts/TerrainGenerator.cs:42)
6. MeshEditor:OnInspectorGUI() (at Assets/Hydraulic-Erosion/Assets/Editor/MeshEditor.cs:13)
7. UnityEngine.GUIUtility:ProcessEvent(Int32, In

I'm running 2019.3.8f1, and I have a 2080 Super GPU. Any thoughts?

 

I have the same issue, with 2019.3.3f1 and radeon rx 580series.
Any solution ?

 

Same issue here with a little demo scene using HDRP 7.2.1 @ 2019.3.6f1.
I get this error only on the Mac platform (not on Windows), i'm using metal.
I can share the build to you by PM @SebLagarde if you want but i can't find any button on this forum to do so from your profile.

If it can help, here are some detailed log from by build and the used and mentionned shader graph :

Mono path[0] = '/private/var/folders/yt/223vn28s3g343qrl6146x3tm0000gn/T/AppTranslocation/54F73375-1440-4559-9713-658A8E6488DB/d/BuildMac.app/Contents/Resources/Data/Managed'

Mono config path = '/private/var/folders/yt/223vn28s3g343qrl6146x3tm0000gn/T/AppTranslocation/54F73375-1440-4559-9713-658A8E6488DB/d/BuildMac.app/Contents/MonoBleedingEdge/etc'

Initialize engine version: 2019.3.6f1 (5c3fb0a11183)

[Subsystems] Discovering subsystems at path /private/var/folders/yt/223vn28s3g343qrl6146x3tm0000gn/T/AppTranslocation/54F73375-1440-4559-9713-658A8E6488DB/d/BuildMac.app/Contents/Resources/Data/UnitySubsystems

GfxDevice: creating device client; threaded=1

2020-04-29 14:19:48.371 my-game[568:15882] iMac preferred device: AMD Radeon Pro Vega 64 (high power)

2020-04-29 14:19:48.371 my-game[568:15882] Metal devices available: 1

2020-04-29 14:19:48.371 my-game[568:15882] 0: AMD Radeon Pro Vega 64 (high power)

2020-04-29 14:19:48.371 my-game[568:15882] Using device AMD Radeon Pro Vega 64 (high power)

Initializing Metal device caps: AMD Radeon Pro Vega 64

Begin MonoManager ReloadAssembly

- Completed reload, in  0.105 seconds

WARNING: Shader Unsupported: 'HDRP/Lit' - All passes removed

WARNING: Shader Did you use #pragma only_renderers and omit this platform?

WARNING: Shader Unsupported: 'Shader Graphs/Shader Master Props' - All passes removed

WARNING: Shader Did you use #pragma only_renderers and omit this platform?

UnloadTime: 0.559386 ms

Thread group count is above the maximum allowed limit. Maximum allowed thread group count is 65535.

UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal_Injected(ScriptableRenderContext&)

UnityEngine.Rendering.ScriptableRenderContext:Submit_Internal()

UnityEngine.Rendering.ScriptableRenderContext:Submit() (at /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/ScriptableRenderContext.cs:84)

UnityEngine.Rendering.HighDefinition.HDRenderPipeline:Render(ScriptableRenderContext, Camera[]) (at M:\gamedev\escape-game\Library\PackageCache\com.unity.render-pipelines.high-definition@7.2.1\Runtime\RenderPipeline\HDRenderPipeline.cs:1784)

UnityEngine.Rendering.RenderPipeline:InternalRender(ScriptableRenderContext, Camera[]) (at /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/RenderPipeline.cs:34)

UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal(RenderPipelineAsset, IntPtr) (at /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/RenderPipelineManager.cs:86)



[./Runtime/Shaders/ComputeShader.cpp line 920]

(Filename: /Users/builduser/buildslave/unity/build/Runtime/Export/RenderPipeline/ScriptableRenderContext.cs Line: 84)

 

I had the same problem. Using no SRP, just standard unity built in. I set threadGroupsX when dispatching to instanceCount / 64. In the Kernel, I used 64 as threadGroupSizeX. When I roughly hit the 3 million count of instances, the same error message appeared (65k limit etc...).

I fixed it by setting the threadGroupsX and size to 512, according to my pc specs. The error was gone. I tested until 5 million instances. Don't know if this is helping someone.

edit: Unity 2019.3.7f1, gforce 1050ti, windows 10

 

I am having a similar issue with the Thread Group Count Error popping up. However, I did notice something.
When I switch to my Scene view (in Play mode) and look from above at my scene, then the Error does occur when I pan out of my scene (Scene view is empty) and the Error disappears when I pan back to my scene (Scene view shows my GameObjects).
So it seems it has something to do with the Editor and what is visible in the Scene View. Perhaps this helps in clearing this error?

 

Any spr's right now just feel like not possible to use. Why in the hell is still no support for GPU instancing in shader graph? Alteast hide checkbox for instancing and dont try to pretend something works when it does not. Also, deprecating enlighten was a F***ing mistake. I could start another thread about this but how is it possible that GPU lightmapping randomly crashes due to memory errors, using CPU lightmapping is thousand times slower that enlighten. If you cant have one thing perfect, dont go into thousands of unfinished different things, leaving broken S*** behind, period.
I will NOT use this engine under ANY circumstance for Desktop. Even on empty scene with one terrain, realtime reflection probe lags the S*** out of my GTX 960 4GB. C# is not for games and everyone should know that. And a good tip for everyone to make bigger game. Try to think twice, before trying to achieve top notch graphics in this thing. For me, final product quality wins compared to clean UI in editor, which customers will give 0 F***s about.

 

Hi, I am having the same issue: Thread group count error spam in console. I have updated HDRP and ShaderGraph from 7.2.1 to 7.4.1 and Unity from 2019.3.0f6 to 2019.3.15f1 (before there were no related errors and was working all quite well)

Yeah, something similar it's happening to me, but with different tabs/action and not only with scene view tab. For instance:
- with a specific shadergraph shader file tab and scene/game view tab open;
- when moving in scene view and looking at sprites (currently using the default shader: Sprites/Default)
- when moving the cursor over this sprites in the hierarchy;
- camera with rendertexture on and scene view open;
- game and scene view active in the same time;
However if I create a new scene in the same project and i create a camera with a render texture it doesn't create any errors, BUT if you reload the scene will create just 2 errors. And I can't replicate the other errors.

So it might be a custom shader as suggested:

I will now test with the shader that give me the errors and will report here.

I have a GTX 1070 and I'm on windows 10.

 

I have tried to place some object with the shader that was causing errors and open the shadergraph tab of that, but no error this time, everything seems normal. I have also tried with camera and rendertexture.
However there is a strange rendering bug when switching from the scene that generate errors to the new scene: the light captured by the scene view camera remain the same in the new loaded scene.

 

Hi, I stumbled on this issue today and with me it is also because of a RenderTexture. If I use a 1024x1024 render texture: everything works perfectly fine. Bump it up to 2048x2048 and suddenly I get this error. Called in HDRenderPipeline.cs at line 1935.

Sporting version 8.2.0
Unity 2019.3.0f6
GPU is an NVIDIA GeForce GTX 1060
Probably doesn't matter, but using DX12

(And yes I know 2K render texture is expensive, but I was trying stuff out and just wanted to ping that the Render Texture is, in fact, an issue.)

 

Hi, For me this happened in my HDRP project when I used a tool to capture the high resolution screen shot from Main camera. For lower resolution of 1280 x 720 this was not a problem. But when I rendered the texture with high resolution of 6400 x 3600 then this error bumped and project started to freeze. But when I deleted the tool and the shaders of the tool, the error gone and the project is now again smooth.

Unity 2019.4.5f1
HDRP 7.3.1
CPU intel i7-7th Gen
Ram 16 GB
GPU NVIDIA GeForce GTX 1050 ti

 

Yet to this day? No wonder so many mem leaks were happening to me. This explains a lot....

 

So someone know how to deal with this ?

 

I'm the same as you . Have you made it yet?

 

Looks like I am in similar company, as I also experienced this while referencing the Hydraulic Erosion Example while learning about Compute Shaders.

I'm currently on Version 2019.3.12f1
I assume this fix would require me to update to a more recent version of Unity?

 

Sebastian Lague != Sébastien Lagarde

 

For those having the issue regarding Lague's compute shader tutorial, just change numthreads in HeightMap.compute from [numthreads(1,1,1)] to [numthreads(64,1,1)]
and the heightMap dispatch to heightMapComputeShader.Dispatch (0, Mathf.CeilToInt(map.Length/64f), 1, 1) in HeightMapGenerator

Source (answer on GH)

 

I got the same issue. HDRP 7.3.1 unity2019.4.0 . when playing, ram up to 28GB.my pc total ram is 32G.
RTX2080s

And when double click the error, it jump to

 

Hey guys, had the same error.
Popped on a VR project with Unity 2019.4.18 with HDRP 7.5.3.
Turned out that I had cranked up the resolution of my HTC Vive to 300% in my SteamVR app.
Lowering the resolution back to 150% fixed it.
Hope that helps anyone ... cheers!