Some questions about features in Corona 1.0

[iMotion]

As I understand, in earlier versions (like A7 etc) if we need to localy activate DOF in some camera, we just put CoronaCameraMod on it and no need to go to global camera settings. Now in 1.0 we have not such option in CCM, because there are no checkbox that activates DOF. Instead of it, I see checkbox which is deactivates DOF. Logicaly, first I need to go to global camera settings and activate DOF globaly and only after then I can switch it off (instead of switching ON) on some cameras? Thats the right way? Is it really simplier way then before?
I'm a bit confused =)

[Ondra]

Hi,

the situation with camera mod is a bit tricky. This solution was chosen co camera mod does not influence DOF by default - which confused some of the users. So we decided to put either "force off" or "force on" checkbox there - so when it is unchecked, the camera mod would have no effect on DOF.

We chose "force off" because if you would have DOF globaly off, but forced on in some camera mod, you would have the global controls such as bokeh shape frozen.

[iMotion]

Hi, Ondra.
Couldn't be the better way, maybe, to: 1) implement 2 checkboxes - Force DOF on and Force DOF off. 2) Make default settings of corona with global DOF on?
Why I'm asking? I have a situation tonight: My transfer from 7.2 to 1.0 was a little hard, because I instaled 1.0 almost at 23.59 before A7.2 will dead =). I dont expected of such new features with DOF in 1.0 and when I start batch rendering and go to sleep, at morning I see that there are no DOF effect in all of my cameras at all.

[Ondra]

I dont think there is a reason to add extra controls - we need to make some sacrifices to keep the UI simple ;)

[iMotion]

Ok, I will get used to. Thank you

[iMotion]

QUESTION #2: About exposure and same CCM (coronacameramod).
Why it is better to lock Exposure setting when use CCM? As I see, it discredits real time exposure tweaking when rendering (the most powerful advantage of our lovely render engine ;)

[Ondra]

This is because exposure is usually the only reason to use corona camera mod - so we saved another confusing checkbox by making this override always enabled

[iMotion]

Are GGX brdf model are hard locked or can be changed to another type(blinn/phong/ward) ?
Thanks.

P.S Additional thanks for implementing estimated time option ;)
I thought it is not possible at all, even in another renderers (can be viewed only during animation rendering?)

[Ondra]

you can actually change BRDFs via maxscript, but the option is hidden from UI because it is generally not needed, and would complicate the UI

[iMotion]

you can actually change BRDFs via maxscript, but the option is hidden from UI because it is generally not needed, and would complicate the UI

Most people (and you, particularly) said that GGX is good for metals. Most likely, for another types of mats we need another brdf ?Or GGX is something like just physical correct model and universal type?

P.S Will go wikipedia to study BRDFs )))

[Ondra]

GGX work nicely also for other material types, whereas other BRDFs work only for non-metals, but not for metals.

Truth is that people are very bad at recognizing BRDFs, just as they are for example bad at judging refraction. What they recognize is for example lighting and surface details. So usually tweaking reflection maps pays off much more than adjusting BRDF shape. Plus working with textures is natural, whereas working with BRDF models is not

[iMotion]

Thank you. For now - I have exhausted all my questions =). Maybe later when I dig deeper in 1.0 )

[Anri_Ford]

is it possible to lock the render region in interactive?

[Ondra]

currently impossible. Scheduled for a monthly build 1.1 or 1.2

[iMotion]

What is the "god days" in tips about "single bounce only" from scattering option in mat.editor? ))))