UX improvement for enabling Imager/Post Tweet

[J.C]

Updated UI with description in header - (override camera settings)

imager.png

But how would that make it possible for me to render without having to adjust the preview settings beforehand? I guess I would always have to uncheck the side panel checkbox and that's where I already am right now.

You can create a default startup file with this imager disabled.

[J.C]

...And if I don't have the 3D Viewport active it's even worse as I have to enable the 3D Viewport first just to get to the Octane side panel. So if you have a solution to get rid of that issue, please share it. Mine is just what makes sense to me and would work. There might be other or better solutions.

The other solution would be to move this panel into the Render or Output properties panel.

[Andreas_Resch]

I don't think that would make sense. These are preview render settings and not final render settings. The now labeled "Camera Imager (Render Mode)" section already takes care of that.

[elsksa]

As far as Force tonemapping is concerned it is closely related to OCIO as when OCIO is enabled it disables Tone mapping tools. That's why it is located there so you can re-enable them again on top of OCIO tonemapping.

Not in the least. Force Tonemapping was implemented long before OCIO support and isn't directly related.

As covered on this page, the situations calling for a need to check the Force Tonemapping option are close to non-existant.

Instead of "OCIO disabling other options", it is rather the signal (Octane data output) taking another path.

[J.C]

These are preview render settings and not final render settings.

They can be preview or render settings or both. The thing that matters is weather you enable it or not.

On the other hand in C4D plugin the imager settings are be global and affect all cameras. They are located in Octane settings next to Octane render settings. They are permanently enabled until you enable camera imager in camera settings. This is simple solution and could also work in Blender.

[Andreas_Resch]

It's hard to compare the UI of Blender with Cinema 4D. Their infrastructures are quite different. The addon should rather follow the general design guidelines of Blender. I guess that's why the side panel was created in the first place. And that's fine with me. There's no need to make thing more confusing than they already are. A simple fix to the side panel and we are good to go.

[J.C]

1. I'm giving an example of UX not UI. I like how it is done in C4D and it also could be done in Blender.

2. In Cycles all Render/Color settings are located in Render properties. Imager Could also go there.

3. Again it also needs naming correction and making the panel Switchable in one click (not multiple) as it is done in Blender Cycles.
An example from Cycles motion blur settings, one state MB is disabled, the other is enabled. Simple.

[J.C]

Regarding Upsampler options, the AI upscaler is an option that uses AI to enhance upscaled image. If it is off it uses regular methods to upscale image.

[Andreas_Resch]

Well. Then my suggestion wasn't really redundant. The only thing that could be considered is, if the category checkbox is necessary of if triggering the upsampling via the checkbox is enough. Personally I find the checkbox for the category nice. You can set whatever you want inside the category and just turn it ON/OFF. It's also analogue to the Denoiser section above.