Search Issue Tracker
In Progress
Fix In Review for 6000.0.63f1, 6000.4.0a5
Fixed in 6000.2.12f1, 6000.3.0b10, 6000.5.0a1
Votes
46
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
6000.5.0a1
Issue ID
UUM-122367
Regression
No
False Warning "BatchRendererGroups currently don't support override shaders" is spammed in Play mode when using H-Trace WSGI with BatchRenderGroups
How to reproduce:
1. Open the attached “IN-119948” project
2. Open the “OutdoorsScene”
3. Enter Play mode
4. Observe the result
Expected result: No warnings appear in the Console window
Actual result: “BatchRendererGroups currently don't support override Shaders.” is spammed in the Console window
Reproducible with: 6000.0.8f1 (90da52e174c9), 6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a3
Could not test with: 6000.0.7f1 (7dd95c051e11) (could not solve HTraceWSGI issues from downgrading)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- If warning messages are disabled in the ProjectSettings (ProjectSettings > Player > Other Settings), the Player.log will fill up to 1GB+ and frame rate will be affected
- H-trace is simply used to demonstrate the underlying issue which is the false warning since the override shader usage in the project does not use BRG / GRD
Other warnings also appear upon opening the project such as
- “Shader warning in 'Voxelization': 'Load': implicit truncation of vector type at kernel GeneratePositionPyramid2 at C:/…/Downloads/IN-119948_OverrideShaderLogSpamBug/Voxelization.compute(13538) (on d3d11)”
- “Shader warning in 'HDebug': 'Load': implicit truncation of vector type at kernel Debug at HDebug.compute(91) (on d3d11)”
- “Shader warning in 'HDebug': implicit truncation of vector type at kernel Debug at HDebug.compute(34) (on d3d11)”
- “Shader warning in 'HTracingScreenSpace': use of potentially uninitialized variable (RadianceValidation) at kernel ScreenSpaceTracing at HTracingScreenSpace.compute(111) (on d3d11)”
- “Shader warning in 'HTemporalReprojection': 'Load': implicit truncation of vector type at kernel HistoryIndirectionScroll at HTemporalReprojection.compute(250) (on d3d11)”
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Specular highlight appears in fully shadowed areas when HDRP Shadow Color is tinted
- [Ubuntu] VFX Graph Enum Value menu stretches across screen when entered long Enum Value
- Unclear warning message in Rendering Debugger about the Play mode Debugger Overlay
- [Android][iOS] Particles are not affected by External Forces when loaded from AssetBundles with Strip Engine Code enabled
- Rendering Debugger "STP" and "Reflection Probe Atlas" overlays don't change size when changing the "Map Size"
mgeorgedeveloper
Oct 18, 2025 07:59
It's important to note that this is not a 3rd-party asset store package issue - I'm simply using H-trace to demonstrate the underlying issue. The real issue is that the warning is a false alarm, since the override shader usage in the repro project does not use BRG / GRD in the first place. This problem has been confirmed by oprat73 in the thread I linked above.
mgeorgedeveloper
Oct 16, 2025 13:58
Since some of the final details of my original report has been lost, I will link here to the main discussion that contains the most accurate information: https://discussions.unity.com/t/infinite-warning-spamming-batchrenderergroups-currently-dont-support-override-shaders/1681271