You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VulkanReplay::FetchCountersKHR() creates a VkQueryPool for queueFamilyIndex == 0 but later it is used in VkCommandBuffer of different queue families not respecting Vulkan specification and causing issues in Intel GPUs with support for multiple queues(Lunar Lake and newer).
I can workaround it by using a environment variable(ANV_QUEUE_OVERRIDE=gc=1,g=0,c=0,v=0,b=0) that disables all queues but the main one(that supports VK_QUEUE_GRAPHICS_BIT | VK_QUEUE_COMPUTE_BIT | VK_QUEUE_TRANSFER_BIT) but would be nice to have renderdoc to following specification.
Steps to reproduce
renderdoccmd capture ... <application being analyze>
Again this is only reproduced in GPUs that supports multiple queues, for Intel on Linux that would be Lunar Lake(Ultra series 2) and Battlemage(Arc B). I can definitely help with testing.
Environment
RenderDoc version: v1.x branch from today / commit 4ac6b77
Operating System: Linux
Graphics API: Vulkan
HW: Intel Lunar Lake(Ultra series 2)
The text was updated successfully, but these errors were encountered:
I'll look into this but at this stage it won't be until the new year. The KHR counter queries were originally contributed by @djdeath so possibly he can look into it sooner? Looking at the original PR #1600 this was mentioned as a known issue but not addressed at the time.
Also note you should never use renderdoccmd. This is an undocumented internal tool only and not for users. You should launch your program for capture from the RenderDoc UI rather than doing that as an unnecessary extra step.
@djdeath I'm catching up after the holidays - I'll leave this with you for not but let me know if you're not able to get to it and I will try and resolve the issue.
Description of Bug
VulkanReplay::FetchCountersKHR() creates a VkQueryPool for queueFamilyIndex == 0 but later it is used in VkCommandBuffer of different queue families not respecting Vulkan specification and causing issues in Intel GPUs with support for multiple queues(Lunar Lake and newer).
I can workaround it by using a environment variable(
ANV_QUEUE_OVERRIDE=gc=1,g=0,c=0,v=0,b=0
) that disables all queues but the main one(that supports VK_QUEUE_GRAPHICS_BIT | VK_QUEUE_COMPUTE_BIT | VK_QUEUE_TRANSFER_BIT) but would be nice to have renderdoc to following specification.Steps to reproduce
renderdoccmd capture ... <application being analyze>
qrenderdoc <file captured above>
Again this is only reproduced in GPUs that supports multiple queues, for Intel on Linux that would be Lunar Lake(Ultra series 2) and Battlemage(Arc B). I can definitely help with testing.
Environment
The text was updated successfully, but these errors were encountered: