Interactive Rendering inheriting resolution from Render Settings

[danielsian]

Hi guys,

Why does the Interactive Rendering has a resolution based on the Render Settings?

Should be independent, so I can leave my Render Settings with the final resolution, for example 4K x 2K, and use the Interactive Rendering with a lower resolution in order to be more productive.

Thanks

[Eddoron]

Many renderers work like that, though some have the option to only render a certain %-amount of the chosen settings. I wouldn't call this a bug.

One thing you can do is to create two settings, one for previews with a low resolution and maybe lower bounce number and one for the final render.
Then, in the attributes manager, click on mode and chose the viewport settings, go to the hud tab and enable the render settings checkbox.
In the viewport, on the top, a text with your current render setting will appear. If you click on it, you can choose between your settings.
If you hold ctrl/cmd and hold it clicked, you can drag it around.

Another option is if you happen to use windows, to move the vfb window to one side and let it dock. Some part of the image will be cropped and only the visible part will be rendered.

[danielsian]

Thanks Eddoron

I'm using your solution already, but I'd like to not change the render settings or choose a different one. Should be an option on Interactive Rendering window.

Thanks for the tips.

[burnin]

Just a note (from experience gathered):
 
Majority of render engines (Indigo, Iray, Maxwell, Arnold, Thea, Centileo, Cycles, Vray, RedShift, FurryBall...) specifically, their interactive viewports, render independently of resolution/dimensions set in render settings. Preview is based on the active camera view in relation to IPR window size (which also scales interactively). Only Corona's & Renderman's IPR are locked to dimension settings.

So most likely it's a feature request?

Another possibility would be to use render presets to switch through interactively - for now IPR needs to be restarted.


PS.

Bug?

- If cursor is on the viewport, IPR is restarting indefinitely (with small sizes it stops when cursor is off/out of the 3d viewport).   

Probably a plugin conflict. 
Simple scene (sun, camera, cube, plane) was originally made for CentiLeo & then rearranged for Corona.
Fresh scene works fine.

[TomG]

This one I believe is already listed as a bug, the devs can say for sure. Anyway, it isn't this way in Max, the IR can be any size, independent of final render - which is usually what you want, as you'll generally need a smaller IR than your final render (especially if your final will be larger than your screen size!)

[danielsian]

This one I believe is already listed as a bug, the devs can say for sure. Anyway, it isn't this way in Max, the IR can be any size, independent of final render - which is usually what you want, as you'll generally need a smaller IR than your final render (especially if your final will be larger than your screen size!)

For sure, a smaller IR is necessary and I call this problem as a bug as well, because let's suppose I'm working on a scene to be rendered with a resolution at least 7 times bigger than my screen. If I forget to change the Render Settings before to start the IR I'll be in trouble. Probably I'll have a crash because IR is unstable enough to cause problems, mainly when it is used in stress situations.

[houska]

This is a known issue and will need to be improved. It's something that the Corona core is not doing for us, so each plugin (Max, C4D, ...) has to implement this.

[houska]

Probably I'll have a crash because IR is unstable enough to cause problems, mainly when it is used in stress situations.

Please report any crashes to us! The more information about crashes we get, the more likely we are to help you and others by making Corona more stable. Thanks ;-)

[danielsian]

Please report any crashes to us! The more information about crashes we get, the more likely we are to help you and others by making Corona more stable. Thanks ;-)

The crashes are becoming different after all improvement you guys have done.
Before it was possible to reproduce the most crashes, now it's more difficult because it's related to how complex a scene is.

I am trying to reproduce every problem that I find, and the crashes are because IR is unstable when you start to work in heavy scenes. Difficult to isolate the problem.
I imagine how hard is to find bugs like these.

Thanks

[houska]

Thank you for your effort, we deeply appreciate it!

[danielsian]

It's my pleasure :)