Jump to content
  • Advertisement
Sign in to follow this  
HateWork

Vulkan Avoid command buffer re-recording when changing renderpass

This topic is 708 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

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.

Share this post


Link to post
Share on other sites
Advertisement
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!