Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
At least your getting something. Doesn't seen to matter to me, CPU/GPU, GPU or only CPU it all hangs up for me. Re-saving the textures has actually made things worse. Before DS would simply stop responding releasing all my cores and video card while the program continued on counting off time and acting like it was doing something when it wasn't. Now with re-saved textures it actually takes over and locks up my whole system. Might help troubleshoot the problem but it isn't a short term solution. At least it's not for me. The one thing that I have found helps is changing the position of the lights or camera. Sometimes that helps, sometime it makes things worse but it is having an effect one way or another. I know DAZ and Nvidia are working on a solution, and this is a beta after all, but in the mean time with no way for me to do decently sized promo quality work, my production has come to a screeching halt
I feel for you and it is extremely frustrating! Especially since the new shader system is so much fun to explore and with every scene I get better results. What sometimes helps for me is to restart Studio before the final render, memory seems to stack every action done in the scene and with a fresh restart the scene takes not so much RAM.
We only can hope that we can use the power of our machines fully for quality renderes in a reasonable time. Untill then I do basic work, saving shader presets and materials for later use! :)
Yes, I've noticed that. There is even a note that appears in the log file sometimes that continually stopping renders in progress will degrade Iray performance. So saving and restarting definitely helps. The most frustrating thing is while I've saved all my materials and presets so I'll have access to them once this is all fixed but I've had some absolutely amazing looking renders going that have just gone poof and your left sitting there with nothing. If I'd only known iteration 3112 was going to be the bad one before hand I could have done something but now it's to late. I could restart while setting the samples lower and probably get a result but the whole thing is kind of heartbreaking.
I had to make this experience with my last render here in the galleries featuring my Body Jewels, Iray doesn't seem to like the Geometry Shell somehow, I had the render baking overnight and it looked stunning after 8 hours in full size. But my whole system was frozen and I couldn't reach the image with 10.000 iterations - and poof, it was gone. I restarted the scene in smaller size to at least get a hint of how it could look. Grrr. The whole day I was in a bad mood! :( I tried out different scenes with different setups for the Jewels, but no success at all to get a decent image out of it. If only this would be the only scene I had problems with!
I have this problem too. 8GB of RAM, 3.5GB used by DAZ during render. CPU rendering (AMD card). Freezes at 96% convergence (Iteration 1921 in my scene: Mei Lin 6, Stonemason Rogue suit, Xanadu Hair, 3 Photometric spotlights).
It reaches 100% convergence when I spot render but not rendering the full sized frame.
The hair is noisy until 98% convergence (I know fibermesh hairs render a lot slower even in 3Dlight, but I want to use them if possible).
I've gotten into the habit of having IrfanView open and set to do screen captures. If the rendered image fits completely on the screen, it's easy to grab a capture of it, if and when the render hangs. If the image is larger, I'll capture it in chunks as the render goes along, just in case the sliders don't work after the render hangs. I might end up with several versions at various convergence percentages, but it's better than losing all my work.
It's not a perfect solution, but it's better than nothing...
It's been mentioned in another thread that switching Instancing Optimisation from Memory to Speed helps a lot. I just tried it with one scene and it seems to have helped. I'll try it with a more problematic scene tonight.
ADDED: Nope. Crashed Studio after 6 minutes of thinking about the render. Bedtime.
So many of us are having issues with the render just stopping without any indication it stopped. I spent some time making the renders hang while having the Windows Task Manager open. Every single time the render stopped, the CPU usage dropped from 100% to 50% and stayed at 50% until I used Windows to force DS to close. I'm sure there are other utilities to keep track of the CPU usage, and having one running while doing a render would make it pretty easy to see if it's still rendering. And if you haven't hit "cancel" on either window, you can still scroll the image to do a screen capture, if you need to. After you hit cancel, scrolling won't work. Based on my Windows machine, anyway.
There is a known issue with Iray for items that have intersecting Trans maps. I understand Nvidia is working on it. Somewhere else I read it wouldn't hurt to report it as a bug. I suppose the more reports about the problem, the more important it will be to fix it. Squeaky wheel, and all that...
The image I used to test the resources includes hair that causes the render to hang. If I remove the hair from the render, it works just fine. Changing the hair isn't an option for me as it's part of the character's description in the book. (My avatar is that character, and that curly red hair is what hangs the renders.) But it could be a viable option for many of you. Certainly worth a try.
Besides some hair objects, I've read ivy, (with all those intertwining vines and leaves,) and feathers are having issues with the intersecting trans maps. I'm sure there are other things as well.
As frustrating as it can be at times, I'm still really pleased with the results using Iray.
Thanks for the ideas and advise everyone :-)
For me, I've never been able to pin down one exact cause. Some scenes work, some fail, some fail but can be fixed but no one defining element between them. From the (very) little hard info I could get from the Dev. Team there might be more than one reason behind the program hanging up. Nvidia is working on fixes but ETA is unknown.
What I've been doing is I switched to GPU only rendering. It's much easier on my system and DS will respond even after it has hung up. Unfortunately that requires two things, one is a good enough video card that can handle it and the other is software that can monitor your video card's activity as the trick of watching your CPU activity won't help here. I downloaded a little program called GPU-Z, On it's sensors tab it monitors and displays what my GPU is doing. After much trial and error I noticed an entry for 'Memory Controller Load' When I start rendering it jumps up to 70% +/- and pretty much stays there until the program hangs (or the render actually finishes :bug: ). When i see the load drop I can tell DS to stop rendering and then I can save the result and continue on using DS without issue.
I was having a similar problem and someone recommended this...
And it seems to be working.
That one has been plaguing Iray for a while now...I hope Nvidia can get it fixed, soon...well, sooner than the DSM bug in 3DL.
That one has been plaguing Iray for a while now...I hope Nvidia can get it fixed, soon...well, sooner than the DSM bug in 3DL.They believe they have it fixed, once we get the build from them, which has other things in it too, we'll know. :) Remember we are only one consumer of this Render engine :) and they want to have time to test it on their end before putting out a Release Candidate.
Ugh, this has been driving me crazy all day.
I don't mind hanging/crashing.
But not knowing if you've hung or crashed?
That is the worst. :)
I will be very happy when the fix makes its way to us.
Until then, I will play musical textures to get this last render done.
Ive been occasionally watching the Iray forums...there are lots of people waiting for this to be fixed. We think it's bad for some things...it's really bad with certain plants. And if archviz is one of the strong points of Iray and it can't render vegetation....
I always have the Task Manager on top showing the System Performance tab. If any of the CPUs go to zero usage (usually around half of them) I know the render's hanging.
Hi there
I've had a bit of experience with these external/internal renderers (Indigo, Renderman and Lux). I tried out Iray and come across similar difficulties. The best solution is not to get caught up thinking using both CPU and your GPU to do the job will be quicker. As it will only push your CPU to 100 % and your GPU will be practically idle. This leaves little reserve for the CPU to process data and therefore hang Uncheck both the CPU boxes in the render settings to force the dedicated GPU to do the work its designed for, thus leaving the CPU to send the data and hopefully avoid the hang. Tested this in Daz and it has made all the difference so far. Before these settings 7 out of 10 modest scene renders hang, after ........... No hanging
For complex scenes - Render in layers and compile in Photoshop or similar
You would really want Nvidia GTX750 2GB and above, or at the very least the X and the second digit 5 or higher
New Nvidia driver update 347.88 seems a reliable patch too, so advisable
When an Iray render hangs up along the way but the render itself looks good....... is there anyway (besides a screen print) to save the render before canceling the render. I liked that Lux did regular saves of the render as it was processing.
If you can do GPU only renders you can cancel the render and save the result even after it has hung up.
Oh... well maybe when I upgrade my computer.... currently have a different brand and less powerful graphics card... and my power supply wouldn't support a more powerful card anyway... thanks for the info on that.
Then maybe you should give a try to some different render after a little? Of all I know to the moment (do not suppose this as an ad) Thea Render is promised to support not only early promised OpenCL video cards along with present CUDA enabled devices (CPU support is default) but also Android powered devices. Something similar is going on with Octane Render. I do not dig deep about other renders as I have licenses for these two ones and have no need to switch to any different render. Well, maybe modo's built-in render as 701 is my modeling software.
And it seems to be working.
I had the same Problem for the first time today. It kept hanging on iteration 16. After I found this post, I changed the Setting to "Speed" and now it Looks like the render is going through, it's up to Iteration 153 (50%) right now. Thank you for this advice!
EDIT: It worked fine, all the way through!
When it hangs up for me, and I try to stop the render, it won`t respond anymore. DAZ Studio just keps canceling the render forever and ever and I have to force it to close, losing the render of course.
Yes, when it hangs, nothing works anymore. But try restart DAZ and then "save last render", if available. It should bring up the render again.
EDIT: Not sure if it works, but it's worth a try.
Newest beta version seems to have cured the issues I was having with Iray hanging up during rendering.
Well, I hope that`s the case! I will try the newest version with the scene that I could never finish. :)