Page 4 of 4
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Sun Oct 05, 2014 7:20 pm
by prodviz
One reason for including motion blur over multiple frames is to create motion trails, from car headlights etc.
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Sun Oct 05, 2014 8:04 pm
by prodviz
Yeah. really need that extra control for length of blur.
Here's a quick test (light following curve path) and I'd like to be able to extend the length of the blur as we can in Standalone.
There seems to be an error cutting in to the motion blur too.
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Sun Oct 05, 2014 8:33 pm
by JimStar
TBFX wrote:Yes exactly. If you only have 2 frames of animation you only get one frame of motion blur, so you effectively have a 1 frame usable shot. So if I want a shot that is 2 frames long I need to animate 3 frames, which is exactly what I mentioned above. It is always up to the user/animator to know how many pre/post frames they need over and above the length of the shot to ensure they have correct motion blur on the first and last frames of the shot. (pre frames may be needed if the shutter is centered or before the frame or is greater than 360 degrees)
If you currently take the 120 frame animation scene I uploaded earlier you will not get any MB when rendering frame 120. To get that I would need to extend the animation an extra frame (or half frame, or 10 frames depending on how much blur was specified and where it was centered)
But all I really want is internal MB that works over up to one frame that can be centered, you asked the question about having blur over more than one frame and all I said was I don't see any reason not to allow it, and I still don't, even if I will probably never use it I try not to assume nobody would. It was just an opinion.
T.
The main difference is you have
no render-reject error in your 120 frames sequence, you just get 119 motion-blurred frames. Which is absolutely logical, as in the case of motion blur enabled - the semantics of "frame" changes from "point in time" to "continuous time-frame" which means you have only ONE "
continuous time-frame" between your given
two points in time animation. This case does not need to throw any "reject-render" errors, as it is "up to user" to know about that. Moreover, I'll just cut the last frame in next versions to not get silly questions "why is it not motion-blurred?".
In "many frames motion blur" - there will be render-reject error generated right after starting the render. Otherwise - N of first and N of last frames will just get all different and all incorrect results (not just "one extra non motion-blurred frame").
If you don't see here any difference - it's better for me. As I'm just going to add this "reject-render" error together with "few frames MB" starting from next version...
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Mon Oct 06, 2014 9:17 am
by prodviz
Here are 2 examples from Standalone.
Standard keyframed light:
Light attached to curve.
By adjusting the setting between the Shutter Interval and Frame, we can elongate the blur without errors:
It would be cool, if we could have all of the settings from Standalone.
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Mon Oct 06, 2014 1:47 pm
by abstractmedia
Awesome! Thanks JimStar!
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [CURRENT]
Posted: Tue Oct 07, 2014 10:14 pm
by fellowla
Thank you Jimstar for this new release!
So I was re rendering some shots i'm working on with the new motion blur (witch is awesome) and i notice some kind of exposure difference between the 2.04 and the 2.1 version of the plugin. I could reproduce that just with a sphere, one light and one env. (see image)
For now I can color correct in comp to match my old render but I was wondering if it was expected or maybe something i'm missing
?
Ben
Re: OctaneRender® for Maya® 2.10 - 5.0 Win [OBSOLETE]
Posted: Thu Oct 09, 2014 1:26 am
by JimStar