Search Issue Tracker
Fixed in 2022.3.3f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a17
Votes
1
Found in
2022.2.20f1
2023.1.0b17
2023.2.0a14
Issue ID
UUM-35950
Regression
No
[Vulkan] VVL error-01913 for mismatched debug markers
Nes Vulkan Validation Layer error 01913 has exposed that sometimes we try recording a debug marker that should span multiple command buffers. That is OK for primary command buffers but not for secondary command buffers.
How to reproduce:
- Install latest Vulkan SDK: [https://www.lunarg.com/vulkan-sdk/]
- Launch any unity project and switch to Vulkan Graphics API in the editor (e.g. URP 3D Core)
- Launch unity editor again with `--force-vulkan-layers` CLI params
- Observe many VVL errors in console (VUID-vkCmdEndDebugUtilsLabelEXT-commandBuffer-01913)
Reproducible with: 2022.2.22f1, 2023.1, 2023.2.0a14
Not Reproducible with: 2020.3, 2021.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment