Renders ground to snail pace [Solved]

AbnerKAbnerK Posts: 718

Hi,

for some reason, my renders have gone so slow it's just not funny. "IRAY   rend progr: 0.03% of image converged
2018-09-13 11:07:05.400 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00541 iterations after 39921.883s." That's over 11 hours for 0.03% it's a scene with a single G8M, Morning Star Wings, Curly hair, Moon bow and an arrow. pixel size is 2500sq. No hdri but using dome set to midnight in England, December I've got spot lights pumped up to 1000% and  and set to large circles. Every surface has a light hitting it to some intensity. What is going on?

I alwasy get this error too that I've always just ignored. "Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance."

Thanks. 

Post edited by AbnerK on

Comments

  • PaintboxPaintbox Posts: 1,633
    edited September 2018

    Do all scenes have this problem? Even if you just render a simple base figure with standard settings?

    Post edited by Paintbox on
  • AbnerKAbnerK Posts: 718
    Paintbox said:

    Do all scenes have this problem? Even if you just render a simple base figure with standard settings?

    Thanks for the reply. I don't know, I haven't tried that. I will but I don't really want to cancel this render after investing so many hours in it. It's now showing 3%, I paused it and turned it to Scene Only, so it seems to be going a bit quicker. It doesn't look like it's only 3% done but I'm still not ready to end it in case I've done nothing wrong and that's just how long it's going to take. I'd really like to get on and do another scene. 

  • AbnerKAbnerK Posts: 718

    Oh by the way, I did lots of test renders that went quickly, I have tweaked the settings but nothing that should have slowed it down. I turned off noise filtering, increased the lighting % and added another lightm change the exposure value to compensate, I changed the colour of the wings and changed the camera angle but it's the same pose just from a different angle. The render looks really good for 3%, more like 60%, and it's not as noisy as the previous renders at the 'half done stage'. I'd canceled the previous couple at 97% because I didn't think they were going to get any better and still looked noisy in places which is why I added another light and turned off noise filter, actually, I turned that off because I read it did nothing but cause problems. 

    What is this error message. Nobody answered it on another thread? "Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : Expecting restart after abort. Frequent abort and resume in batch mode can severely reduce performance."

    Thanks

  • KitsumoKitsumo Posts: 1,216
    edited September 2018
    That percent complete measurement isn't really accurate. It's just the program's best guess at how close the image is to being finished. It can vary depending on what your settings are for max samples, max time & quality among others. The important thing is how does it look to you and are you seeing any improvement in a reasonable time?

    Are you using GPU rendering?
    Post edited by Kitsumo on
  • AbnerKAbnerK Posts: 718
    Kitsumo said:
    That percent complete measurement isn't really accurate. It's just the program's best guess at how close the image is to being finished. It can vary depending on what your settings are for max samples, max time & quality among others. The important thing is how does it look to you and are you seeing any improvement in a reasonable time?
    Are you using GPU rendering?

    yeah, I'm coming to understand that. I'm on a Mac Book Pro mid 2009 so it's old I've got 8Gb ram and i2. I've done much bigger renders that didn't seem to take that much longer. It's look great for 4% though. It's definitely speeded up in terms of numbers since I turned off the dome. I shouldn't even be using it since it's black anway. I use Photoshop too so what's the point? Thanks for the reply

  • FalcoFalco Posts: 241
    Kitsumo said:
    That percent complete measurement isn't really accurate. It's just the program's best guess at how close the image is to being finished. It can vary depending on what your settings are for max samples, max time & quality among others. The important thing is how does it look to you and are you seeing any improvement in a reasonable time?
    Are you using GPU rendering?

    yeah, I'm coming to understand that. I'm on a Mac Book Pro mid 2009 so it's old I've got 8Gb ram and i2. I've done much bigger renders that didn't seem to take that much longer. It's look great for 4% though. It's definitely speeded up in terms of numbers since I turned off the dome. I shouldn't even be using it since it's black anway. I use Photoshop too so what's the point? Thanks for the reply

    Be aware if the graphics card runs out of memory, it will cause the render to fall back to CPU only (which is like 20 times slower) for the rest of the daz session. You will need to restart daz to enable the gpu again.  What I usually do is have run GPU-Z, and watch the GPU load to make sure that GPU is engaged.  If I see it get disabled I have to restart Daz to enable it again.  So for example if you have a large scene that uses 6GB of GPU memory, and your GPU is only 4GB, you will never be able to use the GPU to render and it will fall back to CPU only.  

  • AbnerKAbnerK Posts: 718
    edited September 2018

     

    Falco said:

    Be aware if the graphics card runs out of memory, it will cause the render to fall back to CPU only (which is like 20 times slower) for the rest of the daz session. You will need to restart daz to enable the gpu again.  What I usually do is have run GPU-Z, and watch the GPU load to make sure that GPU is engaged.  If I see it get disabled I have to restart Daz to enable it again.  So for example if you have a large scene that uses 6GB of GPU memory, and your GPU is only 4GB, you will never be able to use the GPU to render and it will fall back to CPU only.  

     

    my GPU is 

     

     Chipset Model:    NVIDIA GeForce 9400M

      Type:    GPU

      Bus:    PCI

      VRAM (Total):    256 MB

      Vendor:    NVIDIA (0x10de)

      Device ID:    0x0863

      Revision ID:    0x00b1

      ROM Revision:    3427

      Displays:

    Color LCD:

      Display Type:    LCD

      Resolution:    1280 x 800

      Pixel Depth:    32-Bit Color (ARGB8888)

      Main Display:    Yes

      Mirror:    Off

      Online:    Yes

      Built-In:    Yes

    Other than 250Mb VRAM I've got no idea what that means in terms of my renders. But what you said makes me think I had run out of memory because I hadn't restarted Daz Studio for a few days. 

    I think in the end it was a combination of not having restarted Daz for a few renders and having the white wings. A test render with a single figure with long hair worked great and didn't take too long. 

     

    Thanks

    Post edited by AbnerK on
Sign In or Register to comment.