Loading...
> >

Can't render animations with 4.11 (or 4.12 beta)

mumia76mumia76 Posts: 146
edited August 2019 in Technical Help (nuts n bolts)

I have a huge issue with 4.11:

Rendering falls back on CPU only after rendering just 1 frame. It uses GPU as it should for frame 0, but every frame after goes cpu only.

So the first frame is rendered in like 40 seconds, then the second one takes 3x the time.

 

If I cancel the render then set start frame to frame 1 or 2 or anything, it again renders the first selected frame on GPU, then falls back on CPU rendering for every other frame.

This never happened with 4.10

How, why?

Post edited by mumia76 on

Comments

  • mumia76mumia76 Posts: 146

    It seems to me as if Daz Studio is trying to copy the textures into the VMEM again for frame 2 without first releasing frame 1. Why even copy it again? It is the same scene with the same textures. Changing instancing optimization to memory did nothing.

  • mumia76mumia76 Posts: 146

    I've tried going back to an earlier NVidia driver, didn't help.

    Tried disabling SLI, that didn't help either.

  • mumia76mumia76 Posts: 146

    Removing some assets from the scene makes it work.

    So the question remains, why is it able to render one frame with those assets included, but not more?

  • fastbike1fastbike1 Posts: 4,078

    Unless you close the render window between renders or frames, the Vram on the GPU is not released. You are running out of memory on the GPU and Iray falls back to the CPU as designed.

    Studio doesn't "know" it's the same scene.

  • mumia76mumia76 Posts: 146
    edited August 2019
    fastbike1 said:

    Unless you close the render window between renders or frames, the Vram on the GPU is not released. You are running out of memory on the GPU and Iray falls back to the CPU as designed.

    Studio doesn't "know" it's the same scene.

    There is no render window, when rendering animations. This is one render, not rendering 1 frame then rendering another manually. And BTW that works.

    And even if these were single renders when the render is completed the render window only shows a single image, not an interactive view needing assetts to have it displayed. You're confusing a viewport with the render window.

    Post edited by mumia76 on
  • marblemarble Posts: 7,500
    mumia76 said:
    fastbike1 said:

    Unless you close the render window between renders or frames, the Vram on the GPU is not released. You are running out of memory on the GPU and Iray falls back to the CPU as designed.

    Studio doesn't "know" it's the same scene.

    There is no render window, when rendering animations. This is one render, not rendering 1 frame then rendering another manually. And BTW that works.

    And even if these were single renders when the render is completed the render window only shows a single image, not an interactive view needing assetts to have it displayed. You're confusing a viewport with the render window.

    Agreed. I need to some some animation renders soon so I hope you get an answer to this.

  • mumia76mumia76 Posts: 146

    I've done further tests and it is the strangest thing. I left it running for longer didn't cancel when it switched to cpu for the second frame, and here is what happens:

    It renders every odd frame on the gpu and every even frame on the CPU! This is lunacy.

  • spaspa Posts: 44

    Same problem here.

    Did you solve this issue?

     

    TIA

Sign In or Register to comment.