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
If this is Windows right-click on the desktop>nVidia Control Panel and make sure that DS is set to use the nVidia card. Doing what DoctorJellybean asked above would also show which GPU was being used.
Can you say how you are able to use Iray at all on a Mac running Catalina? I've read many (I've lost count of how many) ostensibly authoritative statements that Apple crushed any and all support for NVidia GPUs after High Sierra 10.13.6.
Lordy, all this is confusing for mere techno-speak-challenged mortals who wanted to do art, not become computer tech specialists ...
I must add myself to the list of those frustrated by 4.12 and IRay dropping back to CPU. I have a GTX 1070 which I've been using without a problem for the entire time I've had 4.11 installed but since I updated to 4.12 I have to restart DAZ Studio often because IRay drops to CPU for no apparent reason. It has just done so with a scene loaded with the bare minimum of content - just two figures and one piece of furniture. I have far more complex scenes that render in IRay and this scene renders perfectly well after restarting DAZ Studio. Apart from wasting time with the restart, it is even more frustrating when I don't notice until the render has been going a while and then I have to re-start from scratch.
My NVidia Driver is 431.70.
It wont install content manager if content manager (postgres.exe) is already running when you start installation. It cant overwritte active/already in use content. So restart your computer and than try to install Daz Studio.
Update on my GPU fallback to CPU problem. This is happening when I try to render an animation to an image series. The first render gows through fine on the GPU but the second drops to CPU. I have checked the log and it tells me aboput an Optix Prime error but I don't have Optix Prime Acceleration enabled in the Render settings (Advanced Tab).
By the way, I updated the NVidia Drivers again before running this last attempt. I am now running version 431.86.
2019-10-02 20:56:36.451 Iray [VERBOSE] - IRAY:RENDER :: 1.6 IRAY rend stat : Geometry memory consumption: 640.949 MiB (device 0), 0 B (host)
2019-10-02 20:56:36.466 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.6 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-02 20:56:36.482 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1070): Scene setup failed
2019-10-02 20:56:36.482 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1070): Device failed while rendering
2019-10-02 20:56:36.482 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : All available GPUs failed.
2019-10-02 20:56:36.482 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : No devices activated. Enabling CPU fallback.
2019-10-02 20:56:36.482 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: All workers failed: aborting render
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 8 cores for rendering
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Using Embree 2.8.0
2019-10-02 20:56:36.482 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Initializing Embree
2019-10-02 20:56:36.482 Iray [VERBOSE] - IRAY:RENDER :: 1.3 IRAY rend progr: CPU: Processing scene...
2019-10-02 20:56:39.372 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Importing lights for motion time 0
2019-10-02 20:56:39.388 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Initializing light hierarchy.
2019-10-02 20:56:39.388 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend info : Light hierarchy initialization took 0.002s
2019-10-02 20:56:39.575 Iray [VERBOSE] - IRAY:RENDER :: 1.8 IRAY rend stat : Native CPU code generated in 0.177s
2019-10-02 20:56:39.638 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Scene processed in 3.153s
2019-10-02 20:56:39.654 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Allocated 26.3675 MiB for frame buffer
2019-10-02 20:56:42.045 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Allocating 1-layer frame buffer
2019-10-02 20:56:42.107 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - POST:RENDER :: 1.0 POST rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.
You may try with a simple scene just to see if it's a driver issue or a vram issue. I assume you use studio drivers and not game drivers. You may also try enabling optix though I suspect that 4.12 always enables it. My guess is it's a out of vram issue.
Yes. It ended with me getting rid of it b/c of the bugs mentioned in this forum. And now the issue of those complaining that 4.12 dropping from GPU to CPU is a new reason. I guess that answers my question on whether or not to upgrade.
Finally.
Yeah, as of 4.11 the OptiX Prime toggle in Daz Studio has been deprecated by Iray in favor of ALWAYS using OptiX Prime acceleration for non-RTX GPUs. Actually already successfully reported this to Daz, and kind of surprised the toggle is still there in the Render Settings tab since it no longer does anything.
Guys, is ther a way to downgrade to 4.11? My render tiem increased two times after I installed 4.12
It is weird. I ran another similar scene, same environment and two characters (one the same and one different) and that ran perfectly well for the complete image series. I checked the VRAM and it was reporting around the 6GB mark in GPU-Z. The scene that fails is almos identical in terms of VRAM - around the 6GB mark. Anyhow, I wondered whether it might be just a little over (even though it was a long way short of the 8GB I'm supposed to have with a 1070) so I deleted some things form the scene (mainly fibre hair). The VRAM came down to 5.7 but that scene still falls back to CPU. The other scene, now with more VRAM being used, still works fine.
Also, in both cases they render the first image of the series fine. When the scene falls back to CPU on the second image, GPU-Z does not report any increase in VRAM usage,
The error says Optix Prime is not supported in this release yet DAZ leave it forced on for GTX cards - some strage logic there.
Yes, I did select Studio drivers when updating the drivers yesterday.
For the first time, I wish I had backed up before upgrading. I had been reading on this forum how stable and solid this release is but it clearly is not. I wish they would allow reverting to a previous version. 4.11 rendered much more complex scenes without a problem - single image or image series.
Yeah, I never imagined "optimizing the render" means increasing the render times:-)
Do you have nVidia driver 430.86 or newer installed?
Checked - it says 430.86
Just wanted to add this as well, Once I did the update, My renders also defaults to CPU. I recently built me a new machine dedicated to Daz Studio with nVidia RTX 2080Ti FTW Ultra card. I will make sure I update my driver as specified here and update.
430.86 does have some limitations with supported GPUs before the GTX10 series (and I 'think' a win10 requirement as well, maybe). just an FYI. Oddly, with a GTX1070non-Ti, my Iray times went from 3m59s on DS4.10 (never tested 4.11) to 2m38s on 4.12. I had a reduction in render times with SY's Iray benchmark scene.
Best bet, download the new driver, then, DDU the old driver, then install the new one fresh. some times old driver scraps get left behind and can cause random glitches.
Also, I'm not in the 4.12 is the best thing since sliced bread camp, I haven't decided yet, and have had an odd non-matching camera name error already when creating a new camera, lol. I should have screen capped it, tho hitting cancel and trying to create the camera again worked (shrugs).
Just to reiterate: I have updated to the very latest driver (431.86) and it is still falling back to CPU although the circumstances seem weird to me. Sometimes it does, sometimes it doesn't and I have yet to isolate what causes the failure.
maybe texture cache. if ye is working on scenes doing a lot of surface texture changes, the old textures still eat up memory and linger around. it may be that. As annoying as it can be, a simple scene save, close daz, count to 5 for the database to clear out, then open daz, load the scene, then render from there, will flush out the old texture cache.
It sounds like Iray isn’t getting the initial Context (aka instance) from your animation fully cleared from vram before starting in on the 2nd frame of your animation. The way Daz Studio renders animations is by sequentially launching fresh Contexts of Iray - one for each frame in the sequence. And each one of these Contexts entails a separate - potentially redundant - copy of scene data being stored in vram during its lifetime.
Not sure about a fix other than attempting to render the sequence immediately after freshly rebooting your system (this is actually an EXTREMELY old problem - have had occasional run-ins with it since starting with DS 8+ years ago.) Although it maybe could help to have your scene data and/or operating system located on solid state storage (faster read/write speeds may be able to allay this.) Since going fully solid state I have yet to have this happen.
It says that the OptiX Prime flag (the message Daz Studio sends to the Iray rendering plugin along with any other arguments it needs to do its job) that’s supposed to indicate whether Prime has bee selected or not in DS is no longer supported. OptiX Prime support in Iray itself is unchanged.
What is the GPU? Is it actually being used by Iray?
Please bear in mind that it is not permissible for anyone other than Daz to give you a copy of the DS installers, or other files from the Daz store, without prior permission from Daz.
1070 Ti with 8 GB VRAM. It was making 5000 pases of complex scenes with 3-4 people for 2h - 2h30m; now it takes about 4h30m
This is one of those occasions when I ask myself, what am I doing wasting time on this? I've been doing it for nigh on 15 years now so the habit is ingrained but surely there are better ways to express my creativity? Perhaps I should focus on making my own models in Blender. Or do something with Unity or Unreal?
When you use software daily and update it religiously only to find that they have broken what works and that the new features you gain from the update (in this case Face Transfer and a new animation timeline) are of no interest anyway. All of the facial transfer plugins create really pathetic facsimilies of the originals and the timeline was just fine with Keymate and Graphmate in 4.11. I only updated because of the reported decrease in render times but that is moot considering the risk of CPU fallback seems high.
Do you mean you can understand during the render itself if it renders with the CPU instead of GPU?
I think itenerant means that the render is being done by the CPU, not the GPU, in Catalina. I'm a Mac user, too, and I've read that Apple was dropping Open GL and Open CL both, in favor of Metal, in Catalina. But perhaps this has not happened, at least, not yet. If that's the case, then YEA!!!
But, yes, I've also read that there are no drivers in Catalina that will support nVidida Graphics cards.
Perhaps someone who works there at DAZ3D will explain these things to us. I hope so, and that's what I'm asking for. I'm not tech savy, and I don't want to spread anything that is untrue.
This version has a new feature, allowing you to set both the name and the label in the Create dialogue. The message isn't an error, it's letting you know that name and label don't match - which might be what you want (in which case you can opt not to have DS fix the mismatch) but it might also be a typo (in which case you can let DS fix the mismatch).
OK, so I created a new scene with the same two characters. I went out and left it to render a few frames to an image series. Once again, it fell back to CPU after the first frame but, having left it running, I can see from the GPU-Z log that the GPU kicked in again later for a frame or two and then dropped back to CPU for the rest. This is confirmed by the DAZ Studio log file:
2019-10-03 09:15:16.855 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-03 09:15:16.870 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2019-10-03 09:15:16.870 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2019-10-03 09:15:16.870 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2019-10-03 09:15:16.886 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2019-10-03 09:15:16.886 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1070)
2019-10-03 09:15:16.886 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2019-10-03 09:15:16.886 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
2019-10-03 09:15:17.073 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2019-10-03 09:15:17.073 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Geometry memory consumption: 642.079 MiB (device 0), 0 B (host)
2019-10-03 09:15:17.089 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-03 09:15:17.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.7 IRAY rend error: CUDA device 0 (GeForce GTX 1070): Scene setup failed
2019-10-03 09:15:17.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.7 IRAY rend error: CUDA device 0 (GeForce GTX 1070): Device failed while rendering
2019-10-03 09:15:17.089 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.7 IRAY rend warn : All available GPUs failed.
2019-10-03 09:15:17.104 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - IRAY:RENDER :: 1.7 IRAY rend warn : No devices activated. Enabling CPU fallback.
2019-10-03 09:15:17.104 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [ERROR] - IRAY:RENDER :: 1.7 IRAY rend error: All workers failed: aborting render
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 8 cores for rendering
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Using Embree 2.8.0
2019-10-03 09:15:17.104 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing Embree
2019-10-03 09:15:17.104 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend progr: CPU: Processing scene...
2019-10-03 09:15:19.918 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Importing lights for motion time 0
2019-10-03 09:15:19.918 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing light hierarchy.
2019-10-03 09:15:19.918 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Light hierarchy initialization took 0.002s
2019-10-03 09:15:20.105 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Native CPU code generated in 0.179s
2019-10-03 09:15:20.167 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CPU: Scene processed in 3.068s
2019-10-03 09:15:20.183 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : CPU: Allocated 26.3675 MiB for frame buffer
2019-10-03 09:15:22.558 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Allocating 1-layer frame buffer
2019-10-03 09:15:22.683 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(305): Iray [WARNING] - POST:RENDER :: 1.0 POST rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.
2019-10-03 09:15:22.730 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00001 iterations after 5.843s.
Just got home and did a test here. updated driver. Was 419.67. now 431.86 : Its seems to work for my single render. Definitely faster!
Rendering...
Iray [VERBOSE] - IRAY:RENDER :: 1.16 IRAY rend progr: CUDA device 0 (GeForce RTX 2080 Ti): Processing scene...
Iray [VERBOSE] - IRAY:RENDER :: 1.17 IRAY rend stat : Geometry memory consumption: 28.0385 MiB (device 0), 0 B (host)
Iray [VERBOSE] - IRAY:RENDER :: 1.17 IRAY rend stat : Texture memory consumption: 213.792 MiB for 27 bitmaps (device 0)
Iray [VERBOSE] - IRAY:RENDER :: 1.17 IRAY rend stat : Lights memory consumption: 948 B (device 0)
Iray [VERBOSE] - IRAY:RENDER :: 1.17 IRAY rend stat :
etc.
Looking at my logs, it seems to me that Optix Prime is, as you say, always used in 4.12 but going back to 4.11 I can see when Optix Prime was used (check box on) and not used. When not used, the log reports "Using built-in ray tracing (1.0.0)" but when Optix Prime is enabled (check box) the log reports "Using Optix Prime ray tracing (5.0.1)".
My fall-back problem definitely seems to be an Optix Prime issue.
Nothing worked so I had to go to recovery in windows and reset my pc back to before I updated. I got my verion of 4.11 back , and now my renderer is back. I was working on rendering promos for my character after two months of nothing since my pc died and having to install this is the third board as the first two lasted a week and the other three days. Now to have this no . I will upgrade when the bugs are worked out in the mean time I am using my last version. I also just bought this graphic card as my other one died around the same time as my board, and I only had it two years. I just didn't know why I could not use the one I just bought with the update.