Yeah, I’ve never found buckets to be slower. Almost always substantially faster. I didn’t realize that was considered a bug.
There were two notions in my post, which were quoted.
One was progressive for which i said it should be within reasonable range.
I mentioned also aa few caveats: It can be made much slower than bucket if one wants, just make the resolution huge, and there you have it.
At 2k, 10% ought to be the norm for a plain image.
There are a number of other things at play with it, however, due to the nature of progressive, like tiled textures, proxies, and so on, which won’t play that well with progressive algos in general (not even with the LC, to an extent), as mentioned in the RAM saving guide.
There is however no difference in convergence rates between the two algos, which is really what i meant to say: the difference is due to ancillary issues, not intrinsic ones (like for other engines.).
The other point made was fiddling with local subdivisions while keeping a low amount of AA, which i prefer to take to the beta group if needs be discussed.
I am not sure which notion was challenged there.
Yeah, sure. I didn’t send anything yet, will do that tomorrow. Promise.
No rush on my part.
Am currently brawling hard with Max and the creation of many lights: a fight that will take me a bit of time to lose. Win, i meant win. ^^
You got mail! 