• State Accepted Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 137 subscribers
  • Views 4399 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VK_EXT_extended_dynamic_state bindVertexBuffers2EXT doesn't work correctly

ByLaws

Hi,

I was pleased to find that upon updating to the Android 14 preview, VK_EXT_dynamic_state + VK 1.3 were both supported. However when updating my application to take advantage of the new vertex binding call - 'bindVertexBuffers2EXT' - making use of both the dynamic stride and limit capabilities, I found that causes severe graphical corruption. Almost as if the GPU just skips some draws entirely and lets others through just fine. I can send an RDC capture or a demo app if necessary.

HW Info:

Mali-G78

Pixel 6 Pro

Driver 38.1.0

Parents
  • +1 in reply to Christian F

    My apologies here, I hope I didn't cause you to waste too much time as after looking further into it, it seems to have been a bit of a edge case on our side.

    Our backend was not properly handling the dynamic state 1 disabled (to workaround the stride bug) but dynamic state 2 enabled case thus causing the wrong number of dynamic states to be passed in at pipeline creation time leading to the issue. I'll try to be a bit more cautious reporting driver bugs next time :) 

    Thanks,

    Billy

Reply
  • +1 in reply to Christian F

    My apologies here, I hope I didn't cause you to waste too much time as after looking further into it, it seems to have been a bit of a edge case on our side.

    Our backend was not properly handling the dynamic state 1 disabled (to workaround the stride bug) but dynamic state 2 enabled case thus causing the wrong number of dynamic states to be passed in at pipeline creation time leading to the issue. I'll try to be a bit more cautious reporting driver bugs next time :) 

    Thanks,

    Billy

Children
  • 0 Arm Employee Badge in reply to ByLaws

    No worries at all! We really appreciate the reports; please do not hesitate to keep reaching out. :) We know how painful it can be to try to debug some of these things at API level -- with little-to-no insights into what happens inside the driver -- and so happy to try to help out wherever we can.