Render settings for image series issue

MGMOZ

I am running into issues with render settings when rendering a image Series.

For a scene that I created, I use one camera view that involved a series of 605 individual frames, each image took about 45 seconds to complete.

Using another camera (with same camera settings) in that same scene and using those exact same render settings (this time it's a series of 205 individual frames), each frame is taking over 10 MINUTES to complete!

Could it be to do with the default allocation of my PC's resources by various other programs?

I have noticed that sometimes, if I close and reopen the DAZ3D program, that faster render speed sometimes kicks in but I haven't been able to achieve this so far in this particular case.

In interrogating my PC via the Task Manager, there doesn't appear to be any obvious culprits showing.

Any suggestions?

PS There is a Genesis 9 character visible in that 'Camera 2' position. Could that be a 'slowing' factor?

My PC:
Processor: 12th Gen Intel(R) Core(TM) i9-12900F   2.40 GHz
NVDIA GeForce RTX 3080
Ram: 32 GB
System type: 64-bit operating system, x64-based processor
Window version: Windows 11 Pro 23H2

Those Image Series render settings:
Render Mode: Photo real
Filtering:
Post-denoiser Available ON
Post-Denoiser Enabled ON
Post Denoiser Start Iteration 550

Progressive Rendering:
Rendering Quality Enabled OFF
Max Samples 600
Firefly Filter Enabled ON

 

 

Richard Haseltine

How are the two different? Iray renders contuinue, by default, until 95% of the pixels have reached a settled values - if one camera is looking into shadowed corners, which take longer to settle as fewer light paths reach them, while the othe is looking at brightly-lit areas then the difference is speed would be unsurprising.

MGMOZ

Thanks, Richard. This second camera view was possibly not as well lit. By increasing the light levels, it did improve the speed by about a third. (7 minutes instead of 10+) but still very slow!

After watching a tutorial, I swapped to the Beta version of DAZ and that solved the issue altogether! From what I've gathered, it is to do with the settings and/or interaction between the CPU & GPU.