I know this has been brought up before, but I'm trying to understand the advantage of the render window clearing at each crop render. It seems crop renders are generally used to finesse areas, like clouds, water, terrain, etc. If the whole render window didn't clear each time, you could do strips (crops) and be able to compare each.
Is there some technical reason the render window has to be cleared? I do realize that most changes will effect other areas, so maybe a "clear before render" button would work?
I'm just curious about this.
It's most likely a memory issue. I sometimes want to compare directly and fast, so I catch a screendump and paste it into Irfanview. Not even bothering to save. That works.
Tg2 saves renders by default in the temp folder...
I think it is more of a feature to add to the render window , to act as kind of a browser .
With forward and back buttons and so added , it would be nice to browse and see the changes in render.
I am not a programmer but i think it is more a priority thing , then difficulty!
Similar to desire (perhaps "intense need" would be better) for multiple ROIs.
But I'm sure its all in the feature request list ;D
That's actually a feature that was implemented in Blender recently. The renders just get automatically saved into a limited temporary buffer and you can compare them. Then save one.
I realize there's several ways to accomplish this (screen capture and overlay), but I can't understand why it would be so hard to implement a clear previous (or not) when crop render is activated. Even old Bryce could do that.
It wouldn't have to be a memory problem, since I believe the previous render is already saved to the temporary directory, so simply overlay the last render with the cropped portion of the latest.
It's not necessarily hard to implement, as others said it's just a matter of priority and development time. Features like this are planned for future improvements to the render view (just as viewing of alpha and individual color channels was added recently).
- Oshyan