OctaneRender™ 2020.2 (XB1) is out! + 2021 roadmap updates! Tweet

[jimho]

fast fog as post means it would not help on the god ray, I guess, right?

Correct, it’s just using depth/pos to do a ‘mist’ attenuation pass. We are working on real time GR and have great results in brigade: https://twitter.com/otoy/status/1303018 ... 79296?s=21

Thanks for the respond,
hope the real fast fog/god ray could be used sooner

[funk]

I have some feature requests regarding OCIO

1. Can we have an OCIO config per scene instead of a single global preference?
2. When using OCIO, can we have the octane tonemapping controls working? (at the very least saturation and gamma?)

Maybe 2 is a temporary issue which wont matter once we have a better compositing workflow. Curves, contrast, color correction etc of the final image is essential.

[MildMustard]

Totally agree with Funk.

+1

[Jolbertoquini]

Built-in multi-light, fast fog, wireframe and custom compositing node graph passes
I can't find where it is. you hid it so not intuitively
https://www.youtube.com/watch?v=At-IdZE ... e=emb_logo

I don't understand why not make it easier like Corona - Vray

I searched for an hour and did not find

Hi

I did the same but actually after read the description I understood they said will be on the next build is writed right there in commas.

Best,
JO

[Jolbertoquini]

+ from my side aswell not only OCIO but also Filmic is working great but the fact we loose some settings of the tonnemapping is limited would be great to have access.

Best,
JO

[enricocerica]

Some really cool features, especially the multi-scatter ! Will have a try to it to check how it could manage huge grass surfaces I often use in my scenes.
Also the OCIO is great, I imported the filmic set from blender and it works like a charm

[Kalua]

Built-in multi-light, fast fog, wireframe and custom compositing node graph passes
I can't find where it is. you hid it so not intuitively
https://www.youtube.com/watch?v=At-IdZE ... e=emb_logo

I don't understand why not make it easier like Corona - Vray

I searched for an hour and did not find

Read the first post:

Integrated multi-scatter nodes - Vectron Scatter, Volume Scatter and Surface Scatter*
Built-in mutli-light, fast fog, and wireframe post processing in imager node*
User generated compositor AOV passes for combining render and light passes in full a compositor node graph *
Nested Compositor Operator Nodes*
Built-in Vectron Primitives and Operators*
Built-in Raytype, Utility, RGB channel, math and color operator nodes*
Chaos Texture Tile System*
UV Distortion Map Textures*
Gradient Node Improvements*

(*Coming in 2020.2 XB2+ builds)

[Kalua]

I am curious about <<Chaos Texture Tile System>> and <<UV Distortion Map Textures>> features. Is there any preview of them??

[Goldorak]

I am curious about <<Chaos Texture Tile System>> and <<UV Distortion Map Textures>> features. Is there any preview of them??

Yes we showed these in my GTC talk. I can grab some images

[karl]

I have some feature requests regarding OCIO

1. Can we have an OCIO config per scene instead of a single global preference?
2. When using OCIO, can we have the octane tonemapping controls working? (at the very least saturation and gamma?)

Maybe 2 is a temporary issue which wont matter once we have a better compositing workflow. Curves, contrast, color correction etc of the final image is essential.

I'm looking into the possibility of allowing an OCIO config per scene. It gets a bit complex because you can load one scene into another scene... but it is likely this will be in a future 2020.2 XB release. The per-scene config, if set, would override the global setting. Note that generally OCIO seems to be intended to be used with the system-wide "OCIO" environment variable specifying the same config for all applications and all projects, rather than having to set it up for each application or project, but that workflow might not be for everyone.

I have a question: If you chose an OCIO config for a specific scene, and then exported an ORBX file, would you expect a copy of the OCIO config itself to be embedded in the ORBX file or just a filename reference?

Saturation makes sense and is easy to get working when using OCIO (unless there's something I've missed). We should be able to get this in for XB2. Other things like gamma are problematic, because the current built-in Octane tone mapping requires the color to be clipped into a 0-1 range in the sRGB gamut (and can introduce hue shifts), which would defeat a lot of the purpose of using OCIO in the first place (nicer tone mapping for extreme highlights, outputting in wide-gamut color spaces, etc.).

Another question: Would it be helpful if there was an option to enable all the tone mapping controls even when using OCIO, BUT enabling that option meant that the clipping that the built-in tone mapping does couldn't be undone, so you wouldn't be able to do all the nice HDR stuff that some OCIO configs enable?