MXS scene file Tooltip - MXS scene to render Info |
---|
Browse or enter manually the location of the scene file to be rendered. This is a required field for submission Important: Best practise is to ensure the scene file and all of its dependant files such as textures are on network storage accessible by the workers. |
outputImage Tooltip - full path and name of the image file. Info |
---|
Browse or manually enter the location of the output image file you wish to generate Important: Best practise is to ensure outputs are written to network storage accessible by the workers |
MXI output file Tooltip - MXI output file containing information about the rendering process. It allows for resuming previously rendered image. If not specified, the MSI will use the same name and path as the MXS scene Info |
---|
Browse or manually enter the location of the output MXI file you wish to generate Important: Best practise is to ensure outputs are written to network storage accessible by the workers |
script Tooltip - Load and run a given script Info |
---|
Browse or manually enter the required scripts Important: Best Practise is to ensure scripts are on network storage accessible by the workers |
prescript Tooltip - Load and run a given script Info |
---|
Browse or manually enter the required prescripts Important: Best Practise is to ensure scripts are on network storage accessible by the workers |
postscript Tooltip - Load and run a given script Info |
---|
Browse or manually enter the required postscripts Important: Best Practise is to ensure scripts are on network storage accessible by the workers |
bitmaps Tooltip - Set an alternative folder path for the bitmaps location. If "0", then will discard all the bitmaps Info |
---|
Browse or manually enter the location of the bitmaps file you wish to generate Important: Best practise is to ensure bitmaps are written to network storage accessible by the workers |
overridemat Tooltip - Override all materials in the scen using the material indicated in the path Info |
---|
Browse or manually enter the location of the textures you wish to replace Important: Best practise is to ensure textures are written to network storage accessible by the workers |
curdir Tooltip - Set the current directory of the OS. This could be useful for using relative paths for textures and other dependencies. Info |
---|
Browse or manually enter the location of the current directory |
dependencies Tooltip - Set an alternative folder path for the dependencies location. Info |
---|
Browse or manually enter the location of the required dependancies |
resume Tooltip - Continue a render from a previously saved MXI file. To resume a previously rendered images and update the MXI file, this flag must be added. Info |
---|
Browse or manually enter the location of the MXI file to be resumed |
renameoutput Tooltip - When this flag is used, Maxwell Render does not write the MXI file directly in the given output path; it write a temporary file and when the writing process finishes it renames it to the final path. Info |
---|
Tick box to rename MXI file upon completion |
Internal(Range) Sequence of frames to render, overriding the scene settings. The format is comma-separated frames and frame ranges. For example, 12,21-30,99-102 would render frame 12, frames 21-30, and frames 99-102. |