Those settings should result in the exported image being identical to what you see in the render viewport, except in two cases(1)(2). That matches the behavior I see when using those same settings. Because the OCIO view is set to None (sRGB) and the save color space is set to sRGB, both should use the tone mapping to sRGB as set up in the imager, which in this case says to use ACES sRGB output and ignore all the other pins (as explained by the tooltips for the relevant pins).GXGsynth wrote:What is the correct protocol to utilize the new 'ACES tone mapping' feature in regards to OCIO view/Force tone mapping/response curve/gamma/save format?
I'm having trouble getting exported images to look exactly as they do within the Live Viewer window
(1) If display color management is set up differently between Octane standalone and the viewer you're using to view the exported image, the two applications will be applying different color transforms to the image when displaying it. In Octane standalone, check Preferences > Color management > Display color profile to see if a color profile is being used ("sRGB (default)" means no additional color transform will be applied, so the viewport should match any non-color-managed image viewer).
(2) If you're on macOS and are using the HDR viewport (see Preferences > Color management > HDR viewport), the tone mapping settings in the camera imager node are bypassed for the render viewport because the OS does the tone mapping.
If neither of those cases apply and you still see a difference, please attach a scene or some screenshots demonstrating the difference because some further investigation is needed.
