Tweet
An updated version of the Batch Renderer is currently available for download. This version was completely rewritten and has fixes as well as new features. The download page can be found in the V-Ray Tools and Scripts portion of the Download section. Here is the link to the download page.
http://asgvis.com/index.php?option=c...ileinfo&id=331
Since this version only works with the new V-Ray for Rhino 4 SR1, the other versions of the Batch Renderer are still available for download. Please make sure that you are downloading the updated version.
Below is the ReadMe file. Please read it thoroughly as it describes a number of aspects of the update.
*ReadMe*
V-Ray Batch Render _ Version 2
******************************
Requirements:
This Plugin requires Rhino 4 and V-Ray for Rhino 4 SR1. This plugin will not work with Rhino 3 and will not work with the initial release of V-Ray for Rhino 4.
Intro:
This plugin is meant to update the current Batch Renderer with some fixes as well as new features.
Commands:
visBatchCreate
visBatchAdd
visBatchRender
visBatchViewLog
Installation:
Drag and Drop the Rhino Plugin File on a running instance of Rhino. Make sure the plugin file is in a permanant location. A toolbar is included as well, which can be installed by running the Toolbar command and loading the toolbar file.
Usage:
There are 2 main components to using the new Batch Render; Creating or Setting up a batch render sequence, and rendering a batch render sequence.
::Creating a Sequence::
***********************
Creating a batch render sequence involves choosing files to render, choosing the views within each file to render, and setting up the options for those files or views. With the new Batch Renderer you will be able to set the image type and the save folder through the creation of the sequence. You do NOT need to take care of these details through the scene options. If you do they will be disregarded.
You will also be able to associate specific visopts with specific views. This will allow you to have specific camera settings, render output sizes, quality levels, and/or environments with each view. Once you have entered the option to add visopts to views a list will appear that you can pick from. From that list you can choose a view and then choose the visopt file. You do not have to assign a visopt for every single view. Any views that are left in the list will use the scene options for the rendering.
You can create a batch sequence that will render multiple files. You can add view from external files when initially creating the batch render sequence. In some cases, for users who have a lot of plugins in Rhino or where Rhino tends to load slowly, there may be some issues with adding views from external files. To bypass this issue, and as a general addition, you can add views from the current file to an existing sequence. This follows the same procedure as adding normal views, although two files with the same file name cannot be used.
::Rendering a Sequence::
************************
Rendering a sequence is fairly straight forward, and merely involves choosing which sequence to render. A dialog box will show the files and views to be rendered and you must confirm that sequence to begin rendering it. The sequence will close the current file, so make sure that it is saved before running the batch render sequence. Also, make sure that all of the files in the batch render sequence are saved with the correct view information.
While progressing through the batch render sequence, the Batch Renderer also creates a log of the events. This log will record whether scenes and views are succesfully loaded, the visopts that are associated with a given view and the success of retrieving that visopt, where each rendering is saved, and the time of each rendering. This log is meant to give you as much information can be retrieved from events that happen during the sequence.
Notes:
+ All of the files created for batch rendering are automatically saved within a specific batch render folder. In a typical install, this folder will be in [root_dir]:\Program Files\Rhinoceros 4.0\Plug-ins\VRayForRhino\BatchRenderFiles. You can move the files from this directory, but creating a batch render sequence and a render log file will always be saved in that directory.
+ Log files can be viewed by using the visBatchViewLog command. This will open up a specified log file in window notepad.
+ If you intend to work while rendering a batch render sequence, make sure that you have Low Thread Priority enable in all of your scenes and visopts. You will have to work in a second instance of Rhino.
+ If a file is currently not saved at all (i.e. does not have a location), then it will not be allowed to be added to a render sequence. It must be saved first. In the case of using the visBatchAdd command, it will not allow the command to be run, since the only views that can be added within that command are from the current scene.
+ If the current file does not have any saved views then it will not be allowed to be added to the render sequence. In the case of using the batch command, it will not allow the command to be run.
Known Issues:
+ In some cases, adding views from external files has caused issues with retrieving those files. This has typically been seen in situations where Rhino is slow to load due to plugins, startup scripts, or computer performance. If you are seeing this issue, which tend to express itself as a dialog box saying that the program is not responsive, then it is recommended to manually add the views by opening up the file and using the visBatchAdd command.
+ It has been reported that running the visBatchViewLog command was unsuccessful in a foreign language Vista system. If you are experiencing problems using the command you should be able to open a log file directly through Notepad or a text editor. To do this you may need to set the file types to All.
http://asgvis.com/index.php?option=c...ileinfo&id=331
Since this version only works with the new V-Ray for Rhino 4 SR1, the other versions of the Batch Renderer are still available for download. Please make sure that you are downloading the updated version.
Below is the ReadMe file. Please read it thoroughly as it describes a number of aspects of the update.
*ReadMe*
V-Ray Batch Render _ Version 2
******************************
Requirements:
This Plugin requires Rhino 4 and V-Ray for Rhino 4 SR1. This plugin will not work with Rhino 3 and will not work with the initial release of V-Ray for Rhino 4.
Intro:
This plugin is meant to update the current Batch Renderer with some fixes as well as new features.
Commands:
visBatchCreate
visBatchAdd
visBatchRender
visBatchViewLog
Installation:
Drag and Drop the Rhino Plugin File on a running instance of Rhino. Make sure the plugin file is in a permanant location. A toolbar is included as well, which can be installed by running the Toolbar command and loading the toolbar file.
Usage:
There are 2 main components to using the new Batch Render; Creating or Setting up a batch render sequence, and rendering a batch render sequence.
::Creating a Sequence::
***********************
Creating a batch render sequence involves choosing files to render, choosing the views within each file to render, and setting up the options for those files or views. With the new Batch Renderer you will be able to set the image type and the save folder through the creation of the sequence. You do NOT need to take care of these details through the scene options. If you do they will be disregarded.
You will also be able to associate specific visopts with specific views. This will allow you to have specific camera settings, render output sizes, quality levels, and/or environments with each view. Once you have entered the option to add visopts to views a list will appear that you can pick from. From that list you can choose a view and then choose the visopt file. You do not have to assign a visopt for every single view. Any views that are left in the list will use the scene options for the rendering.
You can create a batch sequence that will render multiple files. You can add view from external files when initially creating the batch render sequence. In some cases, for users who have a lot of plugins in Rhino or where Rhino tends to load slowly, there may be some issues with adding views from external files. To bypass this issue, and as a general addition, you can add views from the current file to an existing sequence. This follows the same procedure as adding normal views, although two files with the same file name cannot be used.
::Rendering a Sequence::
************************
Rendering a sequence is fairly straight forward, and merely involves choosing which sequence to render. A dialog box will show the files and views to be rendered and you must confirm that sequence to begin rendering it. The sequence will close the current file, so make sure that it is saved before running the batch render sequence. Also, make sure that all of the files in the batch render sequence are saved with the correct view information.
While progressing through the batch render sequence, the Batch Renderer also creates a log of the events. This log will record whether scenes and views are succesfully loaded, the visopts that are associated with a given view and the success of retrieving that visopt, where each rendering is saved, and the time of each rendering. This log is meant to give you as much information can be retrieved from events that happen during the sequence.
Notes:
+ All of the files created for batch rendering are automatically saved within a specific batch render folder. In a typical install, this folder will be in [root_dir]:\Program Files\Rhinoceros 4.0\Plug-ins\VRayForRhino\BatchRenderFiles. You can move the files from this directory, but creating a batch render sequence and a render log file will always be saved in that directory.
+ Log files can be viewed by using the visBatchViewLog command. This will open up a specified log file in window notepad.
+ If you intend to work while rendering a batch render sequence, make sure that you have Low Thread Priority enable in all of your scenes and visopts. You will have to work in a second instance of Rhino.
+ If a file is currently not saved at all (i.e. does not have a location), then it will not be allowed to be added to a render sequence. It must be saved first. In the case of using the visBatchAdd command, it will not allow the command to be run, since the only views that can be added within that command are from the current scene.
+ If the current file does not have any saved views then it will not be allowed to be added to the render sequence. In the case of using the batch command, it will not allow the command to be run.
Known Issues:
+ In some cases, adding views from external files has caused issues with retrieving those files. This has typically been seen in situations where Rhino is slow to load due to plugins, startup scripts, or computer performance. If you are seeing this issue, which tend to express itself as a dialog box saying that the program is not responsive, then it is recommended to manually add the views by opening up the file and using the visBatchAdd command.
+ It has been reported that running the visBatchViewLog command was unsuccessful in a foreign language Vista system. If you are experiencing problems using the command you should be able to open a log file directly through Notepad or a text editor. To do this you may need to set the file types to All.
