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
Did you use DDU, Display Driver Uninstaller, to uninstall the driver or did you just try to do it manually? If you didn't get DDU get it uninstall whatever driver you have installed and then install the latest Nvidia driver.
I tried a customized install through the Nvidia package that forces a clean install, deletes previous drivers etc. Didn't help.
Get DDU. Those Nvidia things do not always work.
I'll give it a shot when I have time. Maybe over this holliday weekend.
I have Geoforce driver 430.86 and my GPU is reading 0% (with very occasionaly 100% spikes) when rendering in Daz.
Open Task Manager, switch to the performance tab and select your GPU. Pick a graph and open the drop down that shows the graph title and select CUDA instead. What does that show?
It sounds like it's allocating more and more vram as it goes on rendering so it reverses to cpu eventually .. You can check it with gpu-z to see if this is the case. You may try to set memory optimization if the scene is using instances, and to turn off the denoiser or set it to run on the last iteration only.
EDIT. Also from what I read here it seems to me that the new iray is very picky as for drivers and cards and also may be the windows version itself in relation to drivers. This is not good. And I guess I'm lucky that everything seems to work fine on my pc.
no entiendo si hay tanta gente que tiene poblema con la nueva version no lo solucionan ?
I"m hitting the same problem too. RTX2080 (430.86), Daz 4.11 won't use the GPU at all according to GPU-Z. Even a scene with one character and HDRI lighting causes it to fall back to CPU. It says it's using ~6 GB of GPU memory but 0% of the GPU.
And which driver version are you uisng?
430.86, the newest one. Watching GPU-Z closely, it starts out using the GPU prior to rendering but eventually falls back to CPU after 10+ minutes. (that's when I stopped watching) Optix On/Off doesn't seem to make a difference. I'm at work now but can post the log when I get home.
So below is the log file, and attached is a pic of GPU-Z where you can see the GPU use at peak, then suddenly drop to zero. After it drops to zero, nothing gets rendered at all. The render window is blank and it hangs like that until I try to cancel the task, which causes Daz to crash.
2019-07-08 20:48:01.916 NVidia Iray GPUs:
2019-07-08 20:48:01.916 GPU: 1 - GeForce RTX 2080
2019-07-08 20:48:01.916 Memory Size: 7.9 GB
2019-07-08 20:48:01.916 Clock Rate: 1800000 KH
2019-07-08 20:48:01.916 Multi Processor Count: 46
2019-07-08 20:48:01.916 CUDA Compute Capability: 7.5
2019-07-08 20:48:01.963 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::nvidia::lights_photometric" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\nvidia\lights_photometric.mdl".
2019-07-08 20:48:01.963 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::daz_3d::property_annotations" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\property_annotations.mdl".
2019-07-08 20:48:01.963 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::daz_3d::basic" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl".
2019-07-08 20:48:02.001 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::daz_3d::irayubermaterial" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\irayubermaterial.mdl".
2019-07-08 20:48:02.017 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::nvidia::axf_importer::axf_importer" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\nvidia\axf_importer\axf_importer.mdl".
2019-07-08 20:48:02.041 Iray INFO - module:category(SCENE:IO): 1.0 SCENE io info : Loading module "::nvidia::core_definitions" from "C:\Program Files\DAZ 3D\DAZStudio4\shaders\iray\nvidia\core_definitions.mdl".
2019-07-08 20:48:02.059 Total class factories: 2096
2019-07-08 20:48:02.059 Iray VERBOSE - module:category(IRAY:RENDER): 1.1 IRAY rend stat : Environment cache size capacity: 5.
2019-07-08 20:48:02.060 Creating Script Engine...
2019-07-08 20:48:02.070 WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
2019-07-08 20:48:02.070 3D mouse support library could not be loaded.
2019-07-08 20:48:02.071 Creating Main Window...
2019-07-08 20:48:02.071 Creating Viewport Manager...
2019-07-08 20:48:02.105 Successfully created OpenGL viewport for Viewport1.
2019-07-08 20:48:02.167 Successfully created OpenGL viewport for Viewport2.
2019-07-08 20:48:02.209 Successfully created OpenGL viewport for Viewport3.
2019-07-08 20:48:02.252 Successfully created OpenGL viewport for Viewport4.
2019-07-08 20:48:02.301 Creating Action Manager...
2019-07-08 20:48:02.306 Creating Pane Manager...
2019-07-08 20:48:02.404 Successfully created OpenGL viewport for AuxViewportView.
2019-07-08 20:48:02.444 WARNING: QLayout: Attempting to add QLayout "" to BatchPane "Batch Render", which already has a layout
2019-07-08 20:48:02.448 WARNING: QLayout: Attempting to add QLayout "" to BatchPane "Batch Render", which already has a layout
2019-07-08 20:48:02.448 WARNING: QLayout: Attempting to add QLayout "" to BatchPane "Batch Render", which already has a layout
2019-07-08 20:48:02.990 Updated metadata for 0 of 1 items.
2019-07-08 20:48:03.129 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(660): sync completed successfully, 1 items succeeded, 0 items failed.
2019-07-08 20:48:03.129 Metadata update succeeded.
2019-07-08 20:48:03.178 Executing startup script...
2019-07-08 20:48:03.204 Started in: C:/Program Files/DAZ 3D/DAZStudio4
2019-07-08 20:48:03.204 DAZ Studio Started
2019-07-08 20:48:03.205 Creating Pixel Buffer
2019-07-08 20:48:03.225 Pixel buffer - Width: 1024 Height: 1024
2019-07-08 20:48:03.226 Compiling OpenGL Shader...
2019-07-08 20:48:03.228 Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Shader Program successfully linked.
2019-07-08 20:48:03.255 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): recv failed errno=10054
That's not showing the render at all (the log file), or even the loading of the scene.
Hmm...so what do you think the problem might be? It renders fine in the preview window and also fine at lower resolutions but when I try to increase the resolution to 6000x6000 it stalls at that point.
It happening to me too.
The odd thing is, occasionally Daz will use my GPU. When it does render times are faster. It's hit and miss, it appears Daz chooses to use the GPU when it feels like.
6k x6k? What made you think a 2080 could handle 36 millions pixels? You're dropping to CPU because the card ran out of VRAM.
I dunno...perhaps the other renders at 8000x8000 I did that rendered with no issue??
Same scene? Same textures? Same lights? Same subD on everything?
Even at 4k, which is 4.5 times smaller than 6kx6k, getting a complicated scene to render on an 8Gb VRAM card is going to be trickt.
@banpei "It renders fine in the preview window"
If you're running an Iray Viewport, then rendering, I think you double up on the Vram usage.
I have an RTX-2080 attached to an Alienware laptop through the gaming adapter. The first beta version of 4.11 used the RTX beautifully. Without taking measurements, I could tell the work was offloaded to the external GPU. The production version of 4.11 is not using the GPU. My renders are not running through the GPU as confirmed by Task Manager and GPU-Z. But the most obvious proof is that my CPU fan screams as the CPU is maxed at 100% utilization and my computer is barely usable. Render performance has also suffered noticably. My NVidia driver version is 430.86. When I switch to the licensed version of Octane Render plugin for Daz Studio, the render pipeline runs through the 2080. I'm going to have to use it going forward which will add significant time to my workflow (setting up the materials).
Quadro K5000 and GTX760 (both Kepler micro-architecture) not working with production release 4.1.1; this seems to be a valid issue from the reports in the forum threads so is anyone working on it?
4.1.1? Do you eman 4.11.0.383? What driver are you using? What is your OS?
Daz 4.11.0.383 64bit. Nvidia Quadro 431.36, GTX760 was latest from nvidia as of yesterday.
One helpful observation is that changing the nvidia control panel setting for DazStudio.exe to specify the K5000 as the cuda device and not global default setting seems to have resolved it for now without setting OptiX on, if I set that it will no longer utilise the GPU even after unsetting it again. A fresh restart of Daz Studio and it is back using cuda again. Hope this may help others but I think it's still not a fix for some by the previous threads.
I have the same issue
I installed Daz Studio 4.11 through the Install Manager yesterday
I have the following Cards on my system:
Windows 10 64bit
Test rending today I get no Iray preview and black render unless I select only CPU for Interactive Devices. No OptiX Prime Acceleration selected.
I updated NVIDIA Drivers to version 431.60-desktop-win10-64bit-international-whql.
My previous driver version (430) was working with DS 4.10
I have rolled back to Daz Studio 4.10.0.124 64bit but I am still not getting any renders to work :-(
All I ever get in the logs is:
2019-07-25 12:31:43.835 Iray INFO - module:category(IRAY:RENDER): 1.0 IRAY rend info : Using interactive scheduling, architectural sampler unavailable, caustic sampler disabled
2019-07-25 12:31:43.841 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER): 1.0 IRAY rend error: Cannot render: found no usable devices.
2019-07-25 12:31:43.841 Iray Render error: Invalid parameters (NULL pointer).
I have uninstalling my Graphics Cards, re-installing them, uninstalling Daz Studio, re-installed 4.10 and now I can render via my NVIDIA GeForce GTX 1070 Ti.
Just to test I re-installed 4.11 again but again the same thing happened and the cards were not recognised by DS
Rollback to 4.10 allows me to render again.
Funny thing was that on the initial 4.11 install it showed that I had two NVIDIA GeForce GTX 1070 Ti cards, which unfortunately is not the case.
I have the same problem after the update I can not renderizart, I want to go back to version 4.10 have, where I can download?
Have you updated your drivers, to 418.63 or later? If your GPU cannot be updated you will need to contact Technical Support https://www.daz3d.com/help/help-contact-us
Bumped into the same problem. I have a Quadro M4000 and a Kepler-based GTX Titan. After installing the latest drivers, and restarting DS, the Titan no longer appears in the device list. I guess Kepler based cards no longer supported by IRay, because the scene renders fine (albeit slower...) with the Quadro. I guess it's time for a GPU upgrade.
My Quadro M4000 has also stopped working and is not being picked up by Iray render engine instead it just uses CPU 100% and is taking hours to start the actual render which doesn't look right. Was working fine last week so I'm totally bamboozled!
Will NOT be buying anymore DAZ products until I can fix this issue
Does anybody out there have any ideas please?
You need to provide more info to let anyone help you. Simply demanding a fix to a problem that could be in DS or your system as well.
Hello, I continue to have the same issue as many stated before. It is two months I have problem rendering with Iray - since I installed 4.11
Windows 10 64-bit (updated)
Geforce GTX 960M with the latest 436.15
Daz Studio 4.11.0.383 Win 64-bit
When I try rendering a scene, DAZ doesn't crash, instead it simply gives a black or checkered screen. Or sometimes it works, after the tenth try, but the next one doesn't, and so on. It's infuriating.
With CPU checked and GPU unchecked in the Advanced panel, it works (but it's really slow and it's not a solution).
With the previous 4.10 i've never experienced any problem.
Thanks for any help.