[hyltom]

Today i use the tool "region render" to update one of my render. The original render was 2000x1500 and i have to recalculate a very small area (around 200*300). So i wanted to used the "region render" with the render setup at 4000x3000 like that i can get a better resolution of my small area. But i have fund that the memory used to calculate a region render is exactly the same than for the full resolution. Is that normal? is it a bug?

[JDHill]

That's not a plugin issue, but yes, region render takes just as much memory as a full render...it just renders that part faster. However, with the 1.6.8 plugin, you should rarely need to use region render. If you use the Camera in 'Manual' Size Mode for your image output, you can then use the command 'Maxwell_PickFilmSizeRectangle' to define a region you'd like to render - it will have a perspective match with the image size you've defined using the Camera's film-size. Here's an example:


1. a viewport, set up to render a certian size of film, at a random output resolution:



2. the same viewport, after using Maxwell_PickFilmSizeRectangle to define a new region:



3. combining the images together:




The only restriction is that the region picked can't be more than 100% of the film width/height off-center, since this uses Maxwell's Shift Lens feature to define the rendered frame. Maxwell_PickFilmSizeRectangle Rectangle is in the Camera toolbar, third button from the left. If you work this way (i.e. not using 'Viewport' for the Camera's Size Mode), your output resolution will not be linked to the size of the Rhino viewport, so it won't get screwed up when you resize your viewports or move toolbars around.

I hope it helps,

JD

[hyltom]

Thanks for your explanation Jeremy. I will update the plugin as soon as possible and try this. Your development ability is too fast, last time i updated to 1.6.6 and just 2 days later the 1.6.8 came out. So i was too lazy to update it again.

[kami]

The only restriction is that the region picked can't be more than 100% of the film width/height off-center, since this uses Maxwell's Shift Lens feature to define the rendered frame.

That restriction is really a pity. I came across it a few times
But as I guess it must be a mxcl issue (not of the plugin) I suppose, there's nothing you can do...
greets,
kami

[JDHill]

Hi Kami,

Well, this is really a distortion of the purpose of the shift-lens. The function of picking the region with a rectangle is technically only meant to be a shortcut of defining a shift, but we can use it the way I showed above if we want it to. Do you really think it's a huge limitation that the shift can't go past 100% - I mean, are there cameras that do more than that?

Either way, if you want more than 100% shift, you're right about it being mxcl-related, and changing that would be something for the regular Maxwell wish-list.

Cheers,

JD

[kami]

well, i tripped over it, when I wanted to render a section in the top of an image which already had an offset of -30%. But in the end, it's not so often a problem. I never had to use an offset of more than 100% for a whole image.
But it's a technical limitation only which hasn't to be necessary in my opinion... Maybe it's about the same reason why you can't go above ISO 16000