OTOY Forums

Hi face,

was just testing RC1

noticed I had to turn off XSI color management completely in render regions/preview in order to get the same output as standalone
(the copy paste from debug graph feature is great for getting that over btw!)

could it be made possible to use XSI internal color management too? (Right now it looks like the render region/preview output is 8 bit, so using color correction will have strange effects)

-rr

(*changing this post as I discover things*)

Which SI version you use?
There are differences between SI 2015 and 2013/14 in the preview.
In 2013/14 you must turn off the color management to get the same result as in 2015 with activated color management.

face

Using 2015SP2. I'm getting color corrected render regions when "Apply to render region" in color management is on and a profile curve is set. I think this is expected behavior.

The only issue I'm getting is that the octane output seems to be a 8 bit/LDR image and shows banding when color management is applied in XSI.

When the XSI color managment is OFF (profile curve set to "no LUT"), then the output is the same as octane standalone which is a good solution and I can use Octane's color management with the imager node.

There's nothing wrong with the plugin (in fact it's great!) but what would be nice is if there were an option to use XSI's color correction too (It's so fast and nice to use with the sliders and all )

Is there a difference if you switch under the Renderer Options -> Misc Settings the Output Tonemap Type from
"With camera response curve" to "Without camera response curve"?

I think, there is also an issue, with should be without and vice versa...

face

I had it set to "without". If I want to get the same output as Octane standalone I have to switch to "without camera response curve" and turn XSI color management off.

When I use "with camera response curve" I get darker output, with a little less saturation, that can be color managed in XSI to look ok again, but with the banding artifacts.

Hm, for now, i don´t know, how to handle the problem.

On the other hand, it will not affect the image which is saved if you render a frame/pass.

-> SI Color management -> Render/Preview window
Octane image data -|
-> Save functons


Maybe i can catch if only the imager/postpro is changed, so that the rest of my routines can be bypassed.
This should make the imager/postpro much faster...

face

Isn't a real problem, would just be a little gimmick and as you said, it would not affect the render, so it's preview only.

Imager works great, is already quite fast (because it doesn't restart the render)

If it could be made even faster, cool
(maybe is it possible to do that also when if only the camera has moved? )

Und er the misc? settings it should be an option to disable mesh and pointcloud checking...

hi, how to use liveDB material preset in softimage?

Matteo3d wrote:hi, how to use liveDB material preset in softimage?

Haven´t spend time to integradte it for now.
Maybe if all other is working fine.

face