Search Issue Tracker
Won't Fix
Votes
4
Found in
2020.3.30f1
Issue ID
UUM-15744
Regression
No
[DOTS 0.5] Hybrid HDRP after build causes " Hybrid Renderer using error shader for batch with an erroneous material"
Steps to reproduce:
1. Open HybridHDRPSamples
2. Make a build through BuildConfiguration -> HybridHDRPSamplesBuildSettings
3. Go to "Lightmaps" scene (any other scene should be fine too)
4. Observe the warning spam and disappearing entities with the following warning: "Hybrid Renderer skipping a batch due to no valid material."
5. Enable/disable the subscene and enter playmode. Entities turn pink with this now: "WARNING: Hybrid Renderer using error shader for batch with an erroneous material: DefaultHDMaterial_Lightmapped__DIRLIGHTMAP (UnityEngine.Material)"
Expected result: Hybrid HDRP after build should not cause " Hybrid Renderer using error shader for batch with an erroneous material" and entities should not turn pink
Comments (4)
-
IliqNikushev
Mar 14, 2023 19:27
Same, turned out i had the Shader's Precision set to HALF not SINGLE
-
MeepMeep33
Aug 13, 2022 22:30
Getting this with Shader Graph/Unlit material, URP 12.1.7, Hybrid render 0.51.1
-
BigRookGames
Apr 08, 2022 20:47
Also getting this in Entities 0.17.0-preview.41 HDRP
-
colin_young
Mar 26, 2022 14:56
I am experiencing the same error with URP.
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
We were not able to reproduce this issue. Please try with the latest version and re-open if this is still happening.