form•Z | Render Options | File

Owned by
ben (Unlicensed)
Last updated: 04 Dec, 2012 by
Mihai Iliuta (Unlicensed)
Version comment
4 min read

File Tab

These setting specify which files will be created upon initiating a Maxwell rendering, and where they will be stored.

When a Maxwell rendering is made, the form•Z project is translated into an MXS file. The resulting render may be stored as a standard bitmap image, as a high dynamic range Maxwell Image (MXI), or as both. There are three general ways to specify how and where these files will be saved: Automatic, Manual, and Image Only.

 

Output File Paths: Automatic

With Automatic filepaths, the plugin will automatically generate unique filenames and folders for your MXS, MXI, and Image files. using the automatic option ensures that you will never accidentally overwrite an important older file. Unique filenames, called the ‘scene name stem’, are generated as follows:

form•Z project name + scene name + view name (or the text  ‘no view’ if none is selected + a unique number to avoid naming collisions (incremented starting at 1).

The scene name stem is then appended with “.mxs”, “.mxi”, or the image file extension, as appropriate.  If there are any illegal file characters in the project, scene, or view names, they will not be included in the filename. For 100% filename compatibility when exchanging files between platforms or remote servers, you have the option to automatically replace all blank spaces in the filename with either dashes or underscores. See the Whitespace parameter in Project Settings.

  • With Project: All automatically created folders and Maxwell output files will be created within the folder containing your form•Z project.
  • Custom Location: All automatically created folders and Maxwell output files will be created in the location specified in this field.
  • MXI: An MXI will be saved. MXI is a high dynamic range format containing additional information such as Multilight settings. MXIs are unique in that their renderings can be stopped and resumed at any time, across multiple sessions. See Rendering in Maxwell. If disabled, the Image checkbox must be enabled.
  • Image: A bitmap image of the type and bit depth specified in Image Output (see Render Options: Image) will be saved. If disabled, the MXI checkbox must be enabled.

  • Folder per form•Z Project: A sub-folder will be created for each form•Z project, named as follows: form•Z project name + “Maxwell”

  • Folder per Maxwell Scene: A sub-folder will be created with the scene name stem, minus the unique number at the end. If Folder per form•Z Project is also checked, the Maxwell Scene folder will be created within that folder.
  • Create Embedded Textures Subfolder: When this option is selected, a folder for embedded textures which need to be saved to disk will be created inside the folder which receives the MXS. This can help to keep complex projects organized.

  • Filename Construction

    The timestamp option is recommended when doing network renderings; enabling this will avoid a situation where mxs files might otherwise be overwritten.

Output File Paths: Manual

The plugin will use the filenames and absolute filepaths you specify in the following fields for the MXS. MXI, and image outputs.

  • Create Embedded Textures Subfolder: When this option is selected, a folder for embedded textures which need to be saved to disk will be created inside the folder which receives the MXS. This can help to keep complex projects organized.

 

Output File Paths: Image Only

The easiest option. When making test rendering, you will not often not need the MXS or MXI, and having them accumulate will only clutter your project folder. With the Image Only option, the plugin saves the rendered image to the current project folder (or a custom folder) and avoids naming collisions automatically, so you’ll never overwrite an important rendering.

Image Only keeps all the MXS files out of your way, storing them in a temporary, invisible folder which is deleted upon quitting form•Z. MXI files are not saved. The unique image filename is generated as follows:

  • form•Z project name + scene name + view name (or the text  ‘no view’ if none is selected + a unique number to avoid naming collisions (incremented starting at 1) + the selected image file extension

If there are any illegal file characters in the project, scene, or view names, they will not be included in the filename. For 100% filename compatibility when exchanging files between platforms or remote servers, you have the option to automatically replace all blank spaces in the filename with either dashes or underscores. See the Whitespace parameter in Project Settings.

  • With Project: When enabled, the output image will be created within the folder containing your form•Z project.
  • Custom Location: When enabled, the output image will be created in the location specified in this field.