48
« on: 2013-10-24, 17:44:57 »
Of course it does. Nothing wrong with max there but the way you are understanding the issue.
Max per object motion blur is not anything close to motion blur but a trick to improve the look of the mb of a fast moving object.
From the max help doc:
"(Another option, object motion blur, is not meant to simulate a camera, but to improve the rendered appearance of fast-moving objects.)..."
"Object motion blur works by rendering multiple copies of the object in between frames and then rendering them together. It is not affected by camera movement.
Being said is not surprise it ended being part of any pass out of their old scanline renderer.
Now.. When you mention the motion vector pass i guess you mean the one that comes out of MR, right? Cos i can't remember max had one ( but is being a long time i use max scanline so maybe im wrong ). If you are talking about MR then it would simply be an error easy to fix by no using object mb at all.. There is just no point using that if your goal is to make your mb in post.. That's why you are outputting a vector motion pass in the first place.
So. Having that definition of object motion blur as a feature in corona render just doesn't makes sense too much. As captain obvious said you get all motion data ( well, not exactly * ) from your velocity pass and if you mix that with z depth in nuke you'll get a fairly acceptable mb ( vector mb what they call )
It would be more interesting and much more important as an addition in corona to implement EXR 2.0. Now that's something you can play with for your post mb!. And maybe p-ref data for experimenting with it though i'm not yet so familiar of how to use it.
Sorry for the long post guys :)