Search Issue Tracker
Fixed
Fixed in 6000.0.0b14
Votes
0
Found in
6000.0.0b13
Issue ID
UUM-68615
Regression
No
"BatchDrawCommand" error is thrown when opening a scene
How to reproduce:
1. Open the “IN-72440_repro“ project
2. Open the “Lightsmapper“ scene
3. Observe the Console
Expected result: No errors are seen
Actual result: A BatchDrawCommand errors are seen
Reproducible with: 6000.0.0b13
Could not test with: 2021.3.37f1 (Entity Graphics is not available), 2022.3.24f1, 2023.2.18f1 (errors)
Fixed in: 6000.0.0b14
Reproducible on: Windows 10, Windows 11 (user’s device)
Not reproducible on: No other environment tested
Notes:
- Error: A BatchDrawCommand was submitted with an invalid Batch, Mesh, or Material ID. Shader pass: SHADOWCASTER, BatchDrawCommand index: 1, (index in range: 0), BatchDrawRange index: 1
This is not supported when rendering with a BatchRendererGroup (or Entities Graphics). MaterialID: 0 ("<null>"), MeshID: 1 ("mapzero-worldspawn#0-128_honey_2"), BatchID: 1.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
- Errors are thrown when the scene is reopened
- Workaround: Unloading and Loading the Subscenes allows to clear the errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment