Region in IR is not working as expected, it refreshes outside the selection

Hi guys

I’m really enjoying the IR, but sometimes it makes me frustrated because of some issues.
Now I’m working in a specific area in my scene and I want to use the Region feature in IR, for 2 reasons.
First to render faster because its a tiny area and I can see the results faster.
Second because I’m intended to compare with the latest version before every change I do in my shader, so I could see inside the region an updated version and outside the old version.
But this is not happening.

The outside is refreshing when I change something.

I’m using Beta 1 in C4D R18.

Thanks

The first one is known and should be fixed at some point, so that the IR works the same as in Max (IR size is independent of final render size).

The second, do you have “Clear VFB between renders” enabled? Does disabling it change anything? For me, it’s working whatever that is set to (see second image attached, where I moved a cube and applied a new material and changed it, with IR active and a Render Region enabled. I could also stop and restart IR, and only the region updated. Which version of Corona and C4D are you using?

Note that the outer pixels may get redrawn as the IR refreshes (going through the subsampling “big blocks to smaller to pixels”) but the pixels shouldn’t change, and that area is not being re-rendered (as far as I know).


I’m using the latest version’of Corona, Beta 1 and C4D R18.

Happy to know that the problem with IR size will be fixed.

And I made more tests here, and the behavior is exactly like you’ve described.

I suppose this redraw outside the region is something undesirable because it makes the IR slower in performance and makes the visualization more time consuming.
In a perfect world, everything outside the region should be static.

Is it possible to improve IR to freeze all the pixels outside the region?

Thanks

Ok, so if I understand it correctly, it’s not an issue. The IR only redraws pixels inside the region. The fact that the surrounding pixels are also enlarged does not cause any noticeable slowdown. But I’ll report this to the core developers to know if this can be changed.

Well, I’m not sure what exactly you mean with “redraw”.
Every time when IR refreshes and there is a region active, we see inside the region being restarting a new render. But before, the outside region becomes pixelized and starts to refine until stabilize, but not as a new render, just keeping the latest state.

For example if I change a color of a material, outside the region redraws, from a pixelized image to a refined image, but with the old color. Inside the region we see a new render.

I presume this is not expected because looks like it makes the render slower due the “redraw” outside the region.

I understood, what you meant. This “redraw” and refining from a more pixelized image to less pixelized is OK and does not cost virtually any CPU power. Rendering new data is expensive, but that only happens inside the region.