light difference between 2.13 and 2.15 and 2.16a

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.

All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
User avatar (Default)
[email protected]
Licensed Customer
Posts: 134
Joined: Tue Jun 01, 2010 12:52 pm

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
Attachments
Octane usporedbe.jpg
Windows 10 64bit, Intel i5, 32gb Ram, 2x nvidia 1080ti, Driver: 390.77
Top
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

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+.
Top
User avatar (Default)
[email protected]
Licensed Customer
Posts: 134
Joined: Tue Jun 01, 2010 12:52 pm

I didn't use iso or fstop, it's on default settings.

what to do now? :(
Windows 10 64bit, Intel i5, 32gb Ram, 2x nvidia 1080ti, Driver: 390.77
Top
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

Set the exposure in 2.15+ to 0.59
Top
User avatar (Default)
[email protected]
Licensed Customer
Posts: 134
Joined: Tue Jun 01, 2010 12:52 pm

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...
Windows 10 64bit, Intel i5, 32gb Ram, 2x nvidia 1080ti, Driver: 390.77
Top
User avatar (Default)
Phil_RA
Licensed Customer
Posts: 75
Joined: Fri Jul 25, 2014 2:30 am

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.
Top
User avatar
FooZe
OctaneRender Team
Posts: 1335
Joined: Tue May 15, 2012 9:00 pm

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
Top
Post Reply

Return to “Bug Reports”