Larger Files Will Not Render Without Enabling CPU

jefelito5150_c27c0a0e88

I've updated Daz to the most recent download.

I'm running:

13th gen intel core i7-13700F 2.10ghz

32gb RAM

Windows Home 1123H2

NVIDIA GeForce RTX 4070

After updating Daz, I opened an older, large file, attempted to render in IRAY, the render runs but it never gets to 1 iteration before the render just quits and gives an empty image. I render with the CPU unchecked and let the GPU do all the work, but now I'm finding, for larger files, it will not render unless I enable the CPU and that seems to ignore the GPU completely. The task manager shows the CPU at 100% and the GPU at 0%. I haven't had this issue with smaller renders, just larger files.

i am accepting all ideas and suggestions. Thank you in advance.

JT

Richard Haseltine

Different versions of Iray require different amounts of memory, generally newer more than older. It is likely that your large scenes (just) fitted before and now don't. Reducing texture sizes (e.g. with Scene Optimiser or just manually) where possible may fix this.

alan bard newcomer

windows home might not handle things the same as pro?

 

CES3D

It seems that the scene data exceeded your GPU's memory capacity.
Daz Studio isn't very good at freeing up GPU memory, so when rendering large scenes, it's advisable to restart Daz Studio to ensure the GPU memory is fully cleared before starting the render.
If the scene still exceeds the GPU's memory even after restarting, as Richard suggested, you might want to try reducing the scene data using a tool like Scene Optimizer.
Another option is to utilize a remote Iray Server such as Boost for Daz.

alan bard newcomer

will the 4070 work with older dazs? 
And whats the difference in output between the 4070 on daz 423 or daz 421?

 

jefelito5150_c27c0a0e88

So it may have been an issue with the file itself, I recreated it from scratch without touching the textures or resolution and it's rednering, in Iray like normal.

So far Win 11 Home and the 4070 seem to be working okay, which is great because I didn't want to upgrade either.

 

Thank you all,

JT

Padone

There have been reports that 4.23 has issues opening old scenes, while new ones work fine. This may be another case. Having to recreate the whole scene in 4.23 to make it work is of course not acceptable, unless the issue is limited to this single large scene, in which case it may be a corrupted file. Let us know so this could help the daz developers.

jefelito5150_c27c0a0e88

Also I had, somewhere betweeen then and now, quadrupled the DPI and didn't eve think to look when I opewned the old file. WHen saving, I didn't save the render settings so I'm pretty sure it was trying to do more that it could handle.

Thanks again for all the great suggestions.

 

JT

jefelito5150_c27c0a0e88

Also it absolutely needs the "Save", "Close", "Restart the PC" "Launch", "Load" then "Render" and that seems to work.

I added another figure and it started the same symptom described above, I saved and did all that and now it's rendering without ending the render with a blank image.

Bug maybe?

JT

alan bard newcomer

jefelito5150_c27c0a0e88 said:

Also it absolutely needs the "Save", "Close", "Restart the PC" "Launch", "Load" then "Render" and that seems to work.

I added another figure and it started the same symptom described above, I saved and did all that and now it's rendering without ending the render with a blank image.

Bug maybe?

JT

daz is known for not clearing buffers well so restarting resets them

 

jefelito5150_c27c0a0e88

I was kinda off... shut the PC all the way down, turn it back on, first render will be quick, next render will be slower, when the slowness gets to be too long, shut the PC down, start back up and repeat. I don't suppose that could be fixed? Anyone from Daz reading this?

JT