Domo_Digital
08-14-2008, 06:08 PM
This is from an old post I googled.
As of v6 the lm2mv shader isn't necessary. Or any mv shader for that matter.
"Turn on the Motion Render Channel. Click edit, and switch the type from .mv to .tif (or any normal file type). Then adjust the Motion Data under the framebuffer tab (render prefs) to a value that works best.
What it's doing is generating a 3d motion vector pass which isn't compatible with any apps yet (to my knowledge). Setting it to .tif forces it to save as a 2d file. .mt = 3d
tip: If you set the motion data to a really low number like 5 and then open up your script editor. Look in the log window after a region draw. It will tell you what value to set the motion data to."
This is the part Im having trouble with.
"Then adjust the Motion Data under the framebuffer tab (render prefs) to a value that works best."
I dont see an option for any values in the reder prefs. OR the framebuffer tab.
Has anyone used this and had success with it?
If so, can you explain it a little more thurouly?
As of v6 the lm2mv shader isn't necessary. Or any mv shader for that matter.
"Turn on the Motion Render Channel. Click edit, and switch the type from .mv to .tif (or any normal file type). Then adjust the Motion Data under the framebuffer tab (render prefs) to a value that works best.
What it's doing is generating a 3d motion vector pass which isn't compatible with any apps yet (to my knowledge). Setting it to .tif forces it to save as a 2d file. .mt = 3d
tip: If you set the motion data to a really low number like 5 and then open up your script editor. Look in the log window after a region draw. It will tell you what value to set the motion data to."
This is the part Im having trouble with.
"Then adjust the Motion Data under the framebuffer tab (render prefs) to a value that works best."
I dont see an option for any values in the reder prefs. OR the framebuffer tab.
Has anyone used this and had success with it?
If so, can you explain it a little more thurouly?
