Page 1 of 1
light difference between 2.13 and 2.15 and 2.16a
Posted: Fri Jan 09, 2015 10:46 am
Hi, when I upgraded my octane for max from 2.13 to 2.15 or 2.16a, my image gets brighter, don't know if this is a bug, but what's the way to fix this?
here's an image example.
Thanks
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Mon Jan 12, 2015 3:42 am
by FooZe
Hi, There was a change between these versions that removed the ISO and FSTOP parameters from the imager settings to simplify things.
If you used the default fstop and iso parameters in the 2.13 scene, try an exposure of 0.59 with 2.15+.
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Mon Jan 12, 2015 10:19 am
I didn't use iso or fstop, it's on default settings.
what to do now?
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Mon Jan 12, 2015 8:43 pm
by FooZe
Set the exposure in 2.15+ to 0.59
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Tue Jan 13, 2015 11:22 am
ok, got it now... so 59% of current exposure brings back light like before...
my exposure was 4, and 59% of that is 2.36... and when I set my exposure to 2.36, I see no light changes...
to be honest I don't like this change... don't see the point of it, but ok, at lest I have a workaround...
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Wed Jan 21, 2015 2:58 am
by Phil_RA
Wait, why was that removed? If I want to match the f/stop, ISO, exposure values from a photo, how do I do it now? It was good to have an HDR image and use the same value as the ones used when taking the photo. I'm on 2.10 so I haven't upgraded yet.
Re: light difference between 2.13 and 2.15 and 2.16a
Posted: Wed Jan 21, 2015 9:38 pm
by FooZe
It was a design decision by the dev's since both controls just changed the exposure anyway.
Please see the standalone release post here:
http://render.otoy.com/forum/viewtopic.php?f=24&t=44074
Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944