This shows you the differences between two versions of the page.
|
blender:multiscene [2017/09/29 15:46] ranchadmin created |
blender:multiscene [2017/09/29 16:15] (current) ranchadmin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== The render of a multiscene project ====== | ====== The render of a multiscene project ====== | ||
| - | |||
| The way that we render Blender projects on the RANCH allows you to render still images on multiple scenes thank to only one **.blend** file. | The way that we render Blender projects on the RANCH allows you to render still images on multiple scenes thank to only one **.blend** file. | ||
| + | |||
| + | <WRAP center tip 80%> | ||
| + | This option can be implemented automatically thanks to our **RANCHecker add-on for Blender**. If you are using this process, the number of the frame to render that will be written in **Multiscene.txt** would be the one from the timeline at the moment you have created the archive file with the “//Pack your project//” button. | ||
| + | </WRAP> | ||
| + | |||
| Hence, you can load several large still images with only one **.vub** archive file. Each of these frames will be rendered on a specific servor. | Hence, you can load several large still images with only one **.vub** archive file. Each of these frames will be rendered on a specific servor. | ||
| Line 11: | Line 15: | ||
| The **.txt** file contains informations such as the following ones : | The **.txt** file contains informations such as the following ones : | ||
| //Scene name; resolution; frames to render; which frames have to be rendered or not// | //Scene name; resolution; frames to render; which frames have to be rendered or not// | ||
| - | |||
| - | This option can be implemented automatically thanks to our **RANCHecker add-on for Blender**. If you are using this process, the number of the frame to render that will be written in **Multiscene.txt** would be the one from the timeline at the moment you have created the archive file with the “//Pack your project//” button. | ||