Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The plugin’s Maxwell Fire window has been designed to provide this functionality in as simple a manner as possible. As with other plugin windows, it may be used as a Rhino dockbar if desired; see Scene Manger > Options > User Interface > Dockable Fire Window. At the top of the window you will find a toolbar which contains buttons used to control Maxwell Fire:  

CommandFunction
Enable PreviewEnables and disables the engine; if Cache Meshes is disabled, disabling invalidates the scene.
Refresh SceneRe-exports the scene, including changes to geometry, then re-starts the render engine.
Save Image to DiskSaves the Fire-rendered image to disk (the image is saved at the actual rendered resolution).
Enable in-viewport displayDisplays the rendered image directly in the viewport associated with the current camera.
Lock to Current CameraPrevents the plugin from dynamically changing the camera to that of the current viewport.

Additionally, the Fire window contains a context menu, which is available via right-click when Maxwell Fire is enabled. The options here are fairly self-explanatory, as to their respective purposes:

ParameterFunction
SLSets the sampling level at which the engine will stop rendering.
QualitySets the actual resolution at which to render; for display purposes, the image is fit to the size of the window.
ThreadsSets the number of threads which will be used by the engine (zero means auto-detect).

Using Maxwell Fire

Maxwell Fire functionality is tightly integrated with the plugin Export option Cache Meshes. When Fire is active, the plugin’s behavior is identical to what it would be when Cache Meshes is activated; the reason for this is that it is neither necessary nor desirable that the scene’s geometry be re-exported, unless it has actually been altered. As such exporting an MXS, or rendering in Maxwell Render, when Fire is active requires no unnecessary geometry-export.

...