[Bug 98198] Crash when framebuffer is VK_NULL_HANDLE in VkCommandBufferInheritanceInfo

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=98198

--- Comment #3 from Konstantin <konst at openmailbox.org> ---
Maybe a bit offtopic: If a vulkan developer supposed to provide separate
secondary comamand buffers for each framebuffer, wouldn't it be an overkill to
generate 4x as many secondary command buffers(for the whole scene graph)?
I don't see how I can avoid the last restrictions (1 node = one command buffer)
because each model needs different buffers. Even if one uses one giant Buffor
for all vertices and ubos, each model nees different textures -> this means
different descriptor sets -> which means different command buffers. Even if you
update the same descriptor set, you still may have different pipelines for some
models.
I would have thought setting inheritance.framebuffer to VK_NULL_HANDLE would be
the most usual case, unless it's a fixed demo.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20161017/1bdae8bf/attachment.html>