[Mesa-dev] [Bug 110970] [RADV] texelFetch not working when multiple texel buffer inputs are bound

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jun 22 14:40:48 UTC 2019


            Bug ID: 110970
           Summary: [RADV] texelFetch not working when multiple texel
                    buffer inputs are bound
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Vulkan/radeon
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: kd-117 at hotmail.com
        QA Contact: mesa-dev at lists.freedesktop.org

Created attachment 144613
  --> https://bugs.freedesktop.org/attachment.cgi?id=144613&action=edit
Renderdoc trace of affected frame

I've encountered a curious situation using RADV regarding texel buffer access
in vertex shaders. I have 3 buffers mapped to texel buffer inputs and I cannot
properly access both at the same time. Curiously, if one buffer object is
viewed in more than one buffer view, everything is ok. If I comment out all
access to one of the loads in renderdoc the fetches seem to work fine as long
as the other is not referenced in the shader. I have attached a renderdoc trace
showing this behaviour. The renderdoc eventID of interest is no 97 which is
supposed to render a cube.

This issue has been confirmed by at least one other RADV user with an RX570.
Changing the driver to amdvlk makes the issue go away. Hopefully I merley
overlooked something but khronos' validation layer gives no errors or warnings.

Application: RPCS3 emulator
Mesa version: Mesa 19.2.0-devel (git-21dd881 2019-06-20 bionic-oibaf-ppa)
RADV version: 'AMD RADV POLARIS10 (LLVM 8.0.0)' running on driver 19.1.99

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190622/3b1dab0b/attachment.html>

More information about the mesa-dev mailing list