OTOY Forums

Hi aoktar,

during my last project I realised there is a bug with the stage camera object switching between two cameras, that have motion blur activated.
It only accurs, if the 2 octane cameras have different field of view (thats what I discoverd so far). It is not there, if both cams are set to the same FOV.
It is also gone, when you disable the motion blur.

And most important: It only occurs in final rendering! with the picture manager, it is not visible in the live viewer!

SCENE: Stage Object switches between CamA (35mm) and CamB (50mm) from Frame 25 to Frame 26.
BUG: Frame 26 is rendered with a field of view of something between CamA and CamB, not with the field of view of CamB. Frame 27 is fine again.

Here some screenshots that show the problem in final render output.
Here the little test scene: Hope it is the same elsewhere. Created with R15.
Try rendering without motion blur, and it is ok. Or try rendering with CamB also set to 35mm, it is also ok.

Thanx,
ChrisVis

i don't register the fov of cameras for motion blur.

Hi aoktar,

that is why the problem occurs? So it can be fixed, if motion blur is aware of the cams FOV?

Oh and my mistake: It is the focal lenght or focal distance (35mm, 50mm) we are talking about, not the field of view. But almost means the same, I think.

Just wanted to report it... if it is not that easy to fix, leave it like it is. But people should know it.
You can always rerender this one frame with the stage object disabled, but you have to be aware of this.

Cya,
ChrisVis

ChrisVis wrote:Hi aoktar,

that is why the problem occurs? So it can be fixed, if motion blur is aware of the cams FOV?

Oh and my mistake: It is the focal lenght or focal distance (35mm, 50mm) we are talking about, not the field of view. But almost means the same, I think.

Just wanted to report it... if it is not that easy to fix, leave it like it is. But people should know it.
You can always rerender this one frame with the stage object disabled, but you have to be aware of this.

Cya,
ChrisVis

i haven't tested your scene yet. But i'm doing some estimations. What can be a problem when you immediately switch from camA to camB. It's not important to do this with Stage object or some key frames. We check the results. Problem should be related with lack of FOV motionblur data. Octane needs to know all data to produce proper motion blur. If i don't register some required, it can't produce expected result. Atm, i'm giving only matrixes for a camera.

Of course i can add this support, but need some fundamental changes on engine. Noted.

Hi aoktar,

ok, thank you for your feedback.
Now it is clear to me.

Thank you,
ChrisVis

And please don't forget while making some criticism on lacks of manual on infos, i'm just one and product is becoming bigger day-by-day for one people. Also every update of Octane causes lot of new work here.

aoktar wrote:And please don't forget while making some criticism on lacks of manual on infos, i'm just one and product is becoming bigger day-by-day for one people. Also every update of Octane causes lot of new work here.

Yes, personally I have no glue, how much work you have with the plugin and all the updates, but I guess it is huge! You are doing a great job, ahmet -> fastest developer on the octane-earth! Maybe you should take you some Off-time (to refresh, seriously).
And I didn`t want to make any critisism on the manual, just asked a question, because some features weren`t clear to me and I couldn`t find it there.

We all appreciate your work, just take your time!
Respectfully,
ChrisVis