Recent problem: Iray not using GPU

JD_Mortal

TheKD said:

Daz itself can tell you what it's using to render, in the progress box, click the history button. 4 minutes is pretty good for iray, my average with a 2080 super is like 20 mins, sometimes I have to let it cook an hour or more if I am doing an indoor render with scene specific lighting and no hdri.

That only tells you what it started to render with, not what it is actually or currently rendering with, at any given time, through the rendering process, after any iterations.

I have had GPUs drop-out mid-render and it switches to CPU, without any mention of it in the logs or in the render-window.

Oddly, I also get, on occasion, a notice in the render-window activity, showing specific cards rendering the "Scene update", saying "GPU-0 updated scene", which also don't show in the logs, but they show in the window, as you render... But, not all the time. (Usually just before the whole system stops rendering with anything but the CPU, which I have actually told it NOT to do. Yet another redundant option to select, since it always "Falls back to CPU", instead of just stopping and asking if you want to continue on CPU only, when you tell it NOT to use CPU to render.)

For the record, these are non-RTX cards. (Titan-V and Titan-Xp-Collectors-Edition cards.) All randomly fail, in various rendering situations. With or without IRAY preview on, or with or without Optix selected, on both the public-release and beta-public. Since 4.11 and now worse in 4.12. With any of the latest or prior two video drivers... (Gamer-WHQL, or Studio-WHQL versions.)

I learned something new about Task-manager today... They added CUDA and Compute_1 to the list of things to monitor for the GPUs, which was not there before. Must have been in the last WDDM driver update. Nice... But I still trust MSIafterburner or CPU-Z for that data (at the moment). Windows still doesn't show my cards in TCC mode, so task-manager wouldn't show those values for those cards, to me.

I'm just along for the ride, like everyone-else, at the moment. Patiently awaiting the next release, in hopes that some of these issues are fixed for us. After this, I'm never updating again... :P

kenshaw011267

CUDA and compute_1 have been there for at least a year.

JD_Mortal

kenshaw011267 said:

CUDA and compute_1 have been there for at least a year.

Daz wasn't working with my Titan-Vs least a year, for over a year... CUDA use would have always been 0%. Just jumped back into rendering a few months ago, before it broke with this release. My Titan-Xp-CE cards never had these issues, until now, too. Thus, my "learing about the new settings", which are not exactly "new". (:P) Settings which annoyingly fallback to "3D" activity, instead of what you set to display for monitoring. ARG, windows!

