Android Replay Failing with VK_GOOGLE_display_timing about gfxreconstruct HOT 4 OPEN

Can this be fixed by the replayer rewriting the contents of the extension data (therevy basically invalidating it)? Probably hard to reconstruct the original intent in any case.

from gfxreconstruct.

It's been a while since I looked at this, but I don't think that removing the extension on replay was a reliable solution. Having the extension enabled for capture could still record an image acquire order to the capture file that is different than the order that is produced by replay with the extension disabled.

from gfxreconstruct.

Sorry, you were asking about altering the extension data, not disabling the extension. I don't think we were able to get this to work, either, for the same reason. Something like setting desiredPresentTime to 0 on replay might produce a fifo order, but we may not have captured a fifo order. Improving swapchain support for replay is something that we should be looking at soon. Those improvements will hopefully address this issue.

from gfxreconstruct.

The change from #442 should prevent the OUT_OF_DATE error, without fully addressing the issue. It ensures that the image index specified to vkQueuePresentKHR is the same index that was acquired with vkAcquireNextImageKHR, but will still result in the wrong swapchain image being used for rendering when there is a mismatch between the indices acquired at capture and replay.

from gfxreconstruct.