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.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
Some features i would love to see in a future Daz Studio release, aimed specifically at rendering:
- A toggleable feature to hide and unhide objects and sub-objects based on what is visible from a specific camera view, just like how fps games work, and some "scatter" instancing tools have the option to do. It should work on a layer above the normal visibility setting, so it won't affect the visibility of objects as set by the user. This is done to reduce ram and vram usage during renders.
- A toggleable feature to flush vram memory after each render or in between Iray viewport activations. Some people want their scene kept in vram for animations so it won't need to reload after each frame. Others would simply like to reduce vram load after discovering its full causing CPU switchover rendering (without needing to restart Daz Studio). Also, without flushing vram the above hiding feature would be meaningless.
I waited until yesterday to download the latest beta to make sure the 4.12.0.86 update was live. But it's not. I thought the last beta was supposed to be updated to the latest version, so the 4.12 beta and 4.12 release would be the same code. Or are we stuck with the .85 beta?
(I don't want to update to the released version of 4.12 until the next beta is released, presumably 4.13.)
I'm in the same boat. I want to keep 4.11 and 4.12 for now, so I am still running 4.12.0.85 beta. I really appreciate that we can have both the release and the beta active. It would be nice to have the 4.12.beta match the release, as has happened in the past.
Edit: spelling typo fixed.
Since it's only a minor update the beta has been left at 4.12.0.85 for now - having people, even a limited sub-set, download that as well as the General release 4.12.0.86 would really have killed the hamsters. Rob says watch the ski...I mena change log, there will be more updates soon.
I swear I heard their little screams as I downloaded products at dialup speeds a few days ago…
Did Rob happen to drop a hint on whether those changes will be 4.12 fixes, (as happened with 4.6 and 4.9,) or moving on to 4.13? I check the change log every week day, and the suspense is unbearable!
Ah ha!
Change log is now showing updates. Question answered. The next beta will be 4.12.1.x
Be sure and tell Rob I said thanks for the change log update. (Even though I know it wasn't for my benefit…)
Because I can't download the .86 beta, I don't know if this issue has been fixed or not, but I suspect not. It may even be hardward dependent. But if anyone else is having the same issue with the 4.12, either the beta or the release, I'll file a trouble ticket.
While I'm composing a scene, I generally use Smooth Shaded or Texture Shaded draw mode, but as I work, I'll switch to Nvidia Iray draw mode to preview the progress. I usually have GPU-Z running, and I can see that the GPU is being used for these preview renders. Until it isn't. So somewhere along the line while I'm working, the GPU stops rendering. It appears to be independent of the amount of memory being used.
When I shut down the .86 beta normally, (not a crash,) I frequently find the memory of the video card has not been released. This happened again last night, after the GPU stopped rendering. According to GPU-Z, only 6399MB of the 8GB memory was being used. To clear the memory, I had to reboot the computer. After rebooting, I opened the scene in 4.11 and rendered for 30 minutes. Memory used was reported at 7400MB+ and the GPU was rendering at about 98%. I closed 4.11 opened the .85 beta, loaded the scene and started the render. Memory used was reported at 7400MB+. (Which begs the question, why was only 6399MB reported earlier, before I rebooted the computer?)
I discovered a problem with the scene, some mesh that I thought was hidden was not. I stopped the render and closed the render window. Memory used decreased normally, as reported by GPU-Z. I used the Geometry Editor to select the bits of mesh that were showing and assigned them to a previously created material that has 0% Cutout Opacity. I then started a new render. GPU-Z reported 100% of GPU being used, along with increased memory of 7800MB+. The render has been going all night, and the current report is 7924MB used.
In the log file, between every update of iterations, there are six lines of warnings, (one Optix Prime warning and five memory errors):
2019-10-06 11:12:41.948 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.
2019-10-06 11:17:36.659 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080): out of memory (while allocating memory)
2019-10-06 11:17:36.659 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080): Failed to allocate 170.625 MiB
2019-10-06 11:17:36.659 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080): May not have enough memory available to execute CUDA kernel (estimated 170.625 MiB).
2019-10-06 11:17:36.675 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080): out of memory (while allocating memory)
2019-10-06 11:17:36.675 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080): Failed to allocate 21.75 MiB
WARNING:
Dont use Face Transfer,,,, it uses hard coded path for files into C: !!!
If you have your DAZ3D installed in other location all your work will be wasted and even if you point to missing files It will be a broken character... 4 hours wasted beacause of that.
Errro message even that I have everytrhing on N:
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbasearmsmapd_1004.jpg
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbaseeyes01_1007.jpg
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbasefacemapd_1001.jpg
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbaselegsmapd_1003.jpg
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbasemouthmapd_1005.jpg
c:/users/fableman/appdata/roaming/daz 3d/studio4 public build/temp/face transfer/generate/924/g8fbasetorsomapd_1002.jpg
I had to kill it on frame 1 with task manager as it was using over and above my RAM on CPU yet GPU-Z never went over 5GB
my 980ti has 6GB
I have often rendered hundreds of frames on 6GB no worries other builds
the the first frame rendered GPU
frame 0
this is what I am talking about
what annoys me is 4.11 was fine so I updated the release build too not realising it would be borked like the beta
I thought the releases used the just tested previous betas is sort of the point I thought
printscreen has cut off my picture
2019-10-09 04:29:02.660 Iray [VERBOSE] - IRAY:RENDER :: 1.12 IRAY rend progr: CUDA device 0 (GeForce GTX 980 Ti): Processing scene...
2019-10-09 04:29:02.989 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Geometry memory consumption: 328.186 MiB (device 0), 0 B (host)
2019-10-09 04:29:03.004 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing OptiX Prime for CUDA device 0
its unticked
2019-10-09 04:29:03.541 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.5 IRAY rend error: OptiX Prime error (Device rtpModelUpdate BL): Memory allocation failed (Function "_rtpModelUpdate" caught exception: Encountered a CUDA error: cudaMalloc(&ptr, size) returned (2): out of memory)
2019-10-09 04:29:03.836 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: CUDA device 0 (GeForce GTX 980 Ti): Scene setup failed
2019-10-09 04:29:03.958 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: CUDA device 0 (GeForce GTX 980 Ti): Device failed while rendering
2019-10-09 04:29:03.958 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.12 IRAY rend warn : All available GPUs failed.
2019-10-09 04:29:03.995 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.12 IRAY rend warn : No devices activated. Enabling CPU fallback.
2019-10-09 04:29:04.038 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.12 IRAY rend error: All workers failed: aborting render
2019-10-09 04:29:04.055 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 4 cores for rendering
2019-10-09 04:29:04.055 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2019-10-09 04:29:04.064 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2019-10-09 04:29:04.064 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2019-10-09 04:29:04.064 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Using Embree 2.8.0
2019-10-09 04:29:04.064 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing Embree
2019-10-09 04:29:04.064 Iray [VERBOSE] - IRAY:RENDER :: 1.12 IRAY rend progr: CPU: Processing scene...
2019-10-09 04:29:08.573 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Importing lights for motion time 0
2019-10-09 04:29:08.975 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing light hierarchy.
2019-10-09 04:29:09.337 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Light hierarchy initialization took 0.361s
2019-10-09 04:29:17.881 Iray [INFO] - IRAY:RENDER :: 1.12 IRAY rend info : CPU: Scene processed in 13.818s
2019-10-09 04:29:18.049 Iray [INFO] - IRAY:RENDER :: 1.12 IRAY rend info : CPU: Allocated 71.1918 MiB for frame buffer
2019-10-09 04:29:18.681 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Native CPU code generated in 8.272s
That's the temp folder - which you can move in preferences. You need to save the face, using the function in the pane, to get permanent texture files.
@barbult, It's been a couple of weeks since 4.12 was released. Looks like we're never going to get the 4.12.0.86 beta. With the issues I'm having with the latest Iray, how it hogs the video card's memory, and forces me to use Optix, (which my own testing showed slowed down my renders, way back when the first Beta with Iray support for GTX cards was released,) I'll probably keep using the 4.11 release as my backup. If it won't render on GPU in 4.12, it usually will in 4.11.
I guess it's a wait and see for the next 4.12 updates, but with the change log showing predominantly animation fixes and nothing about a newer version of Iray, I'm not hopeful. Maybe by the time 4.13 is in the works, Nvidia will have streamlined Iray enough to work better with my now ancient, (3-yr old,) GTX 1080. (Or made it completely obsolete! Forget the cost of content, the hardware reqs are going to price me right out of my favorite hobby/addiction!)
same card as me, have you tried rendering an image series?
I've done some scenes lately that use a lot of the card's memory. Those scenes will fit on the card in 4.11 because, apparently, Optix is off. But the added memory requirement of Optix with the version of Iray in 4.12 is enough to push the render to CPU only. Or that's my guess anyway, based on Optix comments in this thread.
I will say that each new driver I install has led to more of the card's memory being available for the scene. It used to drop to CPU with memory just below 7GB. Now it's closer to 7.8GB before it goes to CPU. I saw memory in GPU-Z reported as high as 7900+ MB with my last image.
So, today I tried an image series to see what would happen. I loaded a large scene that used almost all my GPU memory. Frame 0 rendered in GPU as expected. Frame 1 fell back to CPU. I killed it at that point. I wasn't prepared to wait on a CPU render. Is this what you have been experiencing?
Yes!
makes animation impossible
It is the OptiX Prime activating next frame in spite of it being unticked under advanced
our cards don't support it so they fail
I have asked on the Nvidia forum too to no avail if can be disabled that end
Thanks.
Works fine for me and I don't use C for anything.
The temp files you have to save, irrespective of where you keep your Studio folders.
Got around to trying to render an image series in 4.12 using my measly GTX 1050 2GB today and also had it fail in similar fashion.
HOWEVER, I decided to do some more testing and discovered that the same image series renders perfectly if Iray preview is ENABLED before starting the render and left on for the duration (sounds ass backwards I know, but there's actually a plausable explanation to be had here if anyone else can confirm.) @SadKitty_Carrara @L'Adair @barbult any chance you could try doing the same (activate and leave on Iray preview before rendering your sequence) and see if you get similar results?
Fyi there's a newer version of Iray (2019.1.4) already coming down the official pipeline for 4.12.1 (what the next Beta release is going to be called.) Fingers crossed that it makes a difference here.
OptiX Prime itself isn't the probem since OptiX Prime is ALWAYS active for each and every frame rendered in 4.12 using non-RTX GPUs. Meaning that if it were, frame 0 would also fail. The problem is that there's a memory usage overlap between the rednering of frame 0 and 1.
I will try this later when I can
yes certainly memory leak of some sort, I just assumed was Optix Prime from the logfile as I had it unchecked as I do always and it was at that point it went to native CPU
...yeah. Unbeknownst to the Daz folks, Iray's dvelopers went and removed the underlying functionality of that control COMPLETELY when they released the first version of Iray for RTX (see the second paragraph.) That checkbox has been nothing more than a placebo since DS Beta 4.11.033.
DS4.11 beta was what I was happily using and want back
I upgraded both as falsely assumed the general release is the previous beta
Rendering an image series with Iray Preview on did not solve the CPU fallback problem for me. I set up a series with 4 frames. The first rendered in GPU, the following frames all fell back to the CPU. A log file excerpt us attached. I have a GTX 980 Ti.
I fear 4.12 was released in a rush to allow the face plugin sales. Let's hope 4.12.1 and/or the next studio drivers will work better.
I also have a odd behavior in the log at startup. It says everything is ok, but it reports 5Gb free out of 6Gb in my 1060. With 4.11 I had 6Gb free at startup. So it seems there's something in the drivers or iray itself that's reserving 1Gb vram even with an empty scene and before rendering. I have the viewport in opengl mode and the monitor plugged to the mobo. So I use the vega graphics for the viewport and I reserve the 1060 for rendering. Can anyone please check this out just to see if it's common or just me ..
Also gpu-z reports 6Gb free so may be it's just bad data in the log .. But if iray really detects 5Gb then it has 1Gb lost.
I don't know if this will help much. I have two large monitors attached to my GTX 980Ti. One is 3840 by 2160 and the other is 2560 by 1440. It still says my 6GB card has more memory available than yours, even though you have no monitors attached.
2019-10-12 01:08:51.387 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Your NVIDIA driver supports CUDA version up to 10.1; iray requires CUDA version 10.1; all is good.
2019-10-12 01:08:51.390 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Using iray plugin version 5.0-beta, build 317500.3714 n, 19 Jul 2019, nt-x86-64-vc14.
2019-10-12 01:08:51.454 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 0 (GeForce GTX 980 Ti): compute capability 5.2, 6 GiB total, 5.01263 GiB available, display attached
Thank you @barbult, so it seems it's always 5Gb anyway .. I had 6Gb at startup with 4.11. Do you remember how much did you have with 4.11 ? Also how much does gpu-z report for you ?
Have any of you tried setting your "Instancing Optimization" setting to "Memory"?
@Cinus, instancing optimization is for scenes using instanced objects, for sure an empty scene at startup doesn't use instancing. Anyway yes, mine is set to memory but I'm sure it doesn't matter. Thank you for your reply though.