Tweet
So, with very long high-rez still image renders obviously DR really comes into its own. However, Vray still has this issue where certain buckets take exponentially longer to finish than most of the rest of the image, and because DR currently doesn't allow for dynamic subdivision, it's a Catch-22 -- either render on one machine and benefit from dynamic subdivision, or have an overall faster render time with DR but risk getting hung up on a few buckets at the end.
One trick I started using was to turn on Resumable Rendering, allow most of the render to complete with DR, then kill it, disable DR and restart with just one machine to clean up the last remaining buckets with adaptive subdision.
BUT, for some reason this only seems to work some of the time, and some of the time I get this error:
// Error: V-Ray : -1: Buckets don't match (-1)
I am not sure what causes this, but the VFB will also dump the previously rendered section of the image, losing all of the previously completed pixels. Very annoying.
Another workaround used to be using region rendering to complete a half finished render, but at some point Vray stopped saving out the entire image and now only saves the rendered region. This has been the subject of other threads.
Given that Vray is used majorly to render high-rez stills for print, these are all limiting compounding problems. It'd be really great to see the developers properly address these problems:
1) Address the issue of Vray getting so hung up on certain buckets -- why do apparently very similar adjacent buckets take such vastly different render times?
2) Get dynamic subdivision working with DR
3) Fix the problem with the VFB not saving out the whole image when rendering a region. If memory serves correctly, this is how it used to work.
One trick I started using was to turn on Resumable Rendering, allow most of the render to complete with DR, then kill it, disable DR and restart with just one machine to clean up the last remaining buckets with adaptive subdision.
BUT, for some reason this only seems to work some of the time, and some of the time I get this error:
// Error: V-Ray : -1: Buckets don't match (-1)
I am not sure what causes this, but the VFB will also dump the previously rendered section of the image, losing all of the previously completed pixels. Very annoying.
Another workaround used to be using region rendering to complete a half finished render, but at some point Vray stopped saving out the entire image and now only saves the rendered region. This has been the subject of other threads.
Given that Vray is used majorly to render high-rez stills for print, these are all limiting compounding problems. It'd be really great to see the developers properly address these problems:
1) Address the issue of Vray getting so hung up on certain buckets -- why do apparently very similar adjacent buckets take such vastly different render times?
2) Get dynamic subdivision working with DR
3) Fix the problem with the VFB not saving out the whole image when rendering a region. If memory serves correctly, this is how it used to work.
Comment