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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment