I'm dealing with the attached setup.
If you render frame 72 (and that's not the only one) with Redshift or Mantra you'll see one of the cubes is strongly motion blurred, unrealistically so. This happens because the copy_to_point node switches between two different sources of the cube to copy and some of the internal geometry "jumps" from one frame to the next even if it's not visible from the camera.
Somehow I thought that by assigning zero velocity to the points in the appropriate frames I wouldn't get any motion blur, but I still get it.
In Redshift it disappears if I turn Deformation Blur off, but then the desirable motion blur in other frames is also off. In Mantra it seems to show the problem no matter what I do.
Suggestions?
[SOLVED] Motion Blur caused by replacing one geometry with another
735 3 1- manu3d
- Member
- 39 posts
- Joined: Dec. 2018
- Offline
- cncverkstad
- Member
- 119 posts
- Joined: Aug. 2017
- Offline
- manu3d
- Member
- 39 posts
- Joined: Dec. 2018
- Offline
- manu3d
- Member
- 39 posts
- Joined: Dec. 2018
- Offline
Turns out the solution was in part enabling
- Redshift OBJ/Settings/Mesh Deformation Blur From Velocity Attribute
(notice this is an object-level redshift setting)
and in part having unique point IDs so that velocities can be calculated from the previous unique point ID if available or set to zero if not.
- Redshift OBJ/Settings/Mesh Deformation Blur From Velocity Attribute
(notice this is an object-level redshift setting)
and in part having unique point IDs so that velocities can be calculated from the previous unique point ID if available or set to zero if not.
-
- Quick Links