Forums - Possible wrong value for maxUniformBufferRange in VkPhysicalDeviceLimits

2 posts / 0 new
or Register
Last post
Possible wrong value for maxUniformBufferRange in VkPhysicalDeviceLimits
andersrein87
Join Date: 23 May 21
Posts: 4
Posted: Sat, 2022-01-15 06:19
Top

I'm currently working on a native vulkan based application for the Oculus Quest platform. I've been originally developing on Oculus Quest 2 (Snapdragon XR2/Adreno 650), but when I tried the application on Oculus Quest 1 (Snapdragon 835/Adrendo 540)  it did not work. I tracked it down to the fact that I was using the maximum size of the uniform buffer size reported by VkPhysicalDeviceLimits::maxUniformBufferRange. Both devices report this as 65536, but when I use a uniform buffer with this size on Oculus Quest 1 all values seems to be interpreted as zero in the shader.

If I subtract 16 so that the buffer becomes 65520 it works. If I subtract 15 so that buffer becomes 65521 is does not work.

Is this a known bug in the driver?

  • Up0
  • Down0
Re: Possible wrong value for maxUniformBufferRange in...
DuBo
Join Date: 9 Dec 13
Posts: 72
Posted: Fri, 2022-02-11 07:32
Top

It looks interesting.
Do you have one sample code to show the issue  then we can verify it internally?

Thanks
Bob Du

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.