Indigo Renderer Forum

In Blender you can select an area of the view for rendering by using SHIFT+B.

At the moment using render region works but with a problem. The region selected is the only part that gets rendered which is good - however it's seems the full size image is created while rendering. For example a 4500x4500 pixel image that has a region selected of only 150 x150 pixels will have the full 4500x4500 image created, but black, with the 150x150 area being rendered.This method still uses up a lot of RAM.

Any chance that only the selected region is sent for rendering? This would cut down massively on RAM usage particularly for testing purposes.

Hope that wasn't too long winded an explanantion of what I'm requesting

Agreed. I also thought that was weird...

Slows things down when tonemapping or working with lots of light layers for a tiny part of the overall image.

How do you compose the final image after if you only have the region sized render?
It's hard to place it manually to the correct spot.
I think you are talking about something that is called "crop region" in Max. That's not currently supported by Indigo.

{edit]
It's very easy to implement though, as far as I can see.

suvakas wrote:How do you compose the final image after if you only have the region sized render?
It's hard to place it manually to the correct spot.
I think you are talking about something that is called "crop region" in Max. That's not currently supported by Indigo.

{edit]
It's very easy to implement though, as far as I can see.

+1, that's it

could be usefull, actual region rendering isn't realy faster than fullsized rendering

I usually use region rendering just for testing so merging it into the final image isn't really a problem...

Though you could probably get it to spit out coordinates of the corners of the region relative to the whole image in the log or something. That way you just place that region at those coordinates et voila...

suvakas wrote:How do you compose the final image after if you only have the region sized render?
It's hard to place it manually to the correct spot.
I think you are talking about something that is called "crop region" in Max. That's not currently supported by Indigo.

{edit]
It's very easy to implement though, as far as I can see.

crop region - region rendering I think they are one and the same?.
It's useful for checking say textures at full res on an object without rendering the whole thing. Not sure if its quicker but I would presume it would use less RAM?.

Indigo region should render faster, that the whole image. The point here is not to save your RAm, but to speed up rendering of some area. You could use it to render out that glossy glass material faster (if everything else is clean) and compose into initial image later. In production work with Vray I usually use region to change the color of a table for example without having to render the entire image again (enormous speed gain). For that it's needed, that the dimensions of the initial image remain the same so I can insert my region back easily in Photoshop.
There is also a region type called Crop in Max. That does exactly what you are after. Renders only the region and crops everything else.
Also there is a region type called Blowup that renders selected region using initial image resolution.
....there are a fiew more region types in Max, but this is a Blender sub-forum so ...

I could certainly implement 'Crop' and/or 'Blow-up' options in Blendigo. I'll add it to the TODO list.

dougal2 wrote:I could certainly implement 'Crop' and/or 'Blow-up' options in Blendigo. I'll add it to the TODO list.

You would need to use Indigo SDk to implement that.
I mean crop and blowup are currently not supported by Indigo UI.

suvakas wrote:

dougal2 wrote:I could certainly implement 'Crop' and/or 'Blow-up' options in Blendigo. I'll add it to the TODO list.

You would need to use Indigo SDk to implement that.
I mean crop and blowup are currently not supported by Indigo UI.

I was thinking more along the lines of recalculating the camera parameters at export time.

Gotcha!
Would be cool to see this implemented also inside Indigo though.