[Bug 94348] vkBindImageMemory doesn't take into account the offset when the image is used as a depth buffer

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 94348
           Summary: vkBindImageMemory doesn't take into account the offset
                    when the image is used as a depth buffer
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Vulkan/intel
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: bpeeluk at yahoo.co.uk
        QA Contact: intel-3d-bugs at lists.freedesktop.org

In cmd_buffer_emit_depth_stencil it is using image->depth_surface.offset but
only image->offset gets updated during vkBindImageMemory.

I bumped into this because I was lazily using a single allocation for both the
depth buffer and the color buffer in this project here:

https://github.com/bpeel/finvenkisto/tree/vulkan (the vulkan branch of it)

The depth buffer ends up overlapping with the color buffer and it makes some
funky effects. If I change cmd_buffer_emit_depth_stencil to use image->offset
instead then it works, but I don't know if that's the correct solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.
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/20160301/df4b291f/attachment.html>