Spot Render taking really long
scullygirl818_02147fecb6
Posts: 170
So the full render for my 2400x300 took a couple hours. A tiny spot render was on 1hr+ and like 30% or something. I found a post about this, but I don’t think if I post on that thread anyone would notice, because it was marked solved. There it said to make sure the viewport was not on Iray, which may be a problem, but I don’t know what I change and where.
I also read the suggestion of starting the full render and then cancelling it, but leaving the render window open before the spot render. I attempted to keep the cancelled render open, but each time it’s opening a new window for the spot render; I’m not sure if it’s supposed to do that.
It i lately seems to get to like 30 percent or something fairly quickly (I restarted it leaving the other render open, and so far it’s at 23% around 20 minutes), but at about 30% it looks almost complete, but then just keeps going and takes a long long time to move higher percentage, but looks more like its the last 5 percent that is left if that makes sense, rather than 70% left.
ETA the window didn’t seem to help. It’s at 56% and 1 hr 45 mins. That seems way too long for a spot render. I’m tempted to restart my computer, but then I’d have to wait again if it does it again.
I have a i7-7700HQ CPU @ 2.80 ghz with 32gb RAM Windows 10 Pro 64 bit with and NVidia Quadra P3000 video card (though DS won’t run unless I disable it and run the Intel(R) HD Graphics 630 (some programs do this I wish I understood why it seems like it should be using that.
I’m right now still trying to do the spot render to see if leaving the window open helps, which it seems like it might be. It just seems like the longer I have used DS since I booted up the computer (3 days now; I just hibernated each night and went back to working) that it’s slower rendering. It keeps locking up and I can’t move the mouse for bits at a time. Three days ago I was running photoshop while I left it rendering.
ETA leaving the window open didn’t seem to help. It’s at 56% and 1 hr 45 mins. The full render took somewhere between 2-3 hours (Can’t be sure exactly, because I left the house, but it was done when I came back) That seems way too long for a spot render. I’m tempted to restart my computer, but then I’d have to wait again if it does it again.
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
I cannot help you but I made the same experience. The spot render takes too long to make sense for me. I think it is calculating the entire scene during the render time... And never, never run another thing while rendering. Especially PS is the biggest RAM eater....
Are you doing this tio deal with a small area that was still noisy in the original? If so then this is the expected behaviour - you need to do it because the rest of the image converged relatively quickly and so the percentage complete rose fairly briskly; now you are concentrating on the remaining area the proportion of quick-converging pixels is much lower, and so the progress is slower.
Sorry, I'm trying to understand what that means. It's rerendering the same area though that was in the original so why would it take as long as the full render? Or do you mean it's possible the full image was timing out?
This is why I'm wondering. This last spot render I paused last night and resumed this morning. Apparently it didn't have much left to go (although I think it said it was at like 70 so I'm not sure why the rest finished so quickly). At any rate, when I went to overlay the piece in photoshop and looked at 100% zoom, and I noticed something. There is less grain and the quality is better than the rest of the image. I moved the wing, which is emissive, but I don't think it was enough to make a difference in grain because it was lit better. I also added candles, but at the bottom of the scene.
So what I'm guessing is my full render actually timed out? I'm guessing it reached max time and the other pieces rendered 100%? So my question is, how do I know how long to change it to when I rerender so it will all match? Is there a way to know if it is timing out by a log or something? Technically, unless you look at the 2400x3000 image at 100% it's going to be unnoticable, because it isn't a huge difference, but it will eventually be for print, and I'd like it to be the same. Would I be better just brightening the whole scene?
So I thought I had progressive rendering on - but on the render settings, it's grayed out, yet it's options aren't, so I'm not sure what that means.
I'm attaching the render settings and a tiny close up of the part of the scene.
ETA: Not sure you can tell the grain difference, because apparently when it uploaded it it compressed it even though it's small, because they are both much clearer than that.
It's absolutely an increase in quality.I tried rendering the face which is no where near the emissives, and it definitely has less grain. Not sure what to change though or how much.
So was the Spot Render covering the full image, or just an isolated section?
If you are asking did I use the spot render to render the whole image, no, just a small portion where I moved the wing, or in the test I just did I just spot rendered her face.
That's what I thought. Consider a one-hundred pixel square image, with a ten pixel square lump of glass in the middle. Say that the majority of the image takes eaxactly 100 iterations to converge, but the glass take 1,000. On a full render, using 95% convergence, after 100 iterations all but the glass (1%) of the image will be converged, so it wills top. If you now do a spot render of the area around the glass (the tool is tricky to be precise with, so let's say you drag out a twenty pixel square) then after 100 iterations the background will be converged but beacuse that's only 75% of the render area the progress bar will be at only about 80% so it will keep going until the one-thousand iterations needed for the glass have completed.
So how do you render a full image all at once for the 1000 iterations? Because I have no way of knowing what pieces I need to respot render that aren't converged all the way to get the better quality rather than just because something needs fixed. Sometimes that may be more simple to just render in pieces or whatever, but I'd rather leave the full render go overnight.
Also, some of my spot renders are going faster. The emissions I figured would take much longer, and when I do that, that's when I first noticed the surroundings were a bit clearer. This is also likely why when I've done a spot render, they look done way before 100 because the quality of the rest of the image wasn't matching them, which is what I was going by. But not all of them should take hours. Unless, does a dformed item take longer to render? I assumed once it's a still frame it would be the same as everything else. All I know is my other renders didn't seem to be taking so long before, although this is the first time I've added emissions I believe. Also, would it help to make parts invisible if i don't need them for the spotbut I render like the emissives? Because before this one with emissions, a lot of my spot renders on other pieces would be like 15 minutes.
One other question, which I'm not sure you can answer, but I thought my specs were pretty good, but like I said it seemed so much faster previous times. The fact that it is making me use the intel card and not the nividia quadro P3000 be part of the problem? I think before it ran on it, but after a certain point certain programs would crash on it (like Daz) and the video card updates didn't fix it.
You can increase the Convergence Ratio (requires more of the pixels to be converged, but may still stop while smalla reas are unconverged) or the render quality (makes Iray fussier about which pixels it considers converged, so the laggards have more time to catch up). If you have the Public Build, 4.11.0.236, you could also use the new denoiser in some cases (but that may remove details you want).
Generally areas with complex light effects (refraction, reflection, etc.) will take longer to converge, which is why eyes are often a problem area, and so will areas that rely on bounce light rather than direct light.
Yes, Iray will not use an Intel GPU (and if you can't use the nVidia my suggestion about the denoiser won't help - that doesn't work on CPU). If you are having trouble getting DS to see th nVidia GPU check the nVidia control panel - somewhere in there you should find an option to set which applications use which GPU. Also, the 418.x drivers didn't work with Iray - reprotedly the new 419 drivers do, 417.71 certainly does.
check the quality you've set it at in "progresive render" settings the default is 1.0 << "draft" the higher the value the longer it'll take. you can also limit the number of iterations and or the total time a render will be allowed to run in minutes. just remember the shorter the render the lower the quality regardless of aspect ratio
How do I change the render quality? Should I change max time or samples? Since the option itself is grayed out but the options under it aren't (see previous attachment), do I even have it enabled correctly?
By the way, DS is running now though on the video card, not sure why it crashed before. It still however only shows the CPU option.
For the video card, the driver I have now installed is 24.21.14.1181. Windows says it is up to date, which I know half the time means nothing. I went on nVidia and found an update. Is this actually 419 or still 418? on nVidia site, this is the driver I get:
R418 U2 (419.17)
I'm not sure that the driver installed is a completely different number, since I updated it recently, but who knows.
The grey headings in the group list don't mean disabled, they mean that the group is empty (but its children do have properties). Rendering Quality is the penultimate entry in the group in your screen shot - it affects the threshold for deciding a pixel is converged.
Ok, so before I mess with the render settings, that did update the video driver to 419.17. The problem is, it's still not showing up in DS. I'm guessing that I have to turn it on or something for the program, but the issues is, when I try to open nVidia control panel or nview desktop manager, nothing happens. I'm investigating how to fix that, because I'm guessing I need that to set it.
Do you know if there is an earlier version of the driver that will work with DS? I talked to nVidia support for over an hour and they couldn't get the control panel to work. that should have worked - trying to open the control panel from the microsoft store just says the application is not compatible with the installed nvidia driver which makes no sense. They even tried a different driver and windows is updated. They were going to look into it more until I noticed a code 43 error in the device manager so now they are blaming it on something else. I have followed every tutorial I can find and can't get it to load. I tried nvidia inspector profile and it won't load either. The video driver seems to be fine other than I can't run those, which is where I assume you control it in DS.
417.71 is known to work with Iray.