32 bit? where are pixels above 1.0? Tweet

[javierluisbravo]

Hi..

Again... i can't save in 32bit floating point keeping values above 1.0 of the pixels...
how's the workflow now?

i used to do this and it worked before.. Not working now as lot of settings changed:
i did like this:

First of i turned off gamma hack.. put path tracing , 250 samples, static noise, adaptive sampling on, casutic blur 1, gi clamp 10... imager off , linear/off activated...
and saving sequences to exr as default worked perfectly...

now it does not... the overbrights or pixels above one.. are cut down.. so when i exposure down the exr file.. all looks like an 8 bit picture..

Hope someone can tell me how's the way now.. as it's not working as it used to do.

thanks,
Javier

[javierluisbravo]

well...

installing version 2020.1.5 i was able to figure out what was happening... as i made it work in 2020.1.5.
it's something in the renderer tone mapper: HDR.. (theres no more HDR LINEAL there...)

https://ibb.co/8xkxrxV

Tell me if those options are in other place.. i think that there was a problem when ocio /aces got implemented..

if i can't render in raw the exr files are useless..
i hope it's something i am missing...

thanks in advanced!

[paride4331]

Hi javierluisbravo,
I don't understand where your setting is clamping the image but the setting should be like in the screenshot.
Regards
Paride

[javierluisbravo]

Hi..

it's clamping pixels above 1. If you render and right click over the pic where you have something blown in intensity.. you should be able to see values above 1. Try it.
They don't show in 2020.2 . I can only see values going from 0 to around 1.

In 2002.1.5... to get not clamped renders... i changed current tone mapping from HDR to HDRI lineal in kernel tab and it worked perfectly.. But now in kernel tab in this version 2002.2 those options are gone!!!..
now it says HDR and HDR half..(instead of HDR and HDR lineal) why? i don't know why that changed.

I have the same settings...as yours...

What's your kernel settings? I have not setup OCIO yet...

kind regards,
Javier

[samsue]

It is no surprise to see this Topic.

it's a shame the Devs of the SDK for 3DS Max are doing with the usability of Octane

[paride4331]

Hi,
it's not depends on 3dsMax devs, ACES and OCIO in Octane is a topic definitely not light.
Maybe this can help.
viewtopic.php?f=9&t=75843&hilit=linear+ocio#p389792
by the way, I'll check to confirm.
Paride

[samsue]

depends on the Developers to organizing in a rational and practical way, the Octane standalone, is more practical.


Do you find it acceptable to have to read this topic to understand how saving on 32 bits linear works? It should at least be described in the manual, even in the previous version there is nothing.

[javierluisbravo]

Thank you paride!

i will try to mimic that.. maybe is that i have ocio all default with no settings yet... maybe is that... i still did not setupt the ocio config files...
maybe is that... it shoulnt but maybe is that.

i will take a look.
thanks you!

[javierluisbravo]

Well..

after a paride post i found out the issue. I think it's a bug:

=> pixels are clamped over 1 in the render buffer of 3dsmax, when OCIO is turned off / disabled / or no config file
(this should not happen..)

=> when Ocio is setup properly... the pixels are not clamped (unless you put srgb in OCIO color space)

I know the hard stuff that AcesCG / OCIO setup is..when 3dsmax is not even prepared for that yet..
i have been strungling with that in Nuke, After and clarisse...
and as 3dsmax is like delayed with all this.. i could set it up in Vray.. and now i have to find the workflow in Octane to make all match..

Thanks for putting OCIO and AcesCG here... as AcesCG is the way to go to make all more realistic renders..

[samsue]

Cool, thanks for posting what you found out.

I recommend you to read this material, it is very interesting.

https://chrisbrejon.com/cg-cinematography/introduction/