Ok, I understand. Thanks for the article. Interesting read.

Actually I just found out that some flat geometry with screws as textures (in normal and AO map) do need the AO texture slot to be taken into account. At least for some objects. So it would be nice if Octane can take it into account on a per-object or scene wide basis.

I have sent you a PM with a new version which has the black spotlight issue.

Thanks for clearing up the HDR issue bit depth issue. I am glad to hear that this part isn't the issue.

When adjusting the settings you suggested, it does look better, but It still looks way better if I export a 32 bit ...

Were you able to reproduce this?

Is this at least confirmed as a problem?

Thanks for considering

Yes, I am looking for an HDR color space workflow inside the engine itself. Imagine saving a video with a broken workflow like that. It would be nice if this is on the roadmap.

Thanks for the links. I read it but it still doesn't answer the question of how many f-stops of dynamic range Octane uses.

So nobody knows how many f-stops of dynamic range Octane uses? If this is too low, no fiddling with gamma will fix it. Exporting an image and modifying with a 3rd party program is a really, really bad hack.

How many bits (Dynamic Range, f-Stops) does Octane use to render an image? It seems to suffer from the same problem described below. I want my indoor render to look like what a human eye sees, not some cheap disposable camera, HDR wise. The location where the sun shines on the floor is totally white ...