extreme apeture values cause issues over DR

[PIXELBOX_SRO]

Hi Guys,

i have a scene where i need to use very shallow DOF while having to use motion blur too.

My physical camera values are
apeture 0.3
shutter speed 1/400

When i render the scene over the DR, it seems like the node render either completely different frames of completely different values of above mentioned values.

Can you replicate this on your end?
I have a scene with lots of cloth simulations and i cant use more extreme values otherwise it all goes wrong.

Any ideas?

Cheers
M

[Morne]

Is this for a still or for an animation?
If animation, try backburner without DR

If for a still, try a DR node and exclude the ws and see what you get (for a start so we can see if the node is rendering wrong, or your ws)

[PIXELBOX_SRO]

Hi Morne,
i even get this in LC on local machine from time to time.
Really looks like a bug and happens when you have both MB and DOF active.
M

PS: i have to deactivate and activate both again to get it working properly

[Svetlozar Draganov]

Would it be possible to attach that scene for investigation?
Thank you very much in advance.

[PIXELBOX_SRO]

Hi Svetlozar,
sent to support@chaosgroup.com
thanks

[PIXELBOX_SRO]

ok so this bug also comes up when rendergin over BB without DR.
Some frames seem to have different motion vectors.
So i tried local render on my workstation machine with DR on and i got different buckets all over the place - even those from my WS were wrong.
Somethign is not right either its the camera or its some leftover cloth calculations in dump messing up with my scene???
Is there a way how to do a memory dump in max?
Ta

[PIXELBOX_SRO]

ok so settgin motion blur in the camera to disabled sorts out all the problems.
To me it looks like a bug in motion blur applying incorect vectors.
Ill try to post a grab of viewport nad grab of the video so you can see what i am talking about
M