Adding to Cart…
![](/static/images/logo/daz-logo-main.png)
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Stuck in the [situation] too now... This is so [blooming] irritating and seems to be an expected part of life when you use DAZ 3D, NVIDIA GPU cards, and Window platformed machines. You just have to except every 6 months, the [stuff] will stop working because one of the 3 will make an update that [messes up] the workflow of making pretty in DAZ. Leaving us users, in group guessing game forums trying to solve an issue we didn't create and have no chance of really solving as a group because each of our machines is as different as snowflakes on a ski trail.
So everything was working great in DAZ and then about 3 weeks ago "I suspect" about the time of a system auto-update. Everything stopped being great in DAZ. The GPU will redraw scenes in DAZ as I rotate camera views and such just fine. But if I now render an image, it defaults to the CPU, making the computer a lobotomized idiot, that can only sit on my desk, drooling on itself till the image has finished rendering.
I think the last time, this [business] happened. I had to do a clean re-install of DAZ. ...damn....
Your right. I think someone's PC or MAC configuration may play into it. As mentioned I had a strange glitch on the 1st render where the render window was still showing as rendering but had stopped in the DS viewport. I Just had to cancel and resume but did not happen in the following renders...
I'm seemingly rendering in CPU. Have RTX 2070 Super. Installed newest studio driver. My renders are slow slow slow ... Task manger shows full CPU use... But when I go to performance, it shows CPU 14% utilization and GPU 0>1%. The memory being used is around 6gig. The GPU has 8gig.
Renders that used to take 15>20 minutes now taking a couple of hours.
I was just coming here to post a new thread but forund this one,. I'm not even sure I have my settings correct in DS to utilize the GPU.
First you need to check the advanced tab under render settings and make sure the GPU is selected and the CPU isn't.
GPU-Z is the only reliable tool I've found to show what's really going on with your GPUs. If you are watching the sensors display you can see the memory fill up and then dump if exceeded.
Tom
something going on though... when I 1st bought this system, I could render 3-4 chracters, total in a scene in under 10 minutes..I have a render going right now, a portrait..character, no clothes, and hair --It 70% complete @ 19 minutes. AMD 3800x 16 gig ram, RTX Super 2070 OC
daveso, Yeah, I'm in the boat as you right now. DAZ/GPU/OS use to render complex images w multiple characters and props in quick order and within the last 3 weeks or so, something changed
Here is what I found works
Keep your textures Low as they use up 90% of the VRam (In most of my cases)
Keep CPU selected
I have noticed the my GPU does not run unto issues when I still have this selected. CPU is rarely used even when selected as long as my textures don't use up the GPU's memory.
Errrr renders much faster on game ready drivers in my case..
? CPU is always used at max when selected.
I have a ticket in on this, so we shall see
Windows mandatory updates have a nasty habit of putting the default windows driver in place of the NVIDIA driver.
There was recently (May) a big mandatory windows update. Get the latest driver directly from the NVIDIA site and download and install. Don't rely on windows. (latest Daz update needs 440.-something I believe? i'm running 441.66 on a 2080ti.).
I believe Studio or gaming driver is no real difference, gaming has more frequent updates so you can play all the latest games. Studio is tested (and I beleive Daz Studio is one of the programs tested) for various graphics applications. Either should work, as long as you have a recent enough version (for newest release of Daz). If you're not playing games, I'd go with Studio, but take that as 2 cents.
Mine will use the GPU's I have selected first. Only when I go over my VRAM limit will it use the CPU that I have selected I also use Precision X1 to monitor my GPU and adjust power and fans when Needed. I also noticed if I keep my fan Curve high that I have a less chance of a render crash too. GPU 1 will show 1980MHz and GPU 2 will show 1780MHz when rendering which on average completes in 10 min VS CPU which completes in an hour sometimes 1.5 hours.
That is not how it works. If you select CPU, or any GPU, iRay tries to use every selected processor for the render. It drops GPU's if the scene exceeds the card's VRAM. If the CPU is selected it always uses the CPU which always results in the CPU fully loaded during the render.
You probably haveCPU deselected but don't have the "disallow CPU use" selected.
This is what my Log Shows when I render with all 3 devices selected.
During the whole render it is using my GPU AND my CPU (even after all the fails) BUT if I don't have CPU selected the GPU render fails or falls back to CPU ONLY and the render time increses
It says right from the start that it is using a 1080 ti, 1080 and CPU. It's not dropping to CPU but using it from the start.
The same lines from my most recent render:
2020-05-19 11:50:38.103 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 2 device(s):
2020-05-19 11:50:38.109 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce RTX 2070)
2020-05-19 11:50:38.109 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (GeForce GTX 1080 Ti)
2020-05-19 11:50:38.109 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
Although if that scene isn't pretty big you have some other issue going on. You have a whole bunch of out of VRAM errors.
Only 190 iterations in over 4 minutes does seem to say both GPU's dropped and used the CPU but it was going to do that from the start.
I only needed 190 iterations to complete the scene render. Turned out very Beautiful too. its a low resolution render 1920x817
at 154 iterations the render was already at 89% complete before the multiple Errors. and yeah the scene was Huge with 1,171 textures and 243,000 triangles
if it was not for the memory leak issue It would never fallback to the CPU at the end. Daz needs to fix it to where it does not have to reload the render multiple times during one session which fills the VRAM up without clearing the cache first
The memory leak is between renders not during it. You have something going on that isn't that.
While polys does take up VRAM it isn't very much and having lots of textures is also irrelevant. The dimensions of those textures are what really matter. A 1k texture is 1/64th the size of an 8k one.
But this was about your claim that your CPU was only used when the GPU's dropped. That is clearly not the case based on your own log.