- Feb 4, 2018
- 1,895
- 10,092
Nope even with the geometry tool not selected it doesn't fix my problem but I didn't know that could mess with the genital part thanks for the tips
- Feb 15, 2017
- 612
- 14,513
Hi all. My first post here. After lurking for a while and going through almost this entire thread, I finally decided to download DAZ and see if I could do it. The last 6 hours have been an adventure. I've gone through the first 2 tutorials in DAZ and created 7 renders. Gonna post them (hopefully using the spoiler tags the correct way).
So then I got frisky. Decided to try some of the "move my POV and the model parts around" adjustments. Nothing else...no messing with lights, etc, yet. I'm gonna tag these NSFW, but the purists here will realize the models are still missing some parts (*cough*) yet.
Lots of room for improvement, but I was honestly surprised the way they rendered. I didn't expect what I got for the first time doing it.
I did run into one issue I can't figure out how to "fix" though. And I have searched this site and the DAZ forums, and the info I saw is confusing to me, and outright conflicting depending on who says what. I have the hardware to do IRay, but my renders never use my GPU. CPU goes 100% right from the render start. I've seen all kinds of "this is the problem" posts spread out over the past year-ish of posts, and I'm not sure what I should try right now. The 7 renders above average between 3 to 7 minutes render time, and I'm not even sure if that is "average" for just using my CPU right now. Anyhow, here's my computer specs:
Win 10 Pro 64
i7 6700k 4.00GHz (OC'd to 4.20GHz)
GTX1080 (8GB)
32GB RAM
etc, etc
I've monitored Task Manager during the renders and the GPU memory never goes above 6GB during a render. So...
It shouldn't be a hardware problem. I use the computer for state-of-the-art simulation software (flight sims and racing sims) and it never cuts a sweat. The "help me" posts I've seen seem to be divided between it being an nVidia problem...or a DAZ problem...or a driver problem...or an "I just got out of the wrong side of the bed today" problem. I did IT in the Air Force for 26 years, but I admit even after researching a solution, my head is still spinning. I'm gonna assume some (many?) people here have encountered the issue and solved it. What is the "best" way to go about it for now, without just "flipping a coin" and doing something that ISN'T necessary? Appreciate any insight.
Looking forward to learning more (lots to learn yet) about DAZ and contributing more render posts here.
You don't have permission to view the spoiler content.
Log in or register now.
So then I got frisky. Decided to try some of the "move my POV and the model parts around" adjustments. Nothing else...no messing with lights, etc, yet. I'm gonna tag these NSFW, but the purists here will realize the models are still missing some parts (*cough*) yet.
You don't have permission to view the spoiler content.
Log in or register now.
Lots of room for improvement, but I was honestly surprised the way they rendered. I didn't expect what I got for the first time doing it.
I did run into one issue I can't figure out how to "fix" though. And I have searched this site and the DAZ forums, and the info I saw is confusing to me, and outright conflicting depending on who says what. I have the hardware to do IRay, but my renders never use my GPU. CPU goes 100% right from the render start. I've seen all kinds of "this is the problem" posts spread out over the past year-ish of posts, and I'm not sure what I should try right now. The 7 renders above average between 3 to 7 minutes render time, and I'm not even sure if that is "average" for just using my CPU right now. Anyhow, here's my computer specs:
Win 10 Pro 64
i7 6700k 4.00GHz (OC'd to 4.20GHz)
GTX1080 (8GB)
32GB RAM
etc, etc
I've monitored Task Manager during the renders and the GPU memory never goes above 6GB during a render. So...
It shouldn't be a hardware problem. I use the computer for state-of-the-art simulation software (flight sims and racing sims) and it never cuts a sweat. The "help me" posts I've seen seem to be divided between it being an nVidia problem...or a DAZ problem...or a driver problem...or an "I just got out of the wrong side of the bed today" problem. I did IT in the Air Force for 26 years, but I admit even after researching a solution, my head is still spinning. I'm gonna assume some (many?) people here have encountered the issue and solved it. What is the "best" way to go about it for now, without just "flipping a coin" and doing something that ISN'T necessary? Appreciate any insight.
Looking forward to learning more (lots to learn yet) about DAZ and contributing more render posts here.
- Feb 4, 2018
- 1,895
- 10,092
If u want to use your gpu only
Daz will switch if to the cpu if the gpu can't keep up (like a scene with a lot of light and/or a lot of textures, or that you have stopped a render manually and it is still running, yes sometimes rendering continues in a vacuum. The 1080 is super limited)
If it is, your cpu will work better(Better to keep the fastest).
It changes only for the iray whether it's cpu or gpu for the rendering, the only thing nvidia cards do is this:
Afterwards if you want a specific driver for the rendering ;
You must be registered to see the links
Never had any problem with this driver and I've been using it for several months, even on video games.
Last edited:
- Aug 1, 2019
- 651
- 8,512
Something completely different for a change:
- Jan 26, 2018
- 98
- 432
Hmmm. OK, my installed DAZ version says "Pro" while yours says "Pro Public Build". I did have both the CPU and the GPU boxes checked. But there is another box on mine...the "OptiX Prime Acceleration" one. Even with that checked I noticed in the DAZ log I was getting the following error messages after renders finished:
"2020-01-11 03:25:47.139 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.0 IRAY rend warn : The 'iray_optix_prime' scene option is no longer supported."
Now...after I have unchecked the CPU box like you recommended...I don't get that warning anymore shown in the log. AND my CPU usage during a render only goes to about 28% instead of 100%. BUT my GPU STILL shows (in Task Manager) it's only running 1% - 2% max during the render. And the render takes the same amount of time as before when my CPU was crunching at 100%. So I'm totally confused right now.
When DAZ is using the GPU in "IRay mode" (for lack of a better term), I assumed the GPU would be showing something like 100% crunching. Is that a misunderstanding on my part? I can't reason why my renders would take the same amount of time right now with no increase in the GPU utilization, but a reduction of the CPU utilization from 100% to 28%. How much
GPU utilization would be considered "normal" during IRay rendering?
I need more coffee.........
Here's my DAZ GUI screen. It's the download I got from the DAZ site about 8 hours ago. Should I have a "Pro Public Build" too?
(PS - Thanks for the CPU box heads-up. I didn't know about that)
EDIT: Here's what my Task Manager shows during my renders now, along with the render progress window.
Last edited:
- Dec 18, 2019
- 207
- 981
- Jul 8, 2017
- 62
- 862
2 hours to render but im happy with the result
- Jun 28, 2019
- 184
- 3,964
Don't trust in what the task manager is showing you. Get another programm like HWmonitor or MSI Afterburner and you will see that your GPU is working when you render. I think the taskmanager can't see the Cuda cores(which are doing most of the rendering work) or something like that.
Also if your whole scene is bigger than your VRAM, DAZ will switch to your CPU and RAM for rendering. (At least thats what i read somewhere)
- Sep 27, 2018
- 1,877
- 17,370
- Apr 18, 2018
- 359
- 2,671
- Mar 29, 2019
- 143
- 2,718
Actually managed to blue-screen my rendering rig (first time in four years), so ... a picture with zig-zaggedy hair shadows:
- Jun 2, 2017
- 6,507
- 57,089
You don't have permission to view the spoiler content.
Log in or register now.
And yes, before you say it, her eyes aren't aligned perfectly with the camera xD
Also, I don't think I already shared this here.. I hope.
- Aug 4, 2017
- 610
- 10,627
- Jun 28, 2018
- 65
- 649
