Can't get 4.11 to use the GPU for iRay renders

Brand new MSI Laptop with 16gb RAM and an RTX 2070 running 430.86 drivers and DAZ Studio Pro 4.11.0.383 Pro 64-bit. I got one render of the I13 Office Chair to render using iRay. Since then it's nothing but software.

Comments

  • Are you saying that it's rendering in CPU, not GPU? The last statement "Since then it's nothing but software" is kinda throwing me.

    First double check and make sure the render setting is correct.

    Render settings>Advanced, tick the box for the gpu untick the box for cpu.

    It should default to rendering on the gpu after that.

    Next check your log file and see if for some reason it's dropping to cpu due to exceeding gpu ram. Shouldn't if you're only rendering a chair, but weirder stuff has happened.

    So you're not going through an insane number of lines of code, delete the log file, C:\Users\[name]\AppData\Roaming\DAZ 3D\Studio4, while daz studio is running then hit the render button.

    The appdata folder is hidden by default so you'll need to go into control panel>folder options>View tab>tick Show hidden files folders and drives.

     

    Hopefully that'll give you a starting point

     

  • cm152335cm152335 Posts: 421

    be sure toi use 64bit version ! 

  • TojiroTojiro Posts: 64

    It's happening to me too.  RTX 2080 with the newest drivers and Daz 4.11, but even a simple render of G8F with nothing else falls to CPU after a few IRAY iterations.  

  • same here with the gtx 1070 even after updating and rolling back the driver 

  • PakmulePakmule Posts: 25

    Yes I am saying that it is defaulting to CPU rendering rather than GPU. It does it even if I uncheck the CPU option in the advanced render settings I will check the log files and see what I find.

    Are you saying that it's rendering in CPU, not GPU? The last statement "Since then it's nothing but software" is kinda throwing me.

    First double check and make sure the render setting is correct.

    Render settings>Advanced, tick the box for the gpu untick the box for cpu.

    It should default to rendering on the gpu after that.

    Next check your log file and see if for some reason it's dropping to cpu due to exceeding gpu ram. Shouldn't if you're only rendering a chair, but weirder stuff has happened.

    So you're not going through an insane number of lines of code, delete the log file, C:\Users\[name]\AppData\Roaming\DAZ 3D\Studio4, while daz studio is running then hit the render button.

    The appdata folder is hidden by default so you'll need to go into control panel>folder options>View tab>tick Show hidden files folders and drives.

     

    Hopefully that'll give you a starting point

     

     

  • PakmulePakmule Posts: 25

    I thought I had it fixed as I got it to render on the GPU a few times in a row. Then today...

    2019-07-09 16:02:31.689 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(302): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.

  • Pakmule said:

    I thought I had it fixed as I got it to render on the GPU a few times in a row. Then today...

    2019-07-09 16:02:31.689 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(302): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.

    Sounds like a driver issue, might either try rolling back to the previous driver, or switching to the Studio driver as opposed to the Game ready driver, or vice versa if already using the studio driver.

     

  • PakmulePakmule Posts: 25

    A new game ready driver was released on the 9th that might have solved the issue. I've gotten a couple of renders to use the GPU.

    Pakmule said:

    I thought I had it fixed as I got it to render on the GPU a few times in a row. Then today...

    2019-07-09 16:02:31.689 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(302): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.

    Sounds like a driver issue, might either try rolling back to the previous driver, or switching to the Studio driver as opposed to the Game ready driver, or vice versa if already using the studio driver.

     

     

  • Have you tried the studio drivers?

    Suposedly, according to nvidia, their supposed to be more stable in 3d applications than the game ready drivers.

  • It happens to me too.

    Everyone putting this on driver issues is probably wrong - I downloaded the latest drivers, and the GPU still chooses not to be used. I have a GTX 680, btw.

    On another thread someone said this appears to be an issue called "CPU swapping". Basically the scenes you're trying to render take up so much memory or VRAM (whatever it is) that Daz decides not to use the GPU what so ever.

    I test rendered some scenes that aren't as intensive, and lord and behond my GPU decides to use it. I then test render a full scene with props, walls and a character, and the GPU stops working again.

    Your drivers are likely fine. This requires another solution.

  • Richard HaseltineRichard Haseltine Posts: 102,309

    It happens to me too.

    Everyone putting this on driver issues is probably wrong - I downloaded the latest drivers, and the GPU still chooses not to be used. I have a GTX 680, btw.

    On another thread someone said this appears to be an issue called "CPU swapping". Basically the scenes you're trying to render take up so much memory or VRAM (whatever it is) that Daz decides not to use the GPU what so ever.

    I test rendered some scenes that aren't as intensive, and lord and behond my GPU decides to use it. I then test render a full scene with props, walls and a character, and the GPU stops working again.

    Your drivers are likely fine. This requires another solution.

    The GPU has its own memory. In order for iray to use the GPU the scene (including the textures) must fit into that memory. It's quite likely that your 680 has very limited amounts of memory, so it easily runs out.

  • 3Ddreamer3Ddreamer Posts: 1,312

    I have scenes that rendered on GPU in 4.10 and fall back to CPU in 4.11 almost immediately - same scene. Also have the first render be blank (checkerbox) 99% of the time in 4.11 - I've a ticket open for it. I was going to downgrade to 4.10 yesterday, because I want to use GPU, only to find I'd backed up the 4.10 Beta and not the final 4.10 :-( I've a 980M and the 430.86 driver from the NVidia site. So there is something up with 4.11 and GPU.

  • FasterSceneFasterScene Posts: 8
    edited July 2019
    3Ddreamer said:

    ...So there is something up with 4.11 and GPU.

    I agree with this statement. I have a GPU Iray test scene (1 sphere and nothing else) that renders in 4.10 in about a minute usng my NVIDIA GeForce GTX 1070 Ti.

    In 4.11 and 4.12 the Iray rendering using the GPU fail 100% of the time

    I have the latest NVIDI drivers (431.60-desktop-win10-64bit) that all work in 4.10 but do not want to render in 4.11 or 4.12 Beta

    In both cases (4.11 and 4.12 Beta) the log says:

     WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    Iray Render error: Invalid parameters (NULL pointer).

     I roll back to 4.10 and the problem resolves. All well and good but I would like to upgrade to 4.11 and beyond.

    Post edited by FasterScene on
  • Richard HaseltineRichard Haseltine Posts: 102,309
    Jazma said:
    3Ddreamer said:

    ...So there is something up with 4.11 and GPU.

    I agree with this statement. I have a GPU Iray test scene (1 sphere and nothing else) that renders in 4.10 in about a minute usng my NVIDIA GeForce GTX 1070 Ti.

    In 4.11 and 4.12 the Iray rendering using the GPU fail 100% of the time

    I have the latest NVIDI drivers (431.60-desktop-win10-64bit) that all work in 4.10 but do not want to render in 4.11 or 4.12 Beta

    In both cases (4.11 and 4.12 Beta) the log says:

     WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    Iray Render error: Invalid parameters (NULL pointer).

     I roll back to 4.10 and the problem resolves. All well and good but I would like to upgrade to 4.11 and beyond.

    This using the same release channel (all Public Build or al General Release)?

  • This using the same release channel (all Public Build or al General Release)?

    Public Build for 4.12 Beta

    General release for 4.11

  • OK, the only other thing I can suggest is fully uninstalling the driver and reinstalling - sometimes the update isn't clean. If that doesn't work all I can suggest, assuming no one else has any ideas, is opening a support ticket.

  • Hello gang....I have several pc’s running Daz, one with a 1080Ti and another with dual Titan X GPUs....the Titan machine is still on 4.10 and the 1080 machine is running 4.11 and won’t even render an Iray preview with GPU, let alone a simple render. I tried the machine running 4.10 and it renders fine with the GPU(s). I’m running fairly stale GPU drivers on both machines (6-8 months or so since updating them). I think this is an issue with 4.11 somehow, as my problems started after updating the one PC. I will probably start a ticket. Thanks for all the info above!

  • What is the driver version?

  • Steel RatSteel Rat Posts: 398

    Hello gang....I have several pc’s running Daz, one with a 1080Ti and another with dual Titan X GPUs....the Titan machine is still on 4.10 and the 1080 machine is running 4.11 and won’t even render an Iray preview with GPU, let alone a simple render. I tried the machine running 4.10 and it renders fine with the GPU(s). I’m running fairly stale GPU drivers on both machines (6-8 months or so since updating them). I think this is an issue with 4.11 somehow, as my problems started after updating the one PC. I will probably start a ticket. Thanks for all the info above!

    I've got a GTX1060 in my laptop, and it also won't render with GPU only under Iray. Fails as soon as it starts the actual render process.

  • I just upgraded to 4.11 and have had no issues 
    but a couple commenters mentioned windows 10 --- so maybe system issue?
    I use w7 ... 980ti and titanx nvidia driver 360.64 
    I've done at least 25 renders including several at 4000x3200 and one of those had Sy's drips and droplets over 3 bodies. That one took 2 hours but never dropped to cpu.
    but I have a 12g card in the mix. 
    But I have 2 monitors and often am running another program or a second instance of daz while one is rendering.  Even did a second render today while another one was going with no problems. 
    ---
    so Win7 or win10? How close is the card load to it's max? if it's a 6g card and it's at 5777m .. maybe old iray was okay and new one says wait that's too close?
    ---
    several folks mentioned stuff that ran in 410 not functioning in 411..  could be the new iray render set is reading the scenes differently and thinking more memory? 
    ---
    I use gpu shark and check gpu usage before and during renders. 

  • I just discovered I lied in the previous comment.
    4.11 handles something a lot differently. 
    Have a big scene that I decided to run with the new titan and the 980ti
    attached picture .. done with 980ti and 1050 so max of 6g if the 1050 was dropped. 
    ---
    started rendering same size 2000x1000 
    ----
    sitting, sitting... all of a sudden it's on the cpus .. got BES started and limited Daz to 66% of cpus
    ---
    looked at cards in GPU shark ..  titanx at 11,550 and 980 shut off at 0. 
    ----
    stopped the render, got the gpu down from 11,550 to 2400 (there's a 43 in screen attached to the 980ti and only a 23 on the titanx 
    ---
    but it also took down my facebook screens including the forum comments I had open...  took them to non-responing and had to force quit them.
    ---
    I will now go back to the scene file and do another render using the exact same position and see what happens 
    if it does the same than there's been a change (not necessarily for the better) in how 4.11 is processing iray as opposed to 4.10
    ---
    first picture completed 2kx1k on 980/1050 6g --second one that went to cpu from titanx/980 12g
    ===
    I did move to a different location .. so will reset to previous camera etc and see what happens

     

    mewYorkv3 take 4w.jpg
    1991 x 782 - 617K
    mew york fail to cpuw .jpg
    2000 x 1000 - 908K
  • you might not want to use 4.11 any way. 
    ---
    after the crash to cpu above I went back and retested. 
    ---
    same scene that worked in 4.10 did work in 4.11
    when I switched back to the same camera so everything was the same. 
    But I saw why it switched to cpu ..  I had an extra scene open in another window that used some memory.
    ---
    but closing that extra little daz scene that I use to build object in during renders on the main daz scene
    meant that the titanx only loaded to 12090m just a tad under the potential of 12200m available
    so it rendered successfully in 4.11 using 12090 of 12200 . (lucky I didn't have one of those 11g cards.
    and it took 1 hour 1 minute and 44 sec. 
    ---
    so it closed it and opened the scene in 4.10 
    memory usage 10310m so it looks like 4.10 doesn't use quite as much memory as 4.11 can use. 
    so should have rendered a little slower? Well, no ... 50m 27 sec.  15% faster 
    ----
    interesting .. don't throw away 4.10 yet. 
    ---
    as for me, I think I'm going to see if I can find another titanx with 12g
    because when the render is small enough to stay on both cards titanx and 980ti which are pretty close except for the memory .. render times are about half of what one card takes.
    so with two 12g cards .. that would have been a 25 minute render. 
    1) gpu data during 4.11 render 2) gpu data during 4.10 render 3) rendered image 

    and now at 12090.jpg
    487 x 751 - 254K
    410 memusage.jpg
    487 x 751 - 189K
    titanx 410 50m 27s-w.jpg
    2000 x 1000 - 1M
Sign In or Register to comment.