OTOY Forums

Hello,
the current workflow to Override Imager/Post in viewport has two steps. First you have to select the checkbox next to the Header name, then another checkbox called Override. The Override checkbox is grayed out when in camera mode and it shouldn't be grayed out.

I propose to keep only one checkbox - the checkbox next to the header when enabled will automatically override any camera imager and enable Imager settings from this panel. I also propose to change its name to "Octane Camera Imager (override)" Now it has "Preview mode" in the name which is not exactly true as it also works in final rendering mode.

Same with Ppostprocess settings.

This has bugging users for a long time now, including me. I always have to make sure to disable override before I start rendering. I can't tell you how many times I had to cancel my renderings because I simply forgot.

I'm not sure the whole "Override" business is needed at all. I wish the side panel was just responsible for preview purposes. Once the "Octane Camera Imager (Render Mode) is checked, it will always override the preview settings for the final rendering. If it's unchecked, the preview settings can be used. And the topmost panel checkbox could basically go. Nobody really knows what it actually does.

The "Force Tone Mapping" checkbox is weird as well. It's inset but also affect the section below which is a completely different section and visually higher up in the hierarchy.

And the there's the Upsampling section which is badly organizes and labeled as well.

If I have some time, I might create a mockup.

I really find the global imager option (override) very useful. I almost never use Imager in camera object as it is very convenient to use it directly in viewport which is available right away. It just needs proper naming and simpler workflow (simple on off switch). Imagine you have 10 cameras in you scene and you want to adjust exposure in all of them. Using override you can just use one slider for all of them.

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.

Here's a quick mockup that I created. This would make much more sense to me - and probably new users as well.

Some points ...
*) If "Use for final rendering" is checked, the preview settings ARE the render settings. This will also override the "Camera Image (Render Mode)" if checked.
*) If "ACES tone mapping" is checked, the other settings in the "Tone Mapping" section should be grayed out to underline that they have no effect.
*) I hope that I understood the AI Upsampler confusion correctly. Otherwise ignore that section.

1. Again, you are doubling the steps to enable the Imager. Let's simplify this. Its either ON or OFF.
2. Agree
3. Again, this is being doubled. One checkbox next to Upsample, the other next to "Use AI..." Why do you want users to enable something twice?
One more since I want to enable AI upsampler it should already have one mode selected. Agait its doubling the steps. I don't understand why there is "No upsampling" mode in the dropdown menu. It should be either the dropdown with all there options and no Enable checkbox or Enable checkbox with two upsample options. edit: AI upsample is an option enhance upsampled images. It's not a switch to enable or disable upsampler.

ad 1) There might be a misunderstanding here. There's no doubling. This checkbox simply means, that whatever is set in the side panel, will also be used in final rendering - possibly overriding the Camera Imager RM. Checking or unchecking it will not result in any visual changes of the preview. It's just a flag variable.

ad 3) As I stated, I was not sure if there is a separate AI Upsampler in Octane. If not, this would be doubling indeed and the AI checkbox can be removed. But then the checkbox of the category should be respected. As of now, it's not.

Generally the checkbox enables or disables some option. It's not a flag. It's a common UI element to enable or disable things. Don't make it something else.
Take a look at Cycles render settings. There are options that are enabled using checkbox. eg. Path guiding or Simplify. They are not flags.

Again, the checkbox next to the name should enable or disable Imager. There is no need to have another checkbox that tells it overrides settings again.

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

We are talking past each other.

Right now I have the problem that I always have to do at least one extra action in the side panel before I can hit the render button. 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.

J.C wrote: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.