Maxwell for Rhino :: Motion Blur
The Maxwell for Rhino plugin provides tools for accessing Maxwell Renders motion blur capabilities. There are two types of motion blur available in Maxwell: 1. camera: blur based on the difference in position of the camera from frame to frame 2. object: blur based on the difference in position of objects from frame to frame

Camera Motion Blur

As such, each camera created in the plugin has a switch for enabling blur:
When this is enabled, the plugin will write information for two camera positions into the.mxs file at export time. This implies that there are two positions. However, Rhino has no concept of this, so the plugin must provide some way for you to communicate your intention. It does so using the command Maxwell_SetCameraInitialPositionForMotionBlur. This command may be run by right-clicking the last button in the plugins Animation Control toolbar:
As the name of the command indicates, it records the current camera position for use later when the scene is rendered, it is the difference between this recorded position and the position of the camera at export-time which will be used by Maxwell to figure camera blur. For example, setting the cameras initial position with the left view, then rendering with the camera moved to that show on the right

Results in this image:

As the name of the command indicates, it records the current camera position for use later when the scene is rendered, it is the difference between this recorded position and the position of the camera at export-time which will be used by Maxwell to figure camera blur. When the plugin is in an animation loop (see the Animation tutorial), and it has motion blur enabled, all of this frame-to-frame position recording is done automatically.

Object Motion Blur

Similar to cameras, objects also need to have a previous position recorded so that Maxwell can calculate blur based on the difference between that position and the current position at export-time. This may be done by using the Maxwell_SetObjectsInitialPositionForMotionBlur command, which may be run by left-clicking the last button in the plugins Animation Control toolbar:
Additionally, the motion blur state of objects may be managed using the Maxwell Object Properties page, in the Rhino Object Properties window:
As shown in the window, there are two types of blur supported by the plugin: 1. Linear Motion Only: objects which use this must only be moved in a linear fashion 2. Full-Range Motion: objects which use this may be rotated or moved in arbitrary ways The reason for having two types is based in how Maxwell needs to get mesh-data for motion blur-enabled objects. Technically, a full copy of each mesh must be contained in the.mxs file, in addition to the regular mesh blur is figured by the difference between all points in the two meshes. As you may figure, this also means that there must be double the memory available, since there is essentially a copy of each mesh. When you use Linear Motion Only, the plugin does not store an entire extra mesh; instead it just stores one point and one vector. These are used at export time to write the two meshes into the.mxs, therefore reducing the amount of memory required by the plugin. If you cannot restrict an object to moving in a linear path, then you will need to use Full-Range Motion blur, and the plugin will indeed store an entire copy of the mesh for motion blur purposes. In addition to the toolbar and Object Properties methods of managing object motion blur, the plugin offers several other commands for working with objects and motion blur (Full-Range is referred to as Rotational here): Maxwell_DisableLinearBlurForAllObjects Maxwell_DisableRotationalBlurForAllObjects Maxwell_DisableSelectedObjectsLinearBlur Maxwell_DisableSelectedObjectsRotationalBlur Maxwell_EnableSelectedObjectsLinearBlur Maxwell_EnableSelectedObjectsRotationalBlur Maxwell_SelectRotationalBlurEnabledObjects Maxwell_SelectLinearBlurEnabledObjects

For an example, we will try using both types of object motion blur. The green box will be set to use linear blur, and the blue one full-range. Here are the two positions which will be rendered; the initial positions, and the positions at export-time:
This results in the following image:
As you can see, motion blur is not only for use in animation it is quite easy to use it manually for still shots as well. Even so, as with camera motion blur, initial position will be automatically inferred from the previous frame when rendering animations.

Maxwell Render for Cinema 4D
Version 2.5.1.4 Release Notes
This version of the plugin introduces support for Maxwell Fire, the ability to import Maxwell MXS files, and compatibility with Maxwell Render 2.5.1.

Changes

Compiled for compatibility with Maxwell Render 2.5.1. The Camera tag now always takes its FPS setting from the active Cinema render settings. Scene Object > Animation now uses Cinema render settings values for from, to, and step. The pixel aspect set in Cinema's render settings is now transferred into the Maxwell Render camera. Added the ability to read MXS files into Cinema (see Preferences > Import/Export > Maxwell MXS Files). Made auto-refresh in the material editor optional; see toggle button next to the Refresh Preview button. Added Maxwell Fire functionality, both for Scene rendering and in the plugin's material editor. Added new 'Render previews for converted materials' option to the Convert Cinema Materials command. Added new Maxwell Render 2.5-style SSS Preset material wizards. Added Advanced Wizard option to either modify the current material, or create a new one. Added new Shutter-based Blur option, which blurs objects and cameras based on FPS and camera shutter. Motion blur is now interpolated using the current frame plus and minus half the computed time span. Export filenames for animations now use the associated Cinema frame number, rather than starting at zero. Added 'Randomize all' function for Material ID colors (button located in main Material page). Added 'Pre-roll Timeline' option, which animates the document through all frames prior to the one being exported.

Fixes

Auto-refresh materials button was not working; it is now a button in R12, and a preference elsewhere. The positions of dynamic objects could still vary slightly frame-to-frame, even with Pre-roll Timeline enabled. Scene Object > output format and bpc setting dropdowns were functioning incorrectly. Cinema and 3rd-party shaders were not being asked to generate alpha-based textures correctly. Removing or disabling displacement in a Maxwell Material would produce a crash. New materials by the New Material command were not auto-refreshed. Material editor was not pre-populated with current material when opened from menu/toolbar. Deleting material components from the material editor, by the delete key, could crash Cinema. Maxwell Fire view not being updated when camera moved by Space Mouse; this may or may not be fixed now. UVs could be exported incorrectly for polygon selections which resided in an object hierarchy. A memory leak could occur when polygon geometry was lacking UV coordinates. Linear workflow was not being taken into account for viewport bitmaps under Cinema R12. Mismatches between Maxwell MXED and the plugin in AGS and SSS material wizards.