<p dir="ltr"> Hello,</p>
<p dir="ltr"> Does Blender allow exporting at arbitrary subframes? If not, that might be a problem. If so, then Stuart has me exploring the code, and I think that I could write the patch while doing so. Does that sound okay?</p>
<p dir="ltr"> God Bless,<br>
Gavin Howard</p>
<div class="gmail_quote">On Jun 9, 2013 6:34 AM, "Brecht Van Lommel" <<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We should support exporting at the exact shutter time. At the time I<br>
implemented motion blur evaluation at subframes was actually broken<br>
for shape keys and physics systems so I didn't use it, but that has<br>
been fixed since.<br>
<br>
However, exporting motion from the frame positions may be useful to<br>
keep as it may give more predictable results in some cases. When<br>
you're editing animations that's the only thing you actually see in<br>
animation playback, so the motion between those frames may contain<br>
some unexpected things that you don't want to render.<br>
<br>
I don't know how common that is, did not look at .blend files yet to<br>
see how different the results are, if it is an issue we should<br>
probably have an option (off by default) to only export motion from<br>
integer frame numbers and no subframes.<br>
<br>
On Sat, Jun 8, 2013 at 7:36 PM, Gavin Howard <<a href="mailto:gavin.d.howard@gmail.com">gavin.d.howard@gmail.com</a>> wrote:<br>
> Hello all,<br>
><br>
> I have a question about implementation. I have been told by<br>
> Brecht that currently, the Cycles addon exports three steps for motion<br>
> blur to the renderer: one at the previous frame, one at the current<br>
> frame, and one at the next frame.<br>
><br>
> Now, my memory may not be serving me well here, so I may have<br>
> gotten the details wrong. But if not, shouldn't the addon actually use<br>
> the shutter time to determine the first and third steps? For example,<br>
> shouldn't the addon export a step at the start of the shutter time,<br>
> one at the current frame, and one at the end of the shutter time?<br>
> Also, I think this type of reasoning should apply even when multi-step<br>
> (more than 3) motion blur is added. (Multi-step blur is needed for my<br>
> Deformation Motion Blur GSoC project, so I will add it over the<br>
> summer.)<br>
><br>
> In short, I think that the shutter time should be the goto for<br>
> exporting motion blur steps. If it is, then just ignore this. But if<br>
> it's not, should we change it? Anyway, that's my two cents.<br>
><br>
> God Bless,<br>
> Gavin Howard<br>
> _______________________________________________<br>
> Bf-cycles mailing list<br>
> <a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
_______________________________________________<br>
Bf-cycles mailing list<br>
<a href="mailto:Bf-cycles@blender.org">Bf-cycles@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-cycles" target="_blank">http://lists.blender.org/mailman/listinfo/bf-cycles</a><br>
</blockquote></div>