Hi,
With the latest release (9.11) I've noticed that there is a noticable exposure difference in final render compared to the viewport render.
I have to set gamma to 0.5 in Blender's Color Management tab to match both renders. Since then they are almost identical.
Viewport exposure different from render exposure
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)
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)
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
- Synthercat
- Posts: 284
- Joined: Mon Aug 30, 2010 11:12 am
- Location: Thessaloniki Greece
That seems like the bug I recently reported that was fixed on 9.10 I think
Have you clicked the "Octane Imager" tick on the Camera settings?
(The should default to ON in my opinion)
Have you clicked the "Octane Imager" tick on the Camera settings?
(The should default to ON in my opinion)
Linux Mint 19.3 | GTX-1080Ti | AMD FX-8320 (OCed 4.4GHz) | 16GB RAM
Weather it is ON or OFF there is still a difference.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group
- justavisitor
- Posts: 242
- Joined: Sat Oct 05, 2013 5:34 pm
Has this been fixed?
Latest OctaneRender for Blender. Windows 10, i7 quad 3.7GHz, 16GB, 2xTitan.
You can't use Blender tonemapping AND OctaneRender tonemapping and expecting to have the same result in both Blender Image Editor (F12) and Render Display Mode (Shift+Z). If Octane Imager is ON, you should turn OFF Blender Colour Management completely and visa versa (except the case when you know what are you doing). Otherwise you'll be using tonemapping twice. If any of Blender's tonemapping is still ON, you'll get Blender's tonemapping added on top of the Octane's one. Converting to sRGB colour space is a part of tonemapping too.
Linear workflow means that a user doesn't use OctaneRender tonemapping (Octane Imager is OFF) but uses only the Blender's one (which btw has sRGB colour space turned ON by default) or other applications to add tonemapping to an image later. This is why Octane Imager is OFF by default.
But if you turn ON Octane Imager you have to be sure that ALL Blender's Image Editor tonemapping is OFF.
Linear workflow means that a user doesn't use OctaneRender tonemapping (Octane Imager is OFF) but uses only the Blender's one (which btw has sRGB colour space turned ON by default) or other applications to add tonemapping to an image later. This is why Octane Imager is OFF by default.
But if you turn ON Octane Imager you have to be sure that ALL Blender's Image Editor tonemapping is OFF.
Win 8.1 x64, i7-4930K 64GB, 2 x GTX-690
- justavisitor
- Posts: 242
- Joined: Sat Oct 05, 2013 5:34 pm
Is this correct? I've never seen it mentioned anywhere, and you'd think it would be the headline of any Octane/Blender tutorial/manual.Saramary wrote:If Octane Imager is ON, you should turn OFF Blender Colour Management completely
Also, if this information is accurate, exactly how do you do that? You emphasize that we should turn it off completely, implying there are several ways to do this and that some of those are not complete.
I googled various combinations of turn off color management and/or tonemapping in Blender, but didn't get any usuable results, so this is significantly less simple than it seems.
Latest OctaneRender for Blender. Windows 10, i7 quad 3.7GHz, 16GB, 2xTitan.
This does the trick! I have had sRGB switched ON and that caused the difference in rendered file.Saramary wrote:...
But if you turn ON Octane Imager you have to be sure that ALL Blender's Image Editor tonemapping is OFF....
The example attached file has the proper settings for viewport and final render.
- Attachments
-
- imagerExample.blend
- (732.48 KiB) Downloaded 282 times
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
System – Windows 11
My Behance portfolio, Blender plugin FB support group