J.C wrote:sandyadriadi wrote:Is it possible to completely bypass Octane colour management/tonemapper, and only using blender OCIO config? I'm using ACES workflow with ACES 1.0.3 OCIO config (not the one shipped with blender by default), and it seems that it doesn't let any value to go above 1 in linear space (I'm already set the octane camera imager to linear/off), so the highlight is compressed, even when I'm saving it as an EXR file.
The colour response, Shadow and Midtone value are already accurate/similar with Blender Cycles+ACES config, it only affects the highlight so I guess it is related to Octane tonemapper / imager. And CMIIW, the data flow is: Rendered scene > Octane Imager > Blender OCIO, that's why it only affecting value above 1 in the output file, and it will always be like that whether the Camera Imager is turned on/off.
It is possible in plugin for 2.79. There is a checkbox "Prefer tonemap if applicable" that totally disables/enables Octane tonemapping. I can't find this in 2.8. Maybe turning off Octane imager from camera tab does this automatically?
DrawFun wrote:J.C wrote:eisklotz wrote:I have a GeForce 970 and a 1070 but they are not available. Why?
This is Cycles settings. Octane has its own settings in Render Tab.
Dear Developers can you tell us why have you disabled GPU rendering for Cycles in your build?
This version is built without the cycle cuda kernels integration. We will build it identical to the official blender.org one in the upcoming versions.
Also, how do you use an hdr image for the environment?
VISUAL360 wrote:Also, how do you use an hdr image for the environment?
- Could you please try to connect a texture node to the texture env
Users browsing this forum: Grubert and 1 guest