Avoid command buffer re-recording when changing renderpass

Started by
-1 comments, last by HateWork 7 years, 6 months ago

Hello guys,

I know that in Vulkan, a renderpass is responsible for shaping a frame's rendering flow. Whenever we change a renderpass we need to recreate framebuffers, pipeline state objects, (re-record) secondary command buffers, etc...

Is there a method for not having to re-record secondary command buffers when changing a renderpass? It seems unpractical to record a secondary command buffer (which is supposed to be a long life object) just to have it invalidated after a renderpass recreation which forces us to re-record the same commands for the new renderpass.

Thank you in advance.

This topic is closed to new replies.

Advertisement