Loading...
> >

IRAY rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severe

heinzerbrew_f94794efffheinzerbrew_f94794efff Posts: 236
in The Commons

IRAY   rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance.

So when I learned I could start an Iray render then cancel it and resume it later. I was excited. In the log I get the above message when resuming renders. Can someone explain the "reduce performance" part?

Comments

  • acanthisacanthis Posts: 604
    edited January 2016

    .

    Post edited by acanthis on
  • Richard HaseltineRichard Haseltine Posts: 108,098
    acanthis said:

    I don't know about the reduced performance message, but it is a well known problem with the version of iRay that comes with DS 4.8 that repeated stop/starts will lead to a crash sooner or later - usually after you have let it render for 37 hours and it's just about reached where you want it to be but you haven't saved it yet!

    The render should still be in the temp folder after a crash. C:\Users\You\AppData\Roaming\DAZ3D|Studio4\Temp\Render on Windows. Grab it before restarting DS.

  • nDelphinDelphi Posts: 1,921
    acanthis said:

    I don't know about the reduced performance message, but it is a well known problem with the version of iRay that comes with DS 4.8 that repeated stop/starts will lead to a crash sooner or later - usually after you have let it render for 37 hours and it's just about reached where you want it to be but you haven't saved it yet!

    After 37 hours? Figures why I have never run into this issue because I stop and start renders a lot. My renders run from 6- to 9-hours (the most).

  • acanthisacanthis Posts: 604
    edited January 2016
    Richard Haseltine said:
    acanthis said:

    I don't know about the reduced performance message, but it is a well known problem with the version of iRay that comes with DS 4.8 that repeated stop/starts will lead to a crash sooner or later - usually after you have let it render for 37 hours and it's just about reached where you want it to be but you haven't saved it yet!

    The render should still be in the temp folder after a crash. C:\Users\You\AppData\Roaming\DAZ3D|Studio4\Temp\Render on Windows. Grab it before restarting DS.

    .

    Post edited by acanthis on
  • heinzerbrew_f94794efffheinzerbrew_f94794efff Posts: 236
    acanthis said:

    I know about that folder but the last few times it happened to me, before I adopted the Mandatory Reboot regime, I found nothing there.

    After you cancel the render you can go to that folder and snag the file; it won't be there until you cancel. then you can resume again.

  • AbnerKAbnerK Posts: 718
    edited November 2018
    heinzerbrew_f94794efff said:
    acanthis said:

    I know about that folder but the last few times it happened to me, before I adopted the Mandatory Reboot regime, I found nothing there.

    What is the 'Mandatory Reboot refibme'? I have the same problem. If my Daz or the computer  crashes I don't find anything in the temp folder. I get the impression people are all talking about different things. Have these posts been edited out of recognition? I only get anything in the temp/render folder if I cancel or the render stops. If Daz crashes there's nothing there. 

    Thanks

    Post edited by AbnerK on
  • Richard HaseltineRichard Haseltine Posts: 108,098

    If the crash happens after the render has started then the progress so far should be there, until DS is restarted.

  • AbnerKAbnerK Posts: 718
    edited November 2018
    Richard Haseltine said:

    If the crash happens after the render has started then the progress so far should be there, until DS is restarted.

    Thanks Richard, I'll test it with a force quit, however I would expect to see it there before the crash wouldn't I, if I had a crystal ball and knew to look? I know it isn't there during a render because I've looked thinking I could prepare my post processing. 

    Thanks 

    Post edited by AbnerK on
  • heinzerbrew_f94794efffheinzerbrew_f94794efff Posts: 236
    jimmac-donald said:
    heinzerbrew_f94794efff said:
    acanthis said:

    I know about that folder but the last few times it happened to me, before I adopted the Mandatory Reboot regime, I found nothing there.

    What is the 'Mandatory Reboot refibme'? I have the same problem. If my Daz or the computer  crashes I don't find anything in the temp folder. I get the impression people are all talking about different things. Have these posts been edited out of recognition? I only get anything in the temp/render folder if I cancel or the render stops. If Daz crashes there's nothing there. 

    Thanks

    Did you get this sorted out? 

    The only time you will find a temp render file in the temp folder is after you press cancel on the render window or the render has finished. If you restart, the file will be deleted when Daz launches next.

    If you have a crash during an Iray render there will not be a file in the temp folder unless at some point you had pressed cancel. Your progress on your render is not immediately written to a file it is kept in memory and is lost on crash.

    'Mandatory Reboot" I believe this is a euphemism, not a technical term.

  • grinch2901grinch2901 Posts: 1,247
    edited January 2019
    heinzerbrew_f94794efff said:

    IRAY   rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance.

    So when I learned I could start an Iray render then cancel it and resume it later. I was excited. In the log I get the above message when resuming renders. Can someone explain the "reduce performance" part?

    I was assuming the renderer is trying to say that when you stop a render the scene remains in memory, which is why you can resume it.  If you start a new render (as you would in batch mode) it will have to fit that new render onto the card in addition to the original paused scene. If they don't both fit it goes to CPU and performance turns to .... molasses.  I don't think restart part has anything yo do with reboot or crashes, it means restarting the rende which requires the scene to stay on GPU memory.

    If you save the render or close the window, Iray will finally remove the scene from the GPU memory.

    Post edited by grinch2901 on
  • heinzerbrew_f94794efffheinzerbrew_f94794efff Posts: 236
    grinch2901 said:
    heinzerbrew_f94794efff said:

    IRAY   rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance.

    So when I learned I could start an Iray render then cancel it and resume it later. I was excited. In the log I get the above message when resuming renders. Can someone explain the "reduce performance" part?

    I was assuming the renderer is trying to say that when you stop a render the scene remains in memory, which is why you can resume it.  If you start a new render (as you would in batch mode) it will have to fit that new render onto the card in addition to the original paused scene. If they don't both fit it goes to CPU and performance turns to .... molasses.  I don't think restart part has anything yo do with reboot or crashes, it means restarting the rende which requires the scene to stay on GPU memory.

    If you save the render or close the window, Iray will finally remove the scene from the GPU memory.

    I wasn't using batch mode when I got the message, which makes it more confusing. When I pause then resume it seems to continue where I left off. My use case does not involve more than one render in the gpu memory. It may be a bug that I was getting the warning. It has been a long time, and I stopped worrying about it already. I have know idea if get the message anymore, since I don't use the feature much any more.

Sign In or Register to comment.