Motion Blur stops working at x frames onward

[ratata]

Hello,

Here is a link to cleaned up file with just the problem: https://we.tl/JoTyyeFCdT (it will give an error for redshift, since it saves as an option in render settings, but was not used in any way.)
Motion blur stops working at higher frame counts in this case 1100+

All you need to do is render to picture viewer and you should see MB on cubes, then change the render settings to "cache 000" and on the cloners cache tag - change offset to "0", rendering now produces no motion blur in PV (it works in LV)

I tried removing everything I could think of and it still does this, I noticed this with other objects too, but I guess you only need one example...

Win 10, C4D R17, Octane 3.03.4-R3
also tested on C4D R17, Octane 3.03.2-R5

Sandi

[aoktar]

What's problem? Crash or stop? It's working fine on me.

[ratata]

The problem is the motion blur, if you compare the sequence (rendered as described in first post), one rendered from 1000-1050 and one from 1300-1350, one has motion blur second doesn't.

[aoktar]

There is no movement on cubes after frame=1100. Do you still expect motion blur on these?

[ratata]

From the first post: "...then change the render settings to "cache 000" and on the cloners cache tag - change offset to "0"
Of course there is no animation if you don't change the offset on the tag.
Will try to be more exact next time by providing 2 seperate files...

[aoktar]

I missed that because always doing something and overlook sometimes. Sorry. Well it's not working after "time_sampling>4". Don't know why. Propably about evaluation of mg caches from a temporary document.

[ratata]

Thanks, putting it below 5 worked.