Loading...
> >

Iray render crashes after updating to DS 4.21

2»

Comments

  • IceCrMnIceCrMn Posts: 2,129

    There is also an "unconfirmed bug" with the special shader that the Out Of Touch (OOT) hairs use.

    If you are using any of those try removing them from the scene and see if it will stop the CTD on render/render preview.

  • Richard HaseltineRichard Haseltine Posts: 100,739

    IceCrMn said:

    There is also an "unconfirmed bug" with the special shader that the Out Of Touch (OOT) hairs use.

    I think it is confirmed in the sense that Daz is aware of and investigating it, though I don't know if they have yet figured it out.

    If you are using any of those try removing them from the scene and see if it will stop the CTD on render/render preview.

  • IceCrMnIceCrMn Posts: 2,129

    I should have also pointed out that this OOT hair bug only seems to be present in the current beta and NOT the current General release.

  • alan bard newcomeralan bard newcomer Posts: 2,163

    Richard Haseltine said:

    tom.rowlandson.1727 said:

    Further tests (now with Nvidia's Game Ready driver, version 522.25) shows that DS 4.21 doesn't release GPU memory after finishing a render, requiring a restart of DS, plus several minutes of waiting for GPU memory to be released by the system, and then reloading the scene, before making a second render. Problems I've never had before.

    And still further tests show that it's after having made an Iray-preview of a render in the viewport that DS 4.21 won't release GPU memory, so when I try to make a full render of the scene I just previewed DS forces a CPU render, with a much longer render time, since it's still holding, but apparently not using, all the GPU memory it had used during the viewport preview (in addition to using much more GPU memory than DS 4.2 did), and the only way to get it to release the GPU memory is to close DS, wait a few minutes and then open DS again, etc..

    Not releasing memory at all without a restart sounds like Iray running out of memory.

    daz has always been picky about releasing memory. s
    but doing the same scene with minor changes does seem to create the issue where  (at times it seems) the second render goes faster .. because data is still in gpu memory.. but changing major items it will have issues putting it all on card.  

  • jeremy-2558557jeremy-2558557 Posts: 17

    DS 4.21 Public build is also crashing for me via preview render and render. 

  • PerttiAPerttiA Posts: 10,024

    How much RAM do you have?

  • harrysamharrysam Posts: 6

    Same exact problem. Daz is now unusable. If I even select the IRAY viewing tab it hangs and crashes. Can't render because the renders never complete. Never had this problem before with any other version. Drivers are up to date. Filed a support ticket and it took over a month to respond and that was just asking if I still had the problem. Completely useless. I'm now doing all my renders in Iclone. At least I get an answer there when things are broken. So disappointing. 

  • TaozTaoz Posts: 9,940
    edited November 2022

    IceCrMn said:

    I think 4.21 reintroduced the .tif bug.

    Certain tif files were crashing Studio a few versions ago.

    I just tested with a clothing item that I know uses tif files for the normal maps and I can crash Studio 4.21 100% of the time by either starting the iray preview or a render.

    Same here though I thought it had been there all the time (had the problem in an earlier version of DS but haven't used the product that caused it since, before testing again now in 4.21).

    Otherwise no problems with rendering in 4.21, using the latest driver.

    Post edited by Taoz on
  • vecvec Posts: 37

    Taoz said:

    IceCrMn said:

    I think 4.21 reintroduced the .tif bug.

    Certain tif files were crashing Studio a few versions ago.

    I just tested with a clothing item that I know uses tif files for the normal maps and I can crash Studio 4.21 100% of the time by either starting the iray preview or a render.

    Same here though I thought it had been there all the time (had the problem in an earlier version of DS but haven't used the product that caused it since, before testing again now in 4.21).

    Otherwise no problems with rendering in 4.21, using the latest driver.

    The entire time ive been using daz I havent had any problem with tif files now since updating to 4.21 I crash. I have to check every texture now in every scene before trying to render or preview which is very annoying just found out a characters mouth texture uses .tif after spending a hour setting up a scene

  • Miss AnimatedMiss Animated Posts: 53
    edited July 2023

    Same problem.  It has now been nine months and NO RESOLUTION OR WORKAROUND FROM EITHER NVIDIA OR DAZ??? Highly unacceptable I'm afraid.  If something has been found, please post here too.  This is the top of the Google Search for this issue...

    I went back to 4.20 and had NO ISSUES.  Another issue I had compelled me to go back to 4.21 and lo and behold, crash again!

    Switching back to 4.20.   Come on folks, we gotta get this right whoever it is.  BOTH places look bad...

    nVidia driver 536.67 now...

    Post edited by Miss Animated on
  • Miss AnimatedMiss Animated Posts: 53

    Just switched back to 4.20 and rendering is restored.  Can't be an nVidia thing...

  • barbultbarbult Posts: 24,240

    Miss Animated said:

    Just switched back to 4.20 and rendering is restored.  Can't be an nVidia thing...

    Of course it can. NVIDIA provides new versions of Iray that Daz incorporates into Daz Studio. 4.20 does not use the same version of NVIDIA Iray that 4.21 uses.

  • Miss AnimatedMiss Animated Posts: 53

    Well, someone heard me because 4.23 works!!!! I'm back in sync with the world now.  Good to be back and modern.

Sign In or Register to comment.