Loading...
> >

Recent problem: Iray not using GPU

culannmacculannmac Posts: 48
in Technical Help (nuts n bolts)

Hi all,

I took a month-long break and discovered last night that Iray immediately kicks in to the CPU and ignores the GPU. I've updated my Nvidia drivers (441.20), made sure the appropriate configurations were checked in render settings, and tested everything with small simple renders. Nothing worked,  I'm dead in the water. Is anyone else having these problems?  Is there an upcoming patch planned?

«1

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,948

    What is your card? Have you tried the 430.86 drivers, which are the minimum for DS 4.12 (and were working fairly reliably for most - I stil have those installed).

  • culannmacculannmac Posts: 48
    Richard Haseltine said:

    What is your card? Have you tried the 430.86 drivers, which are the minimum for DS 4.12 (and were working fairly reliably for most - I stil have those installed).

    I have a GTX 1080ti. I updated the drivers yesterday 441.20 which was the most recent release.

  • marblemarble Posts: 7,500
    culannmac said:

    Hi all,

    I took a month-long break and discovered last night that Iray immediately kicks in to the CPU and ignores the GPU. I've updated my Nvidia drivers (441.20), made sure the appropriate configurations were checked in render settings, and tested everything with small simple renders. Nothing worked,  I'm dead in the water. Is anyone else having these problems?  Is there an upcoming patch planned?

    Despite claims of it all working nicely (sorry Richard) - it isn't for me. I have a GTX1070 and have ongoing problems with CPU fallback in 4.12. These issues vary a little, for example, yesterday I was rendering different skin shader settings in IRay Preview (4.12, driver version 441.12) and it suddenly decided to use the CPU even though, according to GPU-Z, I had lots of VRAM available. Other problems with various drivers (including the one Richard claims is stable) include dropping to CPU on the second frame of any image series render and being locked into Optix Prime which eats up more VRAM and causes scenes that would render in 4.11 to crash back to CPU in 4.12.

    I am stuggling to get even small scenes rendered in 4.12 - scenes that, in the past would not have come close to the 8GB limit of my GPU. I've also noticed that there are often spikes in VRAM usage which go over the limit but return instantly to a lower number (I can see such spikes in GPU-Z). Unfortnately, the damage has been done and the GPU is disabled. This is all very frustrating, especially since I take all the precautions such as optimising the textures and deleting scene content that is off-camera.

  • KharmaKharma Posts: 3,214

    I too have found my renders drop to CPU if I have been using the Iray preview when I close the render it doesn't release the vram, but if I don't use the iray preview once I render a scene and then close it the VRAM seems to release and I am using the 430.86 driver and DS 4.12 beta. I am seeing this in GPU-Z

  • culannmacculannmac Posts: 48

    From what I recall, Iray wasn't supported for the RTX series. Could it be possible that the new fixes borked everything for older cards?

  • Richard HaseltineRichard Haseltine Posts: 100,948

    If these are non-RTX cards, I have found the 430.86 drivers to work well - I haven't tried anything newer (yet).

  • kenshaw011267kenshaw011267 Posts: 3,805

    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

  • marblemarble Posts: 7,500
    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.

  • kenshaw011267kenshaw011267 Posts: 3,805

    Neither Richard or I work for Daz. You do not provide enough information to diagnose the problem. 

  • culannmacculannmac Posts: 48

    Just rolled back to 430.86.  Issue persists. Iray is still loading render to CPU.

  • marblemarble Posts: 7,500
    kenshaw011267 said:

    Neither Richard or I work for Daz. You do not provide enough information to diagnose the problem. 

    I didn't suggest that you do work for DAZ, nor am I asking you to diagnose the problem. I suggested that opening a support ticket would be a waste of time because there is a prevailing view that 4.12 works fine. Further, I am sure that others have submitted these problems to support because they have been present since 4.12 was released and have been discussed at length in the release threads (Beta and General). Yet we have no acknowledgement that there is any problem. If you want more information, look at those threads where I did post  more information.

  • kenshaw011267kenshaw011267 Posts: 3,805
    marble said:
    kenshaw011267 said:

    Neither Richard or I work for Daz. You do not provide enough information to diagnose the problem. 

    I didn't suggest that you do work for DAZ, nor am I asking you to diagnose the problem. I suggested that opening a support ticket would be a waste of time because there is a prevailing view that 4.12 works fine. Further, I am sure that others have submitted these problems to support because they have been present since 4.12 was released and have been discussed at length in the release threads (Beta and General). Yet we have no acknowledgement that there is any problem. If you want more information, look at those threads where I did post  more information.

    Isolated problems where not enough information is posted, I did find your posts, cannot be easily diagnosed. There is an effectively infinite range of HW and SW combinations that could be the source of your issue. 

  • fastbike1fastbike1 Posts: 4,078

    If you are using driver 441.12, that is almost certainly a big part of the problem.That driver pops up in most threads where"GPU is not working for Iray and I have the "latest drivers".

    If Iray preview creates a problem, then just run a small render to check your lighting, settings, etc. It won't be longer than the Iray preview and probably won't need to run to completion for you to see what you need. Close that render window when done and the VRAM used will be cleared shortly thereafter.

    FWIW, 4.12 does work fine, at least for people that use the minimum required driver rather then "the latest driver".

    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.

     

  • culannmacculannmac Posts: 48

     

     Just rolled back to 430.86.  Issue persists. Iray is still loading render to CPU.

    As I stated earlier I did. The result was the same. I've searched for a technical fix from different sites with no success. All I know is that my set up was rendering fine at the start of October, but as of now it's not working. I've changed nothing on the HW side, the only software changes I vaguely recall was Win10 updates and the newest Nividia driver. I would happily be the first to admit I was wrong and post whatever user error solution that accounts for this problem. At this time after trying various fixes, I can reasonably assume that the problem isn’t on my end. FWIW I have submitted a ticket and am eagerly awaiting a response.

    fastbike1 said:

    If you are using driver 441.12, that is almost certainly a big part of the problem.That driver pops up in most threads where"GPU is not working for Iray and I have the "latest drivers".

    If Iray preview creates a problem, then just run a small render to check your lighting, settings, etc. It won't be longer than the Iray preview and probably won't need to run to completion for you to see what you need. Close that render window when done and the VRAM used will be cleared shortly thereafter.

    FWIW, 4.12 does work fine, at least for people that use the minimum required driver rather then "the latest driver".

    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.

     

     

  • Richard HaseltineRichard Haseltine Posts: 100,948
    culannmac said:

     

     Just rolled back to 430.86.  Issue persists. Iray is still loading render to CPU.

    As I stated earlier I did. The result was the same. I've searched for a technical fix from different sites with no success. All I know is that my set up was rendering fine at the start of October, but as of now it's not working. I've changed nothing on the HW side, the only software changes I vaguely recall was Win10 updates and the newest Nividia driver. I would happily be the first to admit I was wrong and post whatever user error solution that accounts for this problem. At this time after trying various fixes, I can reasonably assume that the problem isn’t on my end. FWIW I have submitted a ticket and am eagerly awaiting a response.

    fastbike1 said:

    If you are using driver 441.12, that is almost certainly a big part of the problem.That driver pops up in most threads where"GPU is not working for Iray and I have the "latest drivers".

    If Iray preview creates a problem, then just run a small render to check your lighting, settings, etc. It won't be longer than the Iray preview and probably won't need to run to completion for you to see what you need. Close that render window when done and the VRAM used will be cleared shortly thereafter.

    FWIW, 4.12 does work fine, at least for people that use the minimum required driver rather then "the latest driver".

    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.

     

     

    Which driver are you using now then? Windows Update is usually an older version, so if that was the last change it may simply be that you are currently pre-430.86

  • marblemarble Posts: 7,500
    fastbike1 said:

    If you are using driver 441.12, that is almost certainly a big part of the problem.That driver pops up in most threads where"GPU is not working for Iray and I have the "latest drivers".

    If Iray preview creates a problem, then just run a small render to check your lighting, settings, etc. It won't be longer than the Iray preview and probably won't need to run to completion for you to see what you need. Close that render window when done and the VRAM used will be cleared shortly thereafter.

    FWIW, 4.12 does work fine, at least for people that use the minimum required driver rather then "the latest driver".

    From what I have read, the 441.12 driver seems to be the cause of problems mostly for the RTX cards. It is actually better for me with my GTX 1070 than the 430.86 driver. That was a nightmare for CPU fallback for me - especially when I tried to render an image series. Guaranteed to fall back on the second frame. The remaining problem with the 441.12 (or DAZ Studio 4.12 - I have no idea which) is the IRay preview which, as has been suggested is easy to avoid by just not using the preview at all (use a render window instead). However, it is still not working as intended. Also, the latest drivers enforce Optix Prime which uses more VRAm which means that my scenes have to be smaller. 

  • marblemarble Posts: 7,500
    kenshaw011267 said:
    marble said:
    kenshaw011267 said:

    Neither Richard or I work for Daz. You do not provide enough information to diagnose the problem. 

    I didn't suggest that you do work for DAZ, nor am I asking you to diagnose the problem. I suggested that opening a support ticket would be a waste of time because there is a prevailing view that 4.12 works fine. Further, I am sure that others have submitted these problems to support because they have been present since 4.12 was released and have been discussed at length in the release threads (Beta and General). Yet we have no acknowledgement that there is any problem. If you want more information, look at those threads where I did post  more information.

    Isolated problems where not enough information is posted, I did find your posts, cannot be easily diagnosed. There is an effectively infinite range of HW and SW combinations that could be the source of your issue. 

    I repeat - I am not asking you to diagnose (as you point out - you don't work for DAZ). I was just adding to the conversation. I'm sure that support is aware of these issues and that they have indeed been reported. I see no need to duplicate support tickets.

  • kenshaw011267kenshaw011267 Posts: 3,805
    marble said:
    kenshaw011267 said:
    marble said:
    kenshaw011267 said:

    Neither Richard or I work for Daz. You do not provide enough information to diagnose the problem. 

    I didn't suggest that you do work for DAZ, nor am I asking you to diagnose the problem. I suggested that opening a support ticket would be a waste of time because there is a prevailing view that 4.12 works fine. Further, I am sure that others have submitted these problems to support because they have been present since 4.12 was released and have been discussed at length in the release threads (Beta and General). Yet we have no acknowledgement that there is any problem. If you want more information, look at those threads where I did post  more information.

    Isolated problems where not enough information is posted, I did find your posts, cannot be easily diagnosed. There is an effectively infinite range of HW and SW combinations that could be the source of your issue. 

    I repeat - I am not asking you to diagnose (as you point out - you don't work for DAZ). I was just adding to the conversation. I'm sure that support is aware of these issues and that they have indeed been reported. I see no need to duplicate support tickets.

    You are very mistaken. Always submit your own bug report.

    First if only one person is reporting an issue then it will generally be very low priority. If a dev team is looking at bunches of bug reports all reporting the same, or nearly the same issue, then they have a basis for trying to track down the issue and know that, incases where it is an issue with the SW and the larger system, the configuration is common enough that it was worth the money to get the implicated equipment and try and duplicate the problem.

    Second non technical people frequently report issues very non specifically so many different faults may appear the same based on the basic description. If they have multiple reports of "program chashes" but upon follow up the details are very different that means there are multiple bugs to find.

  • culannmacculannmac Posts: 48

    441.20. I manually downloaded the 430.86 driver directly from Nividia  and installed it.  I tested a scene I was working on, then tried a very simple render with two G8f figures. Both times failed. After that, I reinstalled the 441 drivers. I've yet to hear from anyone regarding my support ticket. 

    Richard Haseltine said:
    culannmac said:

     

     Just rolled back to 430.86.  Issue persists. Iray is still loading render to CPU.

    As I stated earlier I did. The result was the same. I've searched for a technical fix from different sites with no success. All I know is that my set up was rendering fine at the start of October, but as of now it's not working. I've changed nothing on the HW side, the only software changes I vaguely recall was Win10 updates and the newest Nividia driver. I would happily be the first to admit I was wrong and post whatever user error solution that accounts for this problem. At this time after trying various fixes, I can reasonably assume that the problem isn’t on my end. FWIW I have submitted a ticket and am eagerly awaiting a response.

    fastbike1 said:

    If you are using driver 441.12, that is almost certainly a big part of the problem.That driver pops up in most threads where"GPU is not working for Iray and I have the "latest drivers".

    If Iray preview creates a problem, then just run a small render to check your lighting, settings, etc. It won't be longer than the Iray preview and probably won't need to run to completion for you to see what you need. Close that render window when done and the VRAM used will be cleared shortly thereafter.

    FWIW, 4.12 does work fine, at least for people that use the minimum required driver rather then "the latest driver".

    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.

     

     

    Which driver are you using now then? Windows Update is usually an older version, so if that was the last change it may simply be that you are currently pre-430.86

     

  • culannmacculannmac Posts: 48

    This is beyond frustrating. I'm sitting here with no way to render. Tried the reality plugin yesterday. Results looked like crap. I know it could do better, but I'd probaly have to rework every shader in the image. Also thinking about using a render farm, or just buying a 2080ti card. 

    Of course Daz has yet to answer my ticket.  Anyone know when Daz will be updated again. I'm hoping whatever the recent patch broke will be fixed with a new one.

  • culannmacculannmac Posts: 48

    so here's the log from my last test with the 430.86 driver. It appears something is wrong with iray optix prime. It was switched off.

     

    2019-11-18 18:03:56.123 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00329 iterations after 167.818s.

    2019-11-18 18:03:58.152 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00333 iterations after 169.848s.

    2019-11-18 18:04:00.254 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00337 iterations after 171.950s.

    2019-11-18 18:04:00.306 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-11-18 18:04:02.248 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00341 iterations after 173.944s.

    2019-11-18 18:04:05.279 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 93.01% of image converged

    2019-11-18 18:04:05.280 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00345 iterations after 176.975s.

    2019-11-18 18:04:06.421 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00349 iterations after 178.116s.

    2019-11-18 18:04:06.480 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-11-18 18:04:08.376 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00353 iterations after 180.072s.

    2019-11-18 18:04:10.215 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00357 iterations after 181.912s.

    2019-11-18 18:04:12.068 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00361 iterations after 183.764s.

    2019-11-18 18:04:12.119 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-11-18 18:04:14.304 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00366 iterations after 186.000s.

    2019-11-18 18:04:16.542 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00371 iterations after 188.238s.

    2019-11-18 18:04:19.725 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 94.63% of image converged

    2019-11-18 18:04:19.851 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00376 iterations after 191.547s.

    2019-11-18 18:04:19.905 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-11-18 18:04:21.055 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00381 iterations after 192.752s.

    2019-11-18 18:04:22.832 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00385 iterations after 194.529s.

    2019-11-18 18:04:24.607 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00389 iterations after 196.303s.

    2019-11-18 18:04:26.451 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00393 iterations after 198.147s.

    2019-11-18 18:04:26.501 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-11-18 18:04:28.190 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00397 iterations after 199.887s.

    2019-11-18 18:04:29.965 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00401 iterations after 201.661s.

    2019-11-18 18:04:31.807 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00405 iterations after 203.503s.

    2019-11-18 18:04:31.856 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-11-18 18:04:34.477 Iray [VERBOSE] - IRAY:RENDER ::   1.0   IRAY   rend progr: 95.62% of image converged

    2019-11-18 18:04:34.477 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00409 iterations after 206.173s.

    2019-11-18 18:04:34.605 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Convergence threshold reached.

    2019-11-18 18:04:37.021 Saved image: C:\Users\ 2019-11-18 18:04:37.027 Finished Rendering

    2019-11-18 18:04:37.058 Total Rendering Time: 3 minutes 34.49 seconds

    2019-11-18 18:04:37.150 Loaded image r.png

    2019-11-18 18:05:04.770 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

    2019-11-18 18:05:19.912 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:

    2019-11-18 18:05:19.912 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1080 Ti):                  413 iterations, 13.299s init, 193.778s render

  • Richard HaseltineRichard Haseltine Posts: 100,948

    Optix Prime cannot now be switched off, it is on when using a non-RTX card regardless.

  • kenshaw011267kenshaw011267 Posts: 3,805

    According to that log your GPU did the render.

    Did you think a less than 4 minute render was done on the CPU?

  • culannmacculannmac Posts: 48

    Yup. It seemed slow to me. 

  • kenshaw011267kenshaw011267 Posts: 3,805

    It wasn't. Your log is 100% clear. The 1080ti did the render.

    Many, most, monitoring software ignores CUDA activity unless specifically set to display it. I've got two GPU's and they both show 0% activity when rendering.

  • culannmacculannmac Posts: 48

    This sounds bad. I'm I correct in assuming this is a resource hog? It just seems my machine is struggling with renders that it was easily rendering last month. I guess I'll go shopping for an RTX card. 

    Richard Haseltine said:

    Optix Prime cannot now be switched off, it is on when using a non-RTX card regardless.

     

  • culannmacculannmac Posts: 48

    That monitor's worked in the past, but the log is the log. I'm trying GPU-Z but it's not telling me anything either. Do you have a recommendation?  

    kenshaw011267 said:

    It wasn't. Your log is 100% clear. The 1080ti did the render.

    Many, most, monitoring software ignores CUDA activity unless specifically set to display it. I've got two GPU's and they both show 0% activity when rendering.

     

  • TheKDTheKD Posts: 2,691

    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.

  • kenshaw011267kenshaw011267 Posts: 3,805
    culannmac said:

    That monitor's worked in the past, but the log is the log. I'm trying GPU-Z but it's not telling me anything either. Do you have a recommendation?  

    kenshaw011267 said:

    It wasn't. Your log is 100% clear. The 1080ti did the render.

    Many, most, monitoring software ignores CUDA activity unless specifically set to display it. I've got two GPU's and they both show 0% activity when rendering.

     

    Task Manager can do it. on the performance tab select the GPU and choose a graph. Click the graph title and choose CUDA or Compute_1 from the drop down. Run the render with Task Manager still open.

  • marblemarble Posts: 7,500

    I use GPU-Z to monitor the GPU but Task Manager does show GPU load too.

Sign In or Register to comment.