Just a quick note of thanks Vlado and the team, we find ourselves using progressive sampler more and more these days. Coupled with crazy fast xeon cpus, its a workflow made in heaven.
Hoping for continued improvement of it. 
thanks!
For SP3 we will have proper sub-pixel filtering, so it means the progressive sampler will be able to produce 1:1 the results of the Adaptive sampler, even with sharpening AA filters.
We are also looking into more efficient criteria for adaptive sampling; the one that we have right now has worked fine for 10+ years, but is a bit too conservative (i.e. in many cases shoots way more samples than strictly needed).
Best regards,
Vlado
Wow, this will be awesome!
Just hoping you still have the resume feature somewhere on the todo list
I haven’t used it yet. What’s the benefit? It’s not faster, is it?
It’s progressive! 
Yes, but it’ll still take just as long to get a clean render, correct? The difference is you can stop it before it’s done and have something to show for it.
not any faster, just more convenient
Actually, ATM, I find that it’s slower than the DMC.
Whatever render I’m doing, if I crop render and let render the DMC, and then switch to progressive and let it render for the same amount of time as the DMC, I always end up with a noisier result.
Stan
Some slowdown is unavoidable - keeping the image ready for display at any time takes some CPU cycles. There’s quite some room for improvement though.
Best regards,
Vlado
I’m cool to have it refreshing way less than “real-time”
once a minute, or even a option to disable the refresh and having a button “refresh” that would refresh only when pressed would be a good solution for me.
If that was the case and we put the refresh slowdown on the side, should we expect a 1:1 noise for 1:1 rendertime?
Thanks
It’s not purely a matter of display. V-Ray already has some logic to prevent updates from happening too often.
Best regards,
Vlado