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

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

Top replies

Christian F over 1 year ago +3 suggested

Hey ByLaws, Thanks for another report, it's much appreciated :) This is unfortunately indeed broken on r36p0 up-to-and-including r39 (except for r38p2) -- there are multiple scenarios where we fail to...
Christian F over 1 year ago in reply to Christian F +3 verified

Hi again! On the r40/r41 point -- seems like on these drivers vkCmdBindVertexBuffers2EXT will incorrectly apply the dynamic stride to all previous draws using the same PSO. In other words redundant re...
ByLaws over 1 year ago in reply to Christian F +1 verified

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...