Studio crashing suddenly and IMO irrationally

This problem is frustrating because the scene I've been rendering has been working well and suddenly started crashing a few minutes after loading. I do a little work save do some more and it crashes. I've reduced the scene to one character visible and opened in wireframe but I keep getting this on the log:


2018-03-02 00:36:25.863 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00239 iterations after 5.489s.
2018-03-02 00:36:26.077 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00250 iterations after 5.702s.
2018-03-02 00:36:26.269 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00260 iterations after 5.895s.
2018-03-02 00:36:26.493 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00270 iterations after 6.118s.
2018-03-02 00:36:26.669 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00279 iterations after 6.295s.
2018-03-02 00:36:26.872 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00289 iterations after 6.498s.
2018-03-02 00:36:27.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00299 iterations after 6.696s.
2018-03-02 00:36:27.243 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00309 iterations after 6.869s.
2018-03-02 00:36:27.473 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00320 iterations after 7.099s.
2018-03-02 00:36:27.668 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00330 iterations after 7.294s.
2018-03-02 00:36:27.865 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00340 iterations after 7.491s.
2018-03-02 00:36:28.053 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00350 iterations after 7.679s.
2018-03-02 00:36:28.242 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00361 iterations after 7.868s.

Should I be getting render info if I'm not rendering? I'm still in wireframe. The single figure is easy to work with and the scene is very navigable. I'm running OS Sierra 10.12.6 with up-to-date drivers on a mid-2012 Mac Pro with 16GB memory, an Nvidia 1070 with 8GB VRAM and am using Studio 4.10. The card has it's own power supply. I have unchecked the box for the improvement program and after the first few crashes am working offline. The figure is a single G8 Male (Chance). The scene normally has 4 figures, a number of props, an environment and environmental lighting and it was working and rendering prior to this in Iray without any problems. Help.

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,882

    Make sure you don't have another view (such as the Aux Viewport) set to use the Iray preview mode.

  • Richard--thanks for the quick response. The Aux. viewport was set to texture shaded and was not open when I loaded the files (would this make a difference?). To be on the safe side I set the viewport to wireframe and closed it before trying to open the file. It crashed again on loading. The log file is again a long series of render commands followed by this:

    2018-03-02 19:32:53.971 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00145 iterations after 3.710s.
    2018-03-02 19:32:54.111 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Device statistics:
    2018-03-02 19:32:54.111 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1070):      145 iterations, 0.116s init, 3.714s render
    2018-03-02 19:32:54.111 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CPU:      145 iterations, 0.030s init, 3.783s render
    2018-03-02 19:33:45.931 WARNING: /src/sdksource/cloud/dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0

     

    The file is being opened in wireframe, so I'm not sure why it's rendering. The scene has a number of Photoshop modified texture and bump/normal maps and some meshes that were modified in Zbrush but as I say it rendered smoothly before. Studio opens less complex scenes but has started to crash attempting to load complex scenes that were previously loading without any issues. 

     

  • Richard HaseltineRichard Haseltine Posts: 102,882
    edited March 2018

    What does the log say at the beginning of the Iray rendering?

    Post edited by Richard Haseltine on
  • This is the beginning of that log --I haven't included the whole thing since it goes on like this:


    2018-03-02 19:32:33.113 +++++++++++++++ DAZ Studio 4.10.0.123 starting +++++++++++++++++
    2018-03-02 19:32:33.113 Platform bits: 64
    2018-03-02 19:32:33.113 Qt Version: 4.8.7
    2018-03-02 19:32:33.113 OpenSubdiv Version: 3.0.0
    2018-03-02 19:32:33.113 Running on Macintosh OS 10.12 Sierra
    2018-03-02 19:32:33.113 Current DateTime:
    2018-03-02 19:32:33.113     Loc: Fri Mar 2 19:32:33 2018
    2018-03-02 19:32:33.149     UTC: Sat Mar 3 03:32:33 2018
    2018-03-02 19:32:33.150 Temp Data:
    2018-03-02 19:32:33.150     Location = /Users/jc2/Library/Application Support/DAZ 3D/Studio4/temp
    2018-03-02 19:32:33.150     Disk Total: 1.8 TB (1999539175424)
    2018-03-02 19:32:33.150     Disk Avail: 1.4 TB (1610822066176)
    2018-03-02 19:32:33.150 Locale: en_US
    2018-03-02 19:32:33.150     No translator found.
    2018-03-02 19:32:33.211 Creating Plugin Manager...
    2018-03-02 19:32:33.216 Reading style definition /Applications/DAZ 3D/DAZStudio4 64-bit/resources/style/Darkside.style
    2018-03-02 19:32:33.636 Creating Import Manager...
    2018-03-02 19:32:33.636 Creating Export Manager...
    2018-03-02 19:32:33.637 Creating File IO Preset Manager...
    2018-03-02 19:32:33.654 Creating Save Filter Manager...
    2018-03-02 19:32:33.654 Creating Asset IO Manager...
    2018-03-02 19:32:33.654 Creating Image Manager...
    2018-03-02 19:32:33.655 Creating Help Manager...
    2018-03-02 19:32:33.655 Reading help index
    2018-03-02 19:32:33.662 Reading help file /Applications/DAZ 3D/DAZStudio4 64-bit/docs/DAZ Studio/DAZStudioHelp.dsx
    2018-03-02 19:32:33.666 Reading help file /Applications/DAZ 3D/DAZStudio4 64-bit/docs/bookmarks.dsx
    2018-03-02 19:32:33.666 Reading help file /Applications/DAZ 3D/DAZStudio4 64-bit/docs/inlinehelp.dsx
    2018-03-02 19:32:33.699 Creating Multimedia Manager...
    2018-03-02 19:32:33.699 Creating Content Manager...
    2018-03-02 19:32:33.760 WARNING: /src/sdksource/general/dzcontentmgr.cpp(1820): Nested directory encountered while adding a Poser folder: /Users/Shared/My DAZ 3D Library/Poser 11 Content/Downloads/Moctezuma : /Users/Shared/My DAZ 3D Library
    2018-03-02 19:32:33.783 WARNING: /src/sdksource/general/dzcontentmgr.cpp(1820): Nested directory encountered while adding a Poser folder: /Users/Shared/My DAZ 3D Library : /Users/Shared

    I wanted to ask, since you seem to be the most knowledgable person on the forums and since Daz doesn't seem to be planning to add auto-save capability to Studio, do you know of any third party software or plugins that might be able to do auto-saves? I've looked at Super Save but it doesn't seem to have an automatic interval or modification based save function. The three main programs I work with--Zbrush, Photoshop, and Modo all save incrementally and automatically and Zbrush and Photoshop save completely in the background. While I save regularly, there are times when I get hyperfocused and a crash will cause me to lose a lot of work in Daz and, at least on my computer, Daz crashes a lot. Any suggestions you might have would be appreciated. Thanks.

  • Richard HaseltineRichard Haseltine Posts: 102,882

    It's really the bit at the begiining of the render and just before that is of interest, to see what it is doing then. I do notice you have nested content directories - a folder seelcted as a content diectory that contains another folder seelcted as a content directory - but I doubt that is the cause of your crash.

    AutoSave would require a plug-in - I don't know if an external application could do it. Writing a script to save before rendering ought to be possible.

  • The problem is that I'm not rendering when I open the file. This also seems to cause a problem when I shut Daz Studio down. I almost always have to force quit and from what I've seen online, that's usually a problem with a render thread. Is it the Iray preview that causes this?  I rarely open or close a file in Iray. I switch to wireframe because it seems to load faster than the other Draw Styles. Does Studio render in the background? I've been checking the logs for render info and it seems like they all contain some render issues even when I don't render.

    In future threads and this one, I'm won't continue to whine about autosave but I guess I'm curious what the reasoning is behind not having it. I've seen the subject come up on the forums a number of times.The complexity and crashiness (is that a word?) of 3d software would seem to dictate it. Are there other 3d programs that don't have autosave? Illustrator was another program with crash tendencies that for many years didn't have autosave and would wipe out work but it now has the same recovery file saves that Photoshop has. I appreciate the suggestion about scripts, but I'm afraid I don't know enough about scripting to write one for saving at intervals. 

  • Richard HaseltineRichard Haseltine Posts: 102,882

    You may not be rendering by intent, but the log shows that a render is happening.

  • Thanks for your help on this. Any suggestions on how I would find the source of the render? I've checked viewports, preferences, and tried to make things as lightweight as possible. Is there something I'm missing?  

  • Richard HaseltineRichard Haseltine Posts: 102,882

    Find the start of the Iray messages in the log file, that area should give more information.

Sign In or Register to comment.