--- title: "Continue a render with Resumable Rendering" canonical: "https://documentation.chaos.com/space/VMAYA/111740598/Continue%20a%20render%20with%20Resumable%20Rendering" format: markdown --- This page provides details on using V-Ray's Resumable Rendering feature. ## **Overview** --- ## **How it works** --- Resumable renders are possible with both **Bucket** and **Progressive** [Image Sampler](https://docs-chaos.atlassian.net/wiki/spaces/VMAYA/pages/111739176) types. With Bucket rendering, an additional *.vrimg* is written, storing the data of the completed buckets. When resuming the render, V-Ray reads the .vrimg file to determine which buckets still need to be rendered and continues to calculate what is left to complete the image. Another great ability of this feature is that the [Light Cache](https://docs-chaos.atlassian.net/wiki/spaces/THEORY/pages/116719627) data is saved within the partial image file so that the light cache does not need to be recalculated when the render resumes. When rendering with the Progressive image sampler, the state of the render is saved to an additional resumable *.vrprog* file, in a similar way to the .vrimg for Bucket rendering. Setting **Autosave Interval (min)** from the Image File Output rollout of the Render Settings [Common tab](https://docs-chaos.atlassian.net/wiki/spaces/VMAYA/pages/111739309) (to anything higher than 0) is useful so V-Ray can write out the .vrprog files during rendering, in case the process is unintentionally stopped. However, setting the **Autosave Interval (min)** value too low (below a couple of minutes for example) may slow the render process. If V-Ray finds a .vrprog file or a partially completed .vrimg file for the current frame, the rendering resumes from where it left off. If not, V-Ray starts a new render and a resumable file is then saved. > Macro (ui-text-box) > > Note that Distributed rendering is also compatible with Resumable rendering. ## **Workflow** --- ### Still Images - Go to Render Settings window > Common tab > Image File Output rollout and enable the **Resumable rendering** feature. If using the Progessive sampler, it is highly recommended to enable the **Autosave interval (min)** by setting it higher than 0. This saves partial files that can be used and helps prevent losing the render progress if Maya crashes and a .vrprog file hasn't been created/updated. When using the Bucket sampler, the Autosave interval (min) option isn't available. - Disable the **Don't save image (ignored for batch and Cloud) **option from Render Settings > Common tab > Image File Output. ![image](media://8fa17aa7-e1cb-4b41-a9f1-23bd170109ac) If you forget to disabled the option, you will receive an error when you start a resumable render. However, when rendering animations in batch mode, the **Don't save image (ignored for batch and Cloud)** option doesn't affect the resumable rendering. ![image](media://be0b39df-8f2c-4491-bfb7-0fb851168791) - Select an **Image Format** again in the Image File Output rollout. Any of the possible image outputs can be used for this step. - Start rendering your image. The passes calculate for a Progressive render or the buckets begin to drop for a Bucket render. The render can be stopped at any point in time and V-Ray will be able to use the .vrimg or .vrprog files to resume the render later. If you stop the render and want to resume it on another computer or location, make sure to copy the .vrimg or .vrprog file with the rest of your project so V-Ray can pick up where the render left off. It is not recommended to change Render Settings between stopping and resuming renders. The only settings that are acceptable to change in between stopping and resuming a render are [Progressive sampling parameters](https://docs-chaos.atlassian.net/wiki/spaces/VMAYA/pages/111739176) (Min. subdivs, Max. subdivs, Render time, Noise threshold). Changing settings like the output resolution and render elements causes an error and the render does not resume. ### **Animations** - Go to the** Render Settings** window > **Common** tab > **Image File Output** rollout and enable the **Resumable rendering** feature. - Set the frame range, i.e. **Start Frame** and **End Frame** from the **Render Settings** window > **Common** tab > **Animation** rollout. ![image](media://4b1bac53-e9f0-40eb-a487-02f1141deb7c) - Again in the **Image File Output** rollout, set the **Autosave interval (min) **if you want. Also if using the Progressive sampler, set the **Max. render time** to a preferable value depending on how much time you have and the level of quality you need. The **Max. render time** is located in the **Render Settings** window > **V-Ray** tab > **Animation** rollout. ![image](media://e3807363-c843-4a7c-9b22-9d09932d3411) - Start rendering. Just like with still images, make sure to copy the .vrimg or .vrprog file with the rest of your project when you stop a render and resume it on another computer or location. Thus, V-Ray can pick up where the render left off. It is not recommended to change Render Settings between stopping and resuming renders. The only settings that are acceptable to change in between stopping and resuming a render are Progressive sampling parameters (Min. subdivs, Max. subdivs, Render time, Noise threshold). Changing settings like the output resolution and render elements causes an error and the render does not resume. ## **Notes** --- - Light Cache data is saved in the resumable files, but the Irradiance Map (or any other GI map) is not, and will need to be recalculated when resuming the render. The rendering should still continue from where it was stopped, after the GI data is recalculated. - Enable the **Resumable Rendering** option before starting a new render, not only when resuming. - To start a new render, the *.vrimg/.vrprog* file should be deleted. - The scene should not be changed between stopping and resuming, except for the Progressive sampling options (**Min. subdivs**,** Max. subdivs**, **Max Render time**, **Noise threshold**). - When Test Resolution is enabled, Resumable Rendering is temporarily disabled.