This plugin will export motion vectors from Lightwave in the format required by Re:vision FX’s ReelSmartMotionBlur plugin. It does this non-destructively during Lightwave’s normal render pass, and can save the vector pass out to a separate file sequence.
- Requires Lightwave 7.5 or newer (tested in 8.x and 9.x)
- Note that motion vectors are broken in Lightwave 9.0, but are fixed in Lightwave 9.2
- ScreamerNet rendering is now working correctly
Download – Intel 32-bit v1.1 Intel 64-bit v1.1
Update February 2009 – Unfortunately this plugin is no longer supported. I have sold my copy of Fusion and the RSMB plugin was tied to the Fusion dongle. I can no longer test changes to the plugin. This is probably fairly irrelevant given the latest happenings in the Lightwave community.
Interface:
| Parameter | Description |
| Max Pixel Move | The maximum distance in any direction an object could move in a given frame. For 16-bit and float modes 2048 should be suitable in 99% of cases, unless you are rendering very large images. |
| Bit Depth | Choose the output depth. 8-bit is not recommended, but if using 8-bit you should lower the “Max Pixel Move”. Something like 32 is a good start.
It’s recommended to use “float” mode where possible. |
| Image Format | Choose image format to save in. If using 16-bit or float modes, then ensure the output format will support the image depth. Also ensure that the output format has an Alpha channel as this is required by ReelSmart for correct blur. |
| Filename | Enter the filename of the output file. If a relative path is specified (i.e. without drive or absolute folder), then file will be saved relative to the current content directory.
Use the # character to specify where in the filename the 4-digit frame number should be substituted (if required). File extension will be appended automatically if omitted. |
NOTE: Currently saving to Sun 16bpc .rgb files causes a crash of Layout. I’m not sure of what this issue is. Other HDR formats such as .hdr or .exr export with no issues however.
Hi Richard,
There seems to be some changes in LW9.6 motion vectors render buffers that is causing your RSMBExport plugin to output motion vectors that is different from LW8.5.
Would you be able to make changes to it so that it exports the same as LW8.5. I am using the motion vectors exported from RSMBExport for retiming in Twixtor and this change in the output from LW9.6 is breaking the whole process.
How do I donate some beer money to you?
Let me know if you need a test scene to compare the difference.
Thanks.
Hi Richard!
Just wanted to say thanks alot for this very neat plugin! Works great with EXR-saver!
Cheers!
Hi Tajino,
Yes, I imagine that might be the case as the Lightwave renderer changed quite a lot between 8.5 and 9.6. Unfortunately there’s nothing I can do about this – the motion vector data is provided by the Lightwave renderer. My plugin just changes it to be usable by RSMB.
Best bet would be to go back to 8.5 to render out the motion vectors you need in this case.
Hi Richard,
It is the motion-y from LW that is inverted in 9.6. If you could do lw host version detect in your plugin, and do the inversion of motion-y during pixel value interpretation to RSMB normalized motion vector format, it should work correctly.
Anyway I have found other solution of outputing normalized RSMB motion vector by using NodeImagefilter by dpont.
Thanks.