Loading...
> >

Daz crashes whenever I try to use Iray

UthgardUthgard Posts: 867
edited November 2020 in The Commons

All right, I downloaded the latest drivers for my GPU (GTX 1080), reinstalled Studio, and rebooted my computer, but, as the title says, whenever I try to render in Iray (I can use canvasses, but not render a still or use the viewport), Studio crashes. The first few times there wasn't even an error message, but now I consistently get "DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libneuray.dll" at 0033:00000000795C4526, mi_neuray_factory_deprecated()+6818566 byte(s)." I don't know whether anyone in the forum can help, but seeing as I am unable to access the support page to file a ticket because that leads to an error page... Well, anyone's guess is welcome.

Edit: Never mind the part about the ticket, I can manually find the page, it's just the link from the error message that gets borked.

Post edited by Uthgard on

Comments

  • BeeMKayBeeMKay Posts: 7,019
    edited November 2020

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Post edited by BeeMKay on
  • SevrinSevrin Posts: 6,310

    What Nvidia driver is installed?

  • UthgardUthgard Posts: 867
    BeeMKay said:

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Good catch! My default scene loads with a few primitives with non-standard shaders (because if they aren't present on scene load, Studio doesn't process them; weird, I know). Clearing the scene worked, as did loading other figures. What I need to know now is why the heck Studio suddenly decided a few primitive planes with shaders are enough to bring Iray to its knees.

    Sevrin said:

    What Nvidia driver is installed?

    I tried with both the gamer and the developer version.

  • Richard HaseltineRichard Haseltine Posts: 102,797
    Uthgard said:
    BeeMKay said:

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Good catch! My default scene loads with a few primitives with non-standard shaders (because if they aren't present on scene load, Studio doesn't process them; weird, I know). Clearing the scene worked, as did loading other figures. What I need to know now is why the heck Studio suddenly decided a few primitive planes with shaders are enough to bring Iray to its knees.

    Sevrin said:

    What Nvidia driver is installed?

    I tried with both the gamer and the developer version.

    Which number?

  • kgrosserkgrosser Posts: 141
    edited November 2020
    Richard Haseltine said:

    Which number?

    I don't think this does matter to the extent it is stressed here when this issue comes up, as long as it is a recent driver. I am saying this as I keep stumbling into it ever aftzer 4.10 and started on 4.12 with the recommended driver (forgot the rev but i think it was 435). Meanwhile I rolled forth and back in between, swapped GRD with SD variations and yet couldn't track or solve it. So, welcome to the club, @Uthgard. Funnily I can render fine, but Iray viewport is triggering this reliably for me. And yes it seems memory related, not capacity but reactivity though, I get this alo on smaller scenes that fit into the 11GB of my 1080Ti, but crash when swapping/loading new items with iray mats or do fast camera transforms.It's about time nvidia releases that 380Ti 20GB card....

    Post edited by kgrosser on
  • UthgardUthgard Posts: 867
    Richard Haseltine said:
    Uthgard said:
    BeeMKay said:

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Good catch! My default scene loads with a few primitives with non-standard shaders (because if they aren't present on scene load, Studio doesn't process them; weird, I know). Clearing the scene worked, as did loading other figures. What I need to know now is why the heck Studio suddenly decided a few primitive planes with shaders are enough to bring Iray to its knees.

    Sevrin said:

    What Nvidia driver is installed?

    I tried with both the gamer and the developer version.

    Which number?

    457.30

     

    kgrosser said:
    Richard Haseltine said:

    Which number?

    I don't think this does matter to the extent it is stressed here when this issue comes up, as long as it is a recent driver. I am saying this as I keep stumbling into it ever aftzer 4.10 and started on 4.12 with the recommended driver (forgot the rev but i think it was 435). Meanwhile I rolled forth and back in between, swapped GRD with SD variations and yet couldn't track or solve it. So, welcome to the club, @Uthgard. Funnily I can render fine, but Iray viewport is triggering this reliably for me. And yes it seems memory related, not capacity but reactivity though, I get this alo on smaller scenes that fit into the 11GB of my 1080Ti, but crash when swapping/loading new items with iray mats or do fast camera transforms.It's about time nvidia releases that 380Ti 20GB card....

    Dammit, as if I didn't have enough mysterious bugs already...

  • BeeMKayBeeMKay Posts: 7,019
    edited November 2020
    Uthgard said:
    BeeMKay said:

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Good catch! My default scene loads with a few primitives with non-standard shaders (because if they aren't present on scene load, Studio doesn't process them; weird, I know). Clearing the scene worked, as did loading other figures. What I need to know now is why the heck Studio suddenly decided a few primitive planes with shaders are enough to bring Iray to its knees.

    Sevrin said:

    What Nvidia driver is installed?

    I tried with both the gamer and the developer version.

    It could be the non-standard shader. I don't know how they are set up, though I do recall a set of shaders sold here at the store that I stopped using because it crashed Studio every time I used them. It workd fine until DS 4.9, and then started acting up when they intruduced a newer version of Iray. They also changed to a newer version of Iray in the 4.14 version.

    Here are things that are worth looking into:

    EDIT: I did a bit of search, and there's a thread for the problem over at the Tech part of the forum, though to not much of a result (outside of it appearing to be a shader problem): https://www.daz3d.com/forums/discussion/451741/iray-preview-render-causes-daz-to-crash

    And you can read about the error code here: https://raytracing-docs.nvidia.com/mdl/api/html/group__mi__neuray__ineuray.html

     

    Post edited by BeeMKay on
  • 3Diva3Diva Posts: 11,748
    edited November 2020
    Is one of your non-standard shaders Oso Blendy, by chance? There's a known issue that Blendy crashes Daz Studio upon starting an Iray render or Iray preview.
    Post edited by 3Diva on
  • UthgardUthgard Posts: 867
    BeeMKay said:
    Uthgard said:
    BeeMKay said:

    Does that happen even if you just have a primitive in your scene? The error message looks as if your VRAM and RAM isn't sufficient to handle the scene you try to render, basically, you are out of memory.

    Good catch! My default scene loads with a few primitives with non-standard shaders (because if they aren't present on scene load, Studio doesn't process them; weird, I know). Clearing the scene worked, as did loading other figures. What I need to know now is why the heck Studio suddenly decided a few primitive planes with shaders are enough to bring Iray to its knees.

    Sevrin said:

    What Nvidia driver is installed?

    I tried with both the gamer and the developer version.

    It could be the non-standard shader. I don't know how they are set up, though I do recall a set of shaders sold here at the store that I stopped using because it crashed Studio every time I used them. It workd fine until DS 4.9, and then started acting up when they intruduced a newer version of Iray. They also changed to a newer version of Iray in the 4.14 version.

    Here are things that are worth looking into:

    EDIT: I did a bit of search, and there's a thread for the problem over at the Tech part of the forum, though to not much of a result (outside of it appearing to be a shader problem): https://www.daz3d.com/forums/discussion/451741/iray-preview-render-causes-daz-to-crash

    And you can read about the error code here: https://raytracing-docs.nvidia.com/mdl/api/html/group__mi__neuray__ineuray.html

     

    Wow, thank you for your detailed help, I'll be sure to look into it and report if I manage to find out what is happening.

     

    3Diva said:
    Is one of your non-standard shaders Oso Blendy, by chance? There's a known issue that Blendy crashes Daz Studio upon starting an Iray render or Iray preview.

    Sadly, that isn't the problem. I tried erasing them one by one, but managed not to get a crash just by deleting a sample of DimensionTheoyr's Cloudscapes. I would say that's the most likely culprit, but I would rather make more tests before I get too confident about Studio not crashing at the drop of a hat. Mostly, because the crashes started happening in a scene without those shaders loaded and then things deteriorated to the point of the auto-crash.

  • 3Diva3Diva Posts: 11,748

    You could save that Cloudscapes sample alone as a scene subset and with a fresh new scene, load that up and see if it crashes.

  • SevrinSevrin Posts: 6,310

    At one point there were issues with products using the Muelsfell shaders crashing DS in Iray, but those were straightened out. 

  • UthgardUthgard Posts: 867

    Cloudscapes definitely crashes Iray, what I don't know is whether other things will also do it, seeing as the scene that crashed the first time around only had Iray Uber items and a 3Delight hair loaded in (and that scene currently works).

  • hestera_e6928a560fhestera_e6928a560f Posts: 4

    I know this is quite late to this thread, but in case anyone else does come across this, I too had the same problem with some scenes that rendered fine once I updated to 4.15.  The problem I had was with the Leo 7 and Ivan 7 figures.  Turning off the Normal Map fixed the problem and stopped the crashes.  I know that there is probably a way to also combine those maps to fix the problem, but this was the simplest way and still gave me the results I wanted.

  • sakrilassakrilas Posts: 10

    hestera_e6928a560f said:

    I know this is quite late to this thread, but in case anyone else does come across this, I too had the same problem with some scenes that rendered fine once I updated to 4.15.  The problem I had was with the Leo 7 and Ivan 7 figures.  Turning off the Normal Map fixed the problem and stopped the crashes.  I know that there is probably a way to also combine those maps to fix the problem, but this was the simplest way and still gave me the results I wanted.

    I had the same problem when trying to render Kennedy Socks by 3D Universe.

    Even a scene with just the socks by themselves is crashing.

    After reading your comment I looked more into the issue, the Normal Map was the only .tif file in there. After I converted it from .tif to .jpg, the socks stopped causing the iray preview to crash.

    In short, if anyone else is having this issue, check to see if you're using a .tif file for textures, iRay appears to be having a hard time handling this file format.

Sign In or Register to comment.