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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Add comment