[dyarza]

OK, so I just noticed a stupid little thing, and don't mind me if this has been covered (probably has) but I dont ever have much need for motion blur so I had not noticed it before.

The shutter speed setting in the M~R camera tag sems to have no effect in the ammont of blur that is rendered. Instead the motion blur is controlled with the percentage setting in the C4D motion blur tag.

Is it just me or does that not seem that physically correct to someone else?

Also, does anyone have any idea as if this happens with other plug-ins or Studio, or does shutter speed have any effect there?

Cheers,

[Becco_UK]

Motion blur is influenced by frames per second/ object movement, not shutterspeed?

I dislike the trial and error method of messing with motion blur strength which contradicts Maxwell's claim to be physically correct. I think motion blur should be determined by object movement.

Perhaps one day we can also have radial motion blur? For example: apply motion blur to a propeller rotating at high speed and it renders as a blurred triangle!

[dyarza]

Well, yes, FPS would have an impact in an animation sequence, or a real film sequence. But in still photography there is no FPS, motion blur is determined by how much the object moves while the film is exposed, so a qucker shutter should show less movement.

Like I said, doesen't seem very physically accurate.

[Becco_UK]

I agree that Maxwells' motion blur via via the Cinema4D plugin is not accurate. However, because Maxwells' motion blur is calculated during render time you get to see its effects in shadows, reflections and alphas which, at present is more of an advantage to me than 100% accuracy.

Perhaps when the new, delayed, Cinema plugin gets released there will be improvements.