Don't denoise when aborting rendering
When aborting a rendering the scene will still be denoised and some data will be loaded. This might not be an issue with smaller renderings, but when the resolution is high, you sometimes have to wait several minutes after you canceled the rendering.
When working in Octance, I can cancel the rendering immediately within seconds. In Cycles the cancelation already isn't very responsive but with the denoising on top, this just takes way too long.
7 Comments
I'd ask this to be an option—probably enabled by default. I agree it's often not what I expect to happen when canceling a render. But I bet some people enjoy this too, and personally I like it when I'm doing a sampling test to see how much I need to get a good final result without having to manually change the sample count every time: just run render and cancel when you want, see how it looks after denoise, rince, repeat.
Why not. If some users want that to happen - sure.
Yes it takes so much time to abort render like this now... and it will stuck whole blender... simular issue is with ctrl+Z while rendering... as blender loads old saved file... it aborts render and stuck i am stuck sometimes for a minute... From my perspective whole ctrl+Z should be reworked... when the files are big it takes etarnity...
I agree that it isn't very responsive, but I disagree that the option should be enabled by default. Many people have gotten used to the unusual cycles rendering, and im not sure if theres a way to denoise out of the app.
You can always denoise using nodes or CLI.
I'm not sure people being used to it is enough to justify not changing things if we can establish it's for the better.
The biggest example of it is how Blender was changed from right-click-select to left-click-select by default. Even though most users were used to RCS. And we've been reaping the fruits of that change since then, with most new users more likely to keep Blender.
I'm not sure what you mean by "unusual Cycles rendering". But this proposal is for the cases when you spot a mistake in the final render preview and want to cancel the process. This should be a total abort of the process. I don't need my faulty rendering to be denoised. And when you have a big resolution this always adds up to a minute of waiting. This is especially noticeble when you also use Octane for Blender. There canceling isn't just much more responsive, it stops without any additional loading/denoising.
and at the end blender added it glad to see that