IRay interactive - nothing rendered

marblemarble Posts: 7,500
edited June 2016 in Daz Studio Discussion

I have only just tried this for the first time since the DAZ Studio update to 4.9.2.70. I can use IRay Interactive mode in the viewport but if I try to render to a window in interactive mode - nothing happens. A window pops up and asks me if I want to save but nothing has been rendered.

Photoreal mode works just fine. I have the GTX970 selected for both Photoreal and Interactive in the Advanced settings. As I say, it works in teh Viewport and in the Aux viewport but I wanted to try an animation and I get nothing.

 

EDIT: If I open the timeline pane with the viewport in Interactive Draw, the scene switches to untextured  (grey) and I get an endless (10 minutes, so far) "Preparing Scene" progress bar.

Post edited by marble on

Comments

  • marblemarble Posts: 7,500
    edited June 2016

    Just rebooted and tried rendering to a window in Interactive mode and this time it was completely black. When I closed the render window, the viewport had retruned to untextured (grey) and stayed like that.

    EDIT: Just tried with a simple scene - one G2F figure. No problems.Seems to be related to the complexity of the scene but memory isn't a problem for that scene in Photoreal mode.

    Post edited by marble on
  • marblemarble Posts: 7,500

    This is the log. I started from fresh with the scene that has been failing. First try at Interactive worked. Second try failed - log says no memory.

    2016-04-02 17:04:53.061 Finished Rendering2016-04-02 17:04:53.093 Total Rendering Time: 1 minutes 18.54 seconds2016-06-02 17:06:39.376 Rendering image2016-06-02 17:06:41.757 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Creating irt render context (cache id: 0x0000000100000001).2016-06-02 17:06:43.167 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Disabling instancing.2016-06-02 17:06:43.167 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Rebuild all clusters.2016-06-02 17:06:43.932 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Scene update took 2.132140 seconds.2016-06-02 17:06:44.057 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : 72.8% of radiant power of environment in 0.2% of the solid angle.2016-06-02 17:06:44.807 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Creating multiscale environment representation of resolution 6000x3000 took 0.873422s2016-06-02 17:06:44.823 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Progressive buffer resolution 1024x819 (size: 819, offset: 0, stride: 2, block_size 2)2016-06-02 17:06:44.870 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : Out of GPU memory. Flushing all data.2016-06-02 17:06:44.870 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: CUDA 0 (GeForce GTX 970): Failed to allocate 326508000 bytes (311 MB) - Available memory 266747904 (254 MB)2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Cannot render: device failed.2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Failed on first frame. Dropping failing devices and re-rendering2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : All devices disabled.2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : There are no devices that can be used with IRT (Compute Capability 2.0 required)2016-06-02 17:06:44.917 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : -------------------------------------------------2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Cannot render. No devices activated.2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: No devices activated. Enabling cpu fallback2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : All devices disabled.2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : There are no devices that can be used with IRT (Compute Capability 2.0 required)2016-06-02 17:06:44.917 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : -------------------------------------------------2016-06-02 17:06:44.917 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Cannot render. No devices activated.2016-06-02 17:06:44.917 Iray Render error: No sufficiently capable GPUs or selected device combination not supported.2016-06-02 17:06:44.979 Saved image: C:\Users\David\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png2016-06-02 17:06:45.037 Finished Rendering2016-06-02 17:06:45.069 Total Rendering Time: 5.74 seconds2016-06-02 17:06:50.508 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Shutting down irt render context.

     

  • marblemarble Posts: 7,500

    Curiouser and curiouser - I put the same characters in another scene with more content, more clothing, furniture, etc. and that renders in both photoreal and interactive (and I have tried successive renders in case it was a problem of the VRAM not being cleared between renders).I have no clue as to why the first scene is failing.

  • ToborTobor Posts: 2,300
    edited June 2016

    In no particular order:

    1. Be sure you're not using mesh lighting. Interactive won't work with it.

    2. Devices are independently set in the Advanced tab for Photoreal and Interactive.

    3. It could be a shader or geometry that's crashing the scene for Interactive. A simple scene test (as you've done) can help answer that one.

    4. Try rebooting your PC from a cold start. Drivers can sometimes get hung up.

     

    Post edited by Tobor on
  • RuphussRuphuss Posts: 2,631

    i have this all the time with interactive

    and i know all things tobor says

    aux viewport renders but main black

    restarting daz most of the times let it work again

    theres something really wrong in 4.9 with rendering

     

  • marblemarble Posts: 7,500
    edited June 2016

    Thanks, both. 

    @Tobor - 1&2 were checked. As for 3 - I tried a simple scene and an even more complex scene and both rendered fine. The more complex scene contained all of the content of the failing scene plus more. Go figure. I did reboot several times but the failing scene continued to fail.

    @Ruphuss - I'm relieved that someone else has seen this. I was beginning to suspect my NVidia card again and I've just had the original one replaced under warranty.

    Post edited by marble on
  • ToborTobor Posts: 2,300

    To verify if it's card related, be sure to leave CPU checked as one of the rendering devices. If the card(s) fail, you should still have fallback to the CPU. I have occasionally run into this as well, and the problem only affectd rendering on the graphics card. The scene rendered (eventually) to completion using only the CPU. It was solved by rebuilding the scene from scratch. I have no idea what element, or elements, have caused it. In all the times, though, I was converting older V4 and Poser content.

    If you still get black renders even with CPU, then I'd file a bug report with Daz. They'll probably ask you to send the scene file.

  • marblemarble Posts: 7,500

    Lol, I don't think DAZ support would appreciate my subject matter (or perhaps they might). Anyhow, what you say about the CPU fall-back makes sense. That's how I knew the original card was faulty. Also, what you say about building a new scene appears to be my experience too, as I mentioned above (come to think of it, I'm using a converted M4 skin on G2M). I hope there is a bug fix in the next release as it seems to be something that has happened to others.

  • RuphussRuphuss Posts: 2,631
    edited June 2016

    rendered image series with interactive mode

    renders as long theres ram left then renders black

    image rendering with interactive is broken due to ram management

    this is not the case with photoreal

    Post edited by Ruphuss on
  • marblemarble Posts: 7,500

    Yeah - I've tried some more today. Very hit and miss with interactive. I have had to reboot a few times to get the same scene to render - and I agree that it seems like memory management. Something is broken.

  • ToborTobor Posts: 2,300

    Is there a reason you're rendering in Interactive? Control of shadows or AO?

    Just as a matter of comment, Interactive has some limits on number of lights, textures, and other scene elements. I wouldn't think the render would just stop if you exceeded these limits, but you never know.

  • marblemarble Posts: 7,500
    edited June 2016

    I'm trying to create an image series for an animation. Interactive seems to be much quicker than Photoreal. The scenes are pretty minimal in terms of lights and props, etc.  

    Post edited by marble on
  • RuphussRuphuss Posts: 2,631
    Tobor said:

    Is there a reason you're rendering in Interactive? Control of shadows or AO?

    Just as a matter of comment, Interactive has some limits on number of lights, textures, and other scene elements. I wouldn't think the render would just stop if you exceeded these limits, but you never know.

    for testrenders

    they are quick

    and it always worked before so must be a 4.9 thing

  • Windows 10. 64-bit   I had been using 4.9.2.70 with an EVGA 1060 -  Interactive worked for several weeks as I futzed with some settings off and on.  Then I tried a real render.  Wasn't satisfied with speed but when I went back to interactive got this...  

    016-18-06 09:18:56.905 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: failed to estimate required local memory per kernel launch

     

    which was quickly followed by 

     

    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.3   IRT    rend error: failed to load: device kernel image is invalid
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.3   IRT    rend error: Kernel linking failed
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : A device failed during rendering
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Cannot render: device failed.
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Failed on first frame. Dropping failing devices and re-rendering
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : All devices disabled.
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : There are no devices that can be used with IRT (Compute Capability 2.0 required)
    2016-55-06 08:55:15.539 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : -------------------------------------------------

     

    Which is not what I had expected.  As the CPU has no chance whatsoever of doing this (it is a not blindingly fast old quad-core) I am somewhat DIW .   Not sure what happened with this driver.  It seems to have worked until I tried to switch it or that could be coincidence..  I have no trouble with other programs which all do rely on the card, though not in the same way.   Apparently have to go back to 3delight.  

    Wish they'd come up with something that used the cudas to just go really damned fast with 3delight quality (the OpenGL isn't useful as it stands) and the heck with photoreal.  

    One does hope that they get a handle on this quickly.  

  • I should note that the card DOES work just fine in opengl.   Opengl just gives problematical results in respect to lighting and the like.  

     

  • Ralf1958Ralf1958 Posts: 688

    Since the last two Updates to 4.9 Public Build Beta, I cannot render anything anymore. The Viewport is not reacting and it keeps saying "Preparing scene". If I start a normal render, it only renders black. My 4.8 installation still works fine and renders as usual. Tryed to deinstall and reinstall a few times but no luck. Any suggestions?

  • mjc1016mjc1016 Posts: 15,001
    old-dog said:

    Windows 10. 64-bit   I had been using 4.9.2.70 with an EVGA 1060 -  Interactive worked for several weeks as I futzed with some settings off and on.  Then I tried a real render.  Wasn't satisfied with speed but when I went back to interactive got this...  

    016-18-06 09:18:56.905 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: failed to estimate required local memory per kernel launch

     

    which was quickly followed by 

     

    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.3   IRT    rend error: failed to load: device kernel image is invalid
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.3   IRT    rend error: Kernel linking failed
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : A device failed during rendering
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Cannot render: device failed.
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER):   1.0   IRT    rend error: Failed on first frame. Dropping failing devices and re-rendering
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : All devices disabled.
    2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER):   1.0   IRT    rend warn : There are no devices that can be used with IRT (Compute Capability 2.0 required)
    2016-55-06 08:55:15.539 Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : -------------------------------------------------

     

    Which is not what I had expected.  As the CPU has no chance whatsoever of doing this (it is a not blindingly fast old quad-core) I am somewhat DIW .   Not sure what happened with this driver.  It seems to have worked until I tried to switch it or that could be coincidence..  I have no trouble with other programs which all do rely on the card, though not in the same way.   Apparently have to go back to 3delight.  

    Wish they'd come up with something that used the cudas to just go really damned fast with 3delight quality (the OpenGL isn't useful as it stands) and the heck with photoreal.  

    One does hope that they get a handle on this quickly.  

    The build you are using does not support the 10x0 series cards...

     

    Ralf1958 said:

    Since the last two Updates to 4.9 Public Build Beta, I cannot render anything anymore. The Viewport is not reacting and it keeps saying "Preparing scene". If I start a normal render, it only renders black. My 4.8 installation still works fine and renders as usual. Tryed to deinstall and reinstall a few times but no luck. Any suggestions?

    System specs, please...

  • Wound up getting it back.  Had the brainstorm that if it had worked with scenes that had been done initially with the combo of CPU and GPU that conceivably it was relying on the CPU to do some of the meta-information loading the scene into memory and working out how big it was.    

    Went and restarted with both devices present and all seems to be working as-was.  I had thought the slow old 4-core CPU I have was slowing it down, but it was doing just fine using interactive, so I'll just leave it ticked on and leave it for my Christmas Prezzy to deal with any speed issues. 

    So far that's my story and I'm sticking with it ...  unless it turns out to be POM   (phase-of-moon)  dependent  :-) 

    I do wish that 3Delight had the ability to use its more rudimentary but for my purposes satisfactory methods to get fast and acceptable renders out.  Photorealism is overrated when you want flat-out speed to do any sort of animation.    Primitive but FAST.   Lord give me patience, but I want it RIGHT NOW!!! :-) 

    Thanks... 

  • Ralf1958Ralf1958 Posts: 688
    edited November 2016

    Since the last two Updates to 4.9 Public Build Beta, I cannot render anything anymore. The Viewport is not reacting and it keeps saying "Preparing scene". If I start a normal render, it only renders black. My 4.8 installation still works fine and renders as usual. Tryed to deinstall and reinstall a few times but no luck. Any suggestions?

    mjc1016 said:

    System specs, please...

    System Specs:

    Windows 7 Home Premium
    i7-4771 CPU 3,50 GHz
    16 GB RAM
    Grafic nVidia GeForce GTX 970

    DAZ3D 4.9.3.128 Pro Edition (64-bit) Public Build

    Post edited by Ralf1958 on
  • BeeMKayBeeMKay Posts: 7,019

    Have you installed the DS Essentials for the Beta?

  • BeeMKay said:

    Have you installed the DS Essentials for the Beta?

    As long as the content directories match you should not need to install content separately for each version.

  • fixmypcmikefixmypcmike Posts: 19,601

    What's the driver version for your GPU?  The public beta requires 368 or higher.

  • Ralf1958Ralf1958 Posts: 688

    Yes, I have everything installed. Here the driver version:

    TreiberCPU.PNG
    322 x 318 - 10K
  • mjc1016mjc1016 Posts: 15,001

    Nvidia driver version...

  • fixmypcmikefixmypcmike Posts: 19,601

    The video card driver -- Control Panel > NVIDIA Control Panel > click "System Information" in the lower left.

  • Ralf1958Ralf1958 Posts: 688

    The video card driver -- Control Panel > NVIDIA Control Panel > click "System Information" in the lower left.

    It says 353.30

  • Ralf1958Ralf1958 Posts: 688

    Just installed 375.70 it works now! Thank you!

Sign In or Register to comment.