Without getting into a mountain of colour workflow, bit depth, file format headaches, has anyone used the simplified "ACES Tone Mapping button on the camera imager tab with any success? It seems to handle highlights and white objects ok, but it absolutely crushes any dark shades into oblivion, rendering it fairly useless to me.
Am I missing something? from what I can tell, that option deactivates almost every other camera imager parameter except for the exposure slider. I almost get the feeling im supposed to enable some sort of linear colour space mode, but I cant find anything that affects the live view to bring dark colours up to anything usable, the plus the manual states it is designed to save out a standard srgb 8 bit image. The only way I can get close is to crank the exposure all the way up to 3 or 4, but by the time the black objects start revealing themselves, the white parts have gone thermo nuclear.
How is it intended to be used, just with 32 bit renders and post colour grading?
Does anyone use the "ACES tone mapping" option?
Moderators: ChrisHekman, aoktar
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Is this a bug related post?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi, I'd suggest this ACES Octane "guide" as a reference.
This is the infamous ACES look which may look worse with an unsuited (panel, contrast, etc)/uncalibrated monitor and only the tip of the iceberg. It also skews color wildly. It's quick and dirty to avoid clipping (better than the archaic native camera imager options) but not beneficial as part of the color pipeline.
The page explains how it is meant to be used but I'll spoil it a bit: as a in-rendering (during render previews) image conformation (since the default sRGB EOTF will do as worse but less "pleasingly"). AgX OCIO is the (only*) way to go.
*as the single public and gratis solution in the present day
This is the infamous ACES look which may look worse with an unsuited (panel, contrast, etc)/uncalibrated monitor and only the tip of the iceberg. It also skews color wildly. It's quick and dirty to avoid clipping (better than the archaic native camera imager options) but not beneficial as part of the color pipeline.
The page explains how it is meant to be used but I'll spoil it a bit: as a in-rendering (during render previews) image conformation (since the default sRGB EOTF will do as worse but less "pleasingly"). AgX OCIO is the (only*) way to go.
*as the single public and gratis solution in the present day