Depth of Field Flicker

[stir]

Hey

As the subject line states, i got issues with flickering in the DOF.
Its like it changes focus/aperture

https://vimeo.com/183466983/916a52f5b7
(the clip is short and pritey fast)

her in the cropped video you can see what i am talking about.
The camera is a targetcam but on these frames everything is static, exept for the cloth pile in the background, its slowly rotating, like a podium. But still the focus changes..... might even be wrong to say the focus changes because the focus is in the same spot. just the ammount of blur changing.

the settings under "Camera" is

Aperture - 0,0

Use F-stop - (checked)

F-stop - 2,8

Aperture edge - 1

Focustype - targetfocus

rest is default.

Anyone got any ideas of what this might be?


Extra info:

Windows 10 x64
3ds max 2016 sp3 ext1 ext2

Octane Render 3.03.4
Octane Plugin 3.03.3-4.16

[visionmaster2]

it's really strange.
are you sure the target is not mooving ? it's looks like you are in autofocus.
could you share the scene ?

M.°

[paride4331]

Hi visionmaster2,
I did a little test, but I did not have this result.
Actually watching your video seems a fstop problem rather than targetfocus.
I try to make assumptions ..
Have you checked if there is an incorrect key framer with a different camera f-stop during the animation?
Have you tried to replace it with another object, such as a cube, the object of cloth?
Have you tried to export to octane stand alone and have you checked if the problem persists?
Regards
Paride

[stir]

Thanks for the feedback.

We thought this project was done when we send it to the render farm fullrez.
So it became a bit caotic today when this problem stacked on top of a second deadline.
So I haven't done so much troubleshooting.

I thought I post the problem here so I could get some tips on were to start the debugging tomorrow.
So thanks, paride, that's some good things I can try out.

I did however before I left the office, submitted the render to the farm again with aperture 0,85 instead of using f-STOP. If this yields a different result, then we can pinpoint it.

I can't share the scene as it is now sadly.
But if the problem persist after changing the objects as paride mentioned, thenot i could share that file.

I keep you guys posted and again,thanks for quick replys.

-Mats

[stir]

hmmm
Changing from f-stop to aperture did indeed fix the issue.

The next step would now be to try recreate the issue with f-stop, by stripping the scene as much as possible and still maintain the issue.
And maybe be able to recreate it in a new scene.

[paride4331]

Hi stir,
it would be very helpful if you could reprodurre the problem you had.
The problem could be the switch between apertures and f-stop.
Octane SA has a consistent relationship using the aperture and f-stop,
it does not have a check switch, you can use them interchangeably.
If you try to reproduce the issue, send the animation first time with aperture setting and then with f-stop.
Thank
Gabriele