Render Restarting from Beginning
AgitatedRiot
Posts: 4,404
Render Restarting from Beginning
Scenario: While trying to render the below scene. It would start to render then get about 56% convergence. Then it would start to render from the beginning to about 56%, then again.
Step 1: I took to correct the problem. Save the scene. Close DAZ. Waited. Restated DAZ. loaded scene. Render same.
Step 2: Close DAZ restarted Machine. Open DAZ. Then I loaded the scene, hit render, the same.
Step 3: Reinstalled Drivers. Same
Step 4: Uninstalled DAZ with DAZ Central. Reinstall DAZ via Dim Content was still installed. Just had to install the default set. Then loaded the scene, same.
Step 5:Rebuilt Scene same
Step: Last resort Since I don't want to bother others on these forums. Since my Mantrum about support. IMHO is lacking. Wiped Drives reinstall OS and DAZ via DIM Working
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Without having a look at your log, I'm assuming your GPU is running out of VRAM. Or your GPU driver needs updating.
Do you have the CPU enabled and CPU fallback enabled?
That usually fixes this.
If not, then please attach a copy of your log of the failure.
You can open the log in notepad or whatever, clear it, then save it empty before you start the render to just log the render.
I'm working with the same scene. Not one problem. With rendering.
There is a reason I put the bold type in the sentence is that some one told me it's better to report it to support. If I open that can of worms in these forums again, will just get me in trouble.
I did nothing out of the ordinary DAZ when Daz started doing this. The system was stable and running fine.
v4.16.1.47 Public Build - Nvidia Studio Drivers v512.15 March 2022
I'm seeing something like this. When I try using the Iray preview, the preview pane flicks to the "silvery" look, as normal, then an Iray view appears for half a second, then it flicks back to the "silvery" look.
It flips between the "rendered" look and "silvery" about every 10 seconds or so, but it's useless for previewing lighting.
No errors are displayed in the log, but I see multiple lines like this once the "IRAY rend info" lines begin to be reported in the log.:
2022-04-02 06:32:02.985 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
I usually see just one line like that, at the beginning of a render or Iray preview, but these are reported multiple times, as if something is stopping and restarting.
Some example lines at the start of a preview:
2022-04-02 06:29:17.057 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : Light hierarchy initialization took 0.011 s
2022-04-02 06:29:17.075 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Scene processed in 7.354s
2022-04-02 06:29:17.076 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
2022-04-02 06:29:17.077 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 1.906 GiB of work space (2048k active samples in 0.000s)
2022-04-02 06:29:17.077 Iray [INFO] - IRAY:RENDER :: 1.11 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Optimizing for cooperative usage (performance could be sacrificed)
2022-04-02 06:29:17.179 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 7.449s.
2022-04-02 06:29:17.184 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-04-02 06:29:17.189 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-04-02 06:29:17.190 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
2022-04-02 06:29:17.411 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 7.676s.
2022-04-02 06:29:17.418 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-04-02 06:29:17.420 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
2022-04-02 06:29:17.533 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 7.798s.
2022-04-02 06:29:17.582 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-04-02 06:29:17.585 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
2022-04-02 06:29:17.702 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 7.966s.
2022-04-02 06:29:17.740 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2022-04-02 06:29:17.742 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 3090): Allocated 20.855 MiB for frame buffer
2022-04-02 06:29:17.857 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00006 iterations after 8.119s.
2022-04-02 06:29:17.882 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
What's weird is that a regular render seems to proceed normally. It's just the preview that became useless.
Update: False alarm, apparently.
An object in the scene apparently caused Iray to stumble. One of the https://www.daz3d.com/new-york-tenements-2 buildings. I removed it, and the Iray preview went back to normal.
This seems weird, because I've used those buildings in multiple renders. Ah well. Technology!
There seems to be an issue in the new version of Iray that is included in DAZ 4.20. When the scene being rendered is very near the vRam limit of the GPU it want's to switch back and forth between GPU and CPU causing it to restart each time that happens. I think it's a byproduct of a change meant to help clear vRAM between renders and likely will be fixed in the next version of Iray that we get.
From your screenshots it looks like that is what is happening to you. I have "solved" this problem for myself by disabling GPU and enabling CPU for these specific renders. It takes a lot longer, you may want to change the Time Limit for your render, but at least it gets the scene rendered eventually.
You could likely reduce a texture or two and get the scene rendering on GPU only, which would obviously be much faster. Maybe even try using a viewport style that uses less GPU resources than Filament.
Well, that makes sense. The scene rendering takes about the VRAM 11.6 of the 12 GBs I don't know exactly how much Win 10 takes off 12 GBs. I do know that at 11.8 GBs the Graphics on my machine drops to the CPU.
I personally noted that having the caustic sampler ON takes a hell of a long time if you dont really need it in your scene. Esp if you have atmospherics On and only the Sun and sky lighting On. Does this make any sense?
Caustics depend on light: the atmosphere, shiny surface, and diffused surface. The photons from the sunlight will then bounce off surfaces or be absorbed. The bigger the scene more bounces and more extended calculations. Which will slow the render. Yes, your statement makes sense.