Hi,
I've just realised I posted the exact same issue 12 days ago (
https://forum.corona-renderer.com/index.php?topic=42676.0) . These last couple of weeks have been a blur due to the workload I have on :( .
Based on the replies in the above topic.
You have to precalculate uhd cache for animations. Here's a link with more info: https://support.chaos.com/hc/en-us/articles/4528617365649-How-to-use-the-UHD-Cache-for-animations-and-stills-in-Corona-for-3ds-Max
If you don't want to play around with that. Then just switch to path tracing, slower but less problems.
We've probably rendered hundreds of animations so know the process but there are those few jobs (this being one of them) that cause a headache.
I've never used path tracing as a secondary solver. We've always used UHD. The results may be better with secondary being at path tracing, but based on the example in that link I can't justify double the render times.
For all animations we use UHD with 'try to load and append' & 'load file'
The increment we use depends on what we're rendering.
For the animation above I'm using Nth = 10 - We generally use 20-25.
For animated cars/people I use between 10 & 20.
We always use denoising for animations (set to Corona High Quality (0.6 - 0.7)). We also use a denoiser in After Effects because we render animations to 6% - 8% (depending on the job).
All of our jobs seem to suffer at the final stage because we work with large developments, lots of vegetation, long animations etc etc so we need to keep our render times down as much as possible. We also have multiple jobs on at the same time with crazy deadlines.
Reading that page it looks like denoising isn't recommended for animations. On the flip side to this, if we turn denoising off we'll need to have our percentage turned right down and that brings us back to longer render times we can't afford.
https://support.chaos.com/hc/en-us/articles/4528617365649-How-to-use-the-UHD-Cache-for-animations-and-stills-in-Corona-for-3ds-Max
Something we've never done is calculate from scratch for every frame.
As mentioned above we render every 10-25, even if we don't technically need to - this comes from years ago where Vray was less forgiving and we had issues.
As we use network rendering (14 systems), would it be advisable to do one or the other of these:
- Calculate from scratch (discard) on each system
- Calculate from scratch (save/try to load and append/load) for every Nth 1 or Nth 2 frame
The second one means that all systems will use the same UHD cache which has a lot more info that we normally create.
Thanks
Recent Posts