P.S. Only CUDA reports any activity for me. Compute_1, or 0, are both 0%, when rendering. (Are those limited for TCC measurements that WDDM couldn't previously display? Or are they specific only to when you set the cards into "compute mode", in the drivers settings. I know, slightly off topic a bit.) Normally I just monitor card activity in MSI-Afterburner, which reports activity correctly, where windows still doesn't think the cards are doing anything "generally", as "activity".

kenshaw011267

JD_Mortal said:

kenshaw011267 said:

CUDA and compute_1 have been there for at least a year.

Daz wasn't working with my Titan-Vs least a year, for over a year... CUDA use would have always been 0%. Just jumped back into rendering a few months ago, before it broke with this release. My Titan-Xp-CE cards never had these issues, until now, too. Thus, my "learing about the new settings", which are not exactly "new". (:P) Settings which annoyingly fallback to "3D" activity, instead of what you set to display for monitoring. ARG, windows!

P.S. Only CUDA reports any activity for me. Compute_1, or 0, are both 0%, when rendering. (Are those limited for TCC measurements that WDDM couldn't previously display? Or are they specific only to when you set the cards into "compute mode", in the drivers settings. I know, slightly off topic a bit.) Normally I just monitor card activity in MSI-Afterburner, which reports activity correctly, where windows still doesn't think the cards are doing anything "generally", as "activity".

compute_1 showed CUDA for me the lest time I checked. I use afterburner as well but send people to task manager rather than trying to get non technical people to DL and install something.

TheKD

That's weird, there was always something in log about a GPU dropping for me. Since I switched back to win7, the only time it ever drops in the middle of a render is when the whole driver crashes, and you get the normal popup about a driver stopped working etc. Used to happen all the time in win10, was so annoying.

RenderPretender

I'm glad to have found this thread, as now I don't feel so alone, though the issue persists. After updating to 4.12.1.117 this morning, I can't get DAZ to use my GPU to save my life, despite a driver update. Something is definitely going on with the latest DAZ update. Sorry, but it's beyond frustrating.

Wallace3D

I have noticed that My Daz scenes use up more of my VRAM than previose version. I have 11GiB of available VRAM with no display and another 8GiB available on my display card I opened a scene that on the previose version only used up 6GiB of my VRam and on this newset version and even the newset Beta the Scene eats up my VRAM

I have even lowered my threshold to 64 Med and 256 High and it still eats it up. I even turned off ALL subD and switched to Base and the scene STILL ate up my VRAM

I noticed that a lot more Calculations are being put into the render which Recommends TCC and not WDDM

 

Rendering in NVIDIA IrayCompiling Shaders - 0/1Rendering imageRendering...Iray (Statistics) : Geometry memory consumption: 173.838 MiB (device 0), 0.000 B (host)Iray (Statistics) : Geometry memory consumption: 173.838 MiB (device 1), 0.000 B (host)Iray (Statistics) : Texture memory consumption: 6.192 GiB for 557 bitmaps (device 0)Iray (Statistics) : Lights memory consumption: 13.397 MiB (device 0)Iray (Statistics) : Material measurement memory consumption: 0.000 B (GPU)Iray (Statistics) : PTX code (180.938 KiB) for SM 6.1 generated in 0.245sIray (Statistics) : Materials memory consumption: 2.197 MiB (GPU)Iray (Convergence) : 58.61%Iray (Iteration) : 1Iray (Canvas) : Render target canvas was written.Iray (Convergence) : 66.90%Iray (Iteration) : 2

After Trying to render this scene it Stops and i get

 

2020-05-14 16:11:08.492 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.6   IRAY   rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-05-14 16:11:08.497 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.8   IRAY   rend error: All workers failed: aborting render

 

Richard Haseltine

Which was your previous version? Iray in most if not al DS 4.12.x.x has been passing extra code to non-RTX cards like yours, to make up for the features not available in hardware, and that of course increases the memory load. There is a low memory option in the latest version, alkbeit with performance impact.

Wallace3D

Richard Haseltine said:

Which was your previous version? Iray in most if not al DS 4.12.x.x has been passing extra code to non-RTX cards like yours, to make up for the features not available in hardware, and that of course increases the memory load. There is a low memory option in the latest version, alkbeit with performance impact.

4.12.0.33 I had no issues with rendering with my GPU's and it not needing to fallback to my CPU due to memory failures. Scenes that took 10 min to render on that version fail to render and fallback to the CPU making the render 40 min

 

Also to add to this.. When first opening a scene to render it starts off rendering using the GPU and 17 seconds in it falls back to the CPU. every time after the GPU Memory fails and it will only render with the CPU 

in the log it shows multiple "an illegal memory access was encountered (while de-allocating memory)"

kezzafev

Hi,

I've been experiencing the same problem with the GPU not being used for renders in the latest update of DAZ Studio. I found a link for DAZ 4.11 and re-installed that not using the DAZ client. It seems to have worked for me, my renders are back to usual using the GPU and not the CPU. Also in this older version of DAZ you still have the option of disabling Optic X too (for the people who still wanted that to be an option). Here is the link I used if anybody wants to try it to fix there render problems.

 

https://rahim-soft.com/final-stage/#http://dl2.downlinks.me/afg/DAZ.Studio.Pro.4.11.0.383.x64.rar 

 

Hope this helps!

kenshaw011267

4.11 has a non functional check box for Optix. It does nothing. In 4.11 it is always on.

johnkammer1962

marble said:

kenshaw011267 said:

I've got a 2070 and the 430.86 driver. Everything is fine.

iray not releasing VRAM has nothing to do with drivers but an issue between DS and iRay. Try not using iRay viewport

Indeed, after my experiences with the IRay preview yesterday, I have been avoiding that completely. Which is a shame because it is often handy to see how a shader looks in the render or which hair colour looks right. As I said earlier, this is all very frustrating and far from "everything is fine". I have no idea why some of us are getting several problems while others such as you and Richard are not. I do hope that we are not being dismissed as being technically ignorant - these are real issues and I have posted examples in the main threads for these releases and elsewhere. There is clearly no point in logging a Support ticket if the issues are just being dismissed.

I'm noticing this as well. (apparently years later). I can preview in iray and when I get it where I like it can save the scene after setting the view to texture mode. Then reboot DAZ, open the scene back up and render to IRAY. A bit of a pain in the ass, granted, but saves significant rendering time. 

 

s3raph1m_d9befaf610

It seems to be, and still is in 4.21... that if you use IRAY in the viewport at any point, you need to restart daz3d or it will fallback to CPU, no idea why.

did note, that the vram does not get released from viewport.