|
 |
What, actually, happened with the "re-render" function?
It was quite handy when trying to render only a section of the image and
the parser would hit an error. As this leaves you with a blank preview
window, there's no way to manually pick that same section again (except
for guessing), but in 3.6 you could at least re-try rendering the very
same section via the "re-render" command.
I do miss that.
Post a reply to this message
|
|
|
|
clipka wrote:
> What, actually, happened with the "re-render" function?
is that the functionality called "Rerun" in the Windows GUI?
> It was quite handy when trying to render only a section of the image and
> the parser would hit an error. As this leaves you with a blank preview
> window, there's no way to manually pick that same section again (except
> for guessing), but in 3.6 you could at least re-try rendering the very
> same section via the "re-render" command.
I didn't even know that was the behavior for Rerun with
the non-permanent selection in the error case (well I always
use shift-drag anyway). But I think it would be more intuitive
if the non-permanent selection simply remained active until
a render was either completed successfully or explicitely
aborted by the user (even for the normal render command).
Actually the reason I always use shift drag is that I most
often use this to render a section of the image at a higher
resolution, i.e. first "shift drag" region in lowres render,
click "set but don't render", increase resolution, render.
Post a reply to this message
|
|
org> schreef in bericht
news: