Any way to setup Iray render to take longer but not use all ressources?
![statistx_42556c1853](https://secure.gravatar.com/avatar/a62332d38ebf15dafb0b906072974375?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2Fa62332d38ebf15dafb0b906072974375_100.png)
Not sure how to summarize, but my issue is, that I have a mid tier PC setup and occasionally the renders slow my PC to an almost standstill.
Is there a way to setup the render that it takes longer, but does not eat as many ressources at once? I don't care if it takes longer, but at least it doesn't almost force me to hard reset.
Comments
You can make sure to hide anything out of the way of the camera (click the eye icon) to reduce load.
And/or use something like this https://www.daz3d.com/resource-saver-shaders-collection-for-iray
That sounds like your render has dropped to CPU. You need to be aware of how much VRAM your graphiocs card provides and get a feel for how much can fit in that.
You should make sure your CPU is not selected to be used for rendering all the time as well.
Two ways: Start Studio and Task Manager. In Task Manager -> Processes right-click on DAZStudio.exe. Now - method 1: and select 'Set Priority' and then 'Below Normal'; now anything at Normal or above will get preference, but Studio will use everything available if nothing else is trying to run. Method 2: select 'Set Affinity'; this lets you choose which CPU threads may run Studio; any NOT selected will be available to all other processes. The downside to Method 2 is that it permanently prevents Studio from using all processors if nothing else is trying to run.
I prefer method 1 - among other reasons, it can be added to the desktop shortcut used to start Studio. (If you do this, apply it to a copy of the shortcut so it doesn't get deleted every time you update Studio).
Thanks, but the issue is when I have too much to show. If I don't have enough in the scene, there's no issue, but I'm talking about bigger, fuller scenes.
Thanks, but I made sure CPU is ticked off in both windows on the advanced settings. I also turned off Optitex, cause I read in the past that it might slow everything down, but maybe I'm wrong here?
Thanks, gonna try method 1 (sounds more interesting than 2, I agree)
I now figured out through Task manager, that my MEMORY is gettign maxed. I have 12 GB RAM. CPU and Disk is fine, I might have some wrong settings, cause 12 GB getting maxed out when using a GTX 1060 6 GB seems a little excessive. Any idea if there are settings regarding that?
Just because unchecked the boxes does not mean your renders won't drop to CPU. If your machine is slowing down to where it is unusable then it is almost certainly rendering on the CPU.
12 Gb is not a lot anymore. I use an 8 Gb 1070 and upgraded my RAM to 32 Gb because I was maxxing out with 16 Gb. When you are working that tight, make sure that you have closed down all other applications when using Daz Studio, especially Chrome.
All that does is ensure that the CPU is available for other tasks (like surfing the net for PRON or asking n00b questions on Daz3D forum) while rendering PROVIDED THAT THE SCENE FITS ENTIRELY WITHIN THE AVAILABLE VRAM. If the scene is too large the render will fall back to CPU, regardless of whether or not the CPU box is ticked. If it didn't, the render would simply stop and you'd be left staring at a partial render, wondering WTH it never finishes.
The current Public Build has added an option to tell Iray not to drop to CPU if all selected GPUs fail.
If the scene doesn't fit on your 6GB GPU card (Fast) , it is rendered with your CPU (slow) So you want your scene to fit unto that 6Gb card. So all textures, geometry need to fit the card.
In those case you need to optimize as others mentioned. Either reduce geometry, or reduce textures. You could use scene optimizer https://www.daz3d.com/scene-optimizer to reduce texture maps. You won't notice a difference for anything a couple meters / feet away.
Keep an eye on the changelog - Rob says there are chnages in 4.12.1.81, though they still need work as he can fit it in to put them in the UI.