OTOY Forums

aoktar wrote:

james_conkle wrote:Interesting- with those settings the final render does appear correct but scrubbing the timeline and looking at the Live Viewer the motion blur is still incorrect. Thanks for the support on this everyone.

scrubbing can give correct or nearest look if you do it frame-by-frame. Also restarting the render on LV that will give correct look. Probably you didn't read motion blur section notes from c4d manual. Wrong results happen if you randomly jump between frames because it works like caching the frames

I did scrub frame by frame which can still result in improper display (and other weird glitches like objects disappearing), only when restarting the the Live View does it display correctly. I did read the motion blur section notes from the c4d manual. I'm assuming you mean this section on that topic:

"M.BLUR CACHES (FRAMES)

This feature determines how many frames will be cached when moving back and forth in Live Viewer. Because LV can only know the data in existing frames. Therefore, you can store the motion data in LV by entering the frame number to be cached in this field."

I don't see any mention of scrubbing, restarting the live viewer or that one would need to submit an "actual render" to get correct results.

James, I will review the documentation regarding scrubbing in the Live Viewer and if you're correct (you may be) we will amend it.

I'm also having problems with this. I have a 120frames camera animation, and all frames are rendered properly except frame 1, 60,61 and 120. The foreground object attached to the camera completely goes crazy with m.blur.

@Prodigiosovolcan - Do you have Octane tags on everything? If so the objects that are giving you trouble might need to be put into connect objects and then put an octane tag on those connect objects.

I have experienced weird motion blur at the start and end of sequences because keyframes start and end there but it's weird to see that happen in the middle of your sequence. Maybe extend your cameras motion from frame -1 to 121 or more.

Sorry mate, I didn't get to answer you. My bad!

I actually found out as you previously said in 2020, that LV has some problems showing this properly, but then I realized it rendered fine (altough some random frames where completely blurred and I had to repeat those, not sure why).

Anyway I sorted it out, thanks

prodigiosovolcan wrote:Sorry mate, I didn't get to answer you. My bad!

I actually found out as you previously said in 2020, that LV has some problems showing this properly, but then I realized it rendered fine (altough some random frames where completely blurred and I had to repeat those, not sure why).

Anyway I sorted it out, thanks

LV that cannot display proper motion blur unless you understand the logic how motion blur works in there. It needs motion data and it requires that's resend or moving forward step-by-step(because using a caching method for frames). Also it cannot use motion sub-sampling. Please note it!