Motion Blur
The calculation of Motion Blur can be activated from the Redshift Render Settings. There you will also find the global Motion Blur settings. Using the Redshift Object tag you can deactivate or override these global settings for individual objects if needed
Activate this option to override the global Motion Blur settings, that are found in the Redshift Render Settings. To use Motion Blur, it always has to be activated in the Render Settings.
There are several modes available to calculate Motion Blur:
- Global Setting: Uses the Motion Blur settings from the Redshift Render Settings.
- Disabled: No Motion Blur is calculated for this object or object group
- Transformation: Only animated scales, translations and rotations are taken into account when calculating Motion Blur.
- Transformation and Deformation: In addition to animated scaling, translations and rotations, deformations of the geometry are also taken into account in the calculation of the Motion Blur.
Even the movements of a camera can already create motion blur, even if all objects are stationary. You will find special settings for this directly on the Redshift camera.
You can access this setting if you are using Transformation and Deformation as Motion Blur mode. Defomration Steps are the number of linear steps that Redshift will use to represent the trajectory of moving vertices on deforming objects. More steps means the trajectories will be more accurate and the motion blur will look smoother for deformed objects, but more memory will also be used.
These are the available options:
- Global Setting: The Deformation Steps defined in the Redshift Render Settings are used.
- 2,3,5,9,17: Choose the number of caclucation steps.
Calculating Motion Blur for Pyro simulatios is a bit different as they are stored frame by frame rather than, for example, an object animated via keyframes where the speed and motion curves can be accessed at any time. The solution for this is recording speed information to a velocity grid which can be included in a VDB file. Either separate XYZ grids with float scalar values or a single velocity grid with float vector values is required.
Activate this option to enable motion blur calculation for Pyro simulations.
Enter the names of the three appropriate velocity channels that include the x, y, and z components here. If you only have a single 3D velocity channel with float vector data you can add it all by itself to the X field and Redshift will handle the rest. When using a Pyro simulation, this would be the name velocity, that can be entered for X.
This is a multiplier for the velocity grids to increase or decrease the motion blur intensity of a volume. Depending on the values in the velocity grid, this value may have to be increased dramatically before motion blur becomes visible.
This setting describes, how the velocities should be interpreted. The default setting Frames is suitable in most cases, unless the simulation was saved in a third-party program that uses a different Unit. In that case, you can switch to Seconds.
The Frames (Legacy) Unit only establishes compatibility with the behavior of older versions of Redshift and should therefore not be used for new projects.
