Currently, gfxrecon-replay handles capture-time swapchain recreation - when the swapchain was recreated by the original application - but doesn't handle when the driver, at replay-time, starts returning VK_SUBOPTIMAL_KHR then VK_ERROR_OUT_OF_DATE_KHR.
While the driver only returns VK_SUBOPTIMAL_KHR, the issue can be ignored, but we recently started encountering devices that returns VK_ERROR_OUT_OF_DATE_KHR after a few frames of VK_SUBOPTIMAL_KHR, and even cases where Android sends destroyRequested, causing the application to stop.
Currently,
gfxrecon-replayhandles capture-time swapchain recreation - when the swapchain was recreated by the original application - but doesn't handle when the driver, at replay-time, starts returningVK_SUBOPTIMAL_KHRthenVK_ERROR_OUT_OF_DATE_KHR.While the driver only returns
VK_SUBOPTIMAL_KHR, the issue can be ignored, but we recently started encountering devices that returnsVK_ERROR_OUT_OF_DATE_KHRafter a few frames ofVK_SUBOPTIMAL_KHR, and even cases where Android sendsdestroyRequested, causing the application to stop.