Any chances to implement Adaptive Bucket Splitting for distributed rendering? I found this feature as life-saving in many cases, but unfortunately it works only for local rendering. It could be one of the best feature in Vray since ever if it was available also for DR.
Yes, it is something we are working on, so stay tuned. 
Best news ever :)))))
Don’t get your hopes up yet, it’s been 3 years in the works. And seeing as the update cycle is slowing down, you might have to wait a while longer.
…emotional damage…
Where do you get such rumors from?
I’m just being realistic, maybe a little too blunt but first mention of DR dynamic bucket splitting being worked on: https://forums.chaos.com/forum/v-ray…69#post1137269
Apart from me being around since Vray 1.49 and looking at the dates of the changelogs and releases lately, I have the impression it’s slowing down with resources being pushed to the newer acquired products. Granted I was also disappointed with the release of the latest hotfix as well. No harm intended all in good faith ;-).
Right, but that was hardly a promise of any sort, now, was it? 
It turns out neither of the methods was truly viable, and nothing else was available to solve the issue..
Things like this then have to stay parked until a solution is found, it’s not just a case of working harder (or not!) at it, and in this specific case the DR part has to play ball too, which isn’t a given.
It’s RnD, but the D can only come if the R was successful.
On the slowing down of feature releases, I don’t think it’s debatable.
Otoh, it’s not 2005 anymore, the low-hanging fruits have all been picked, and these days finding improvements is absolutely not trivial.
Add to this that supporting open standards (OCIO/Aces, USD, MtlX, etc.) is exceptionally taxing (tons of simple and tedious, and not so simple code.), and a constantly moving target, and you get the gist of why things aren’t as snappy as they used to be.
Yet, to be fair, I feel we have added a wee bit of general performance in the past years precisely “solving” long-standing issues (bucket splitting, adaptivity clamping, firefly suppression, and so on), so while not offended at all by your remark, I don’t think it’s entirely reflective of the quality of our efforts either.
It’s definitely not going to be Chaos’ vMax team to code for Enscape, not to worry.
@Vizioen here’s bucket splitting for DR.
We had to have DR2 working first.
Did I just see on youtube that DR now has adaptive bucket splitting within update 2??
you very much did!
Tears of happiness going down on my cheeks however I’m a bit confused - there is no dispatcher for DR2 in max 2020. I did download latest build from nightlies (33209) and installed and…surprise…no dispatcher in DR window .
Epic Thank you, I’m a bit confused though, in the post about Update 2, it says DR2 is part of another build? Is there a reason why I wouldn’t install this build?
The choice is for the sake of compatibility, and user freedom.
If you have the time to test it because you’re not in the middle of a production, go for it without second thought.
However, it being a first public release of DR2 for Max, it’s likely wise to give it a wide berth if you’re swamped with work right now and would rather not risk having to debug, or simply re-learn, something.
Max 2021+ for DR2, sadly.
2020 isn’t officially supported anymore (not our choice either), so (big) new features won’t come for it.
I guess it’s about time to jump to newer version. I can’t miss that feature, I’ve been waiting for years for it Thanks for an explanation.
Ok thanks Lele