Loading...
> >

Animation defaulting to CPU after 1 frame

Leonides02Leonides02 Posts: 1,379
in The Commons

Hello All - 

I have 4 frames which I'm trying to render (I'm faking a batch render). The 1st frame renders with the GPU as usual, but the 2nd frame goes to CPU. 

I am using Ultrascatter for the scene, but I don't see why that would matter. 

Has anyone else encountering this? Any help would be appreciated!

Comments

  • IvyIvy Posts: 7,165

    Hmm  It sounds like maybe you used all your GPU memory in the first frame rendered, which would push the remaining work load onto the CPU so it could manage the batch file being rendered . just sounds like you ran out of GPU memory, you can check your log files to see how much your GPU is using for rendering it should give you some ideas anyway.

    My advice if your only doing 4 frames why not render one frame at a time & save them as .png image series instead. same end results with better quality images. 

     

  • Leonides02Leonides02 Posts: 1,379
    edited August 2018

    Thank you for your reply!

    My understanding (which may be flawed) is the entire scene is loaded onto the GPU with the first frame. The only thing that's changing is the camera angle.

    The reason I'm only doing 4 frames is because I'm trying to trick DAZ into doing a batch render of 4 different images. That way, I can leave it running over night. The images take 3 hours to render, so I can get all 3 done in one night. :)

    Post edited by Leonides02 on
  • TooncesToonces Posts: 919

    There are other threads about this issue with no clear solution (to my knowledge).

    In the past, I avoided it by disabling Optix...but nowadays I leave optix enabled and simply try not to push the memory limits of my cards when doing an animation (the closer to memory limit, the more frequently it seems to occur).

  • IvyIvy Posts: 7,165

    I would check the log file , You properly already know But you can find it when you open daz studio click help> troubleshooting> view log file

    It may give you some idea  why its dumping to cpu or at least tell you how much gpu is being used during the cycle and at what cycle the dump accrues . it was always my belief  that it wouldn't matter if your doing batch or RIB or single image. if your GPU memory usage is greater than your cards output then its going to dump to CPU in any case,  But If you believe your well with in the cards gpu range,  then I would check the to see if there is a conflict or something that maybe causing it it may show up in the log file.

     

  • BeeMKayBeeMKay Posts: 7,019

    They've cleared up some of the issues in the current version of DAZ Studio 4.11 BETA. If you have already "purchaed" the Beta version from the store, you could give that a try.

  • Leonides02Leonides02 Posts: 1,379

    Thank you, everyone. Turning off Optix seems to work.

    Weird and unfortunate. 

    Maybe I'll try the Beta. I understand it also has the cool A.I. Denoiser.

  • fastbike1fastbike1 Posts: 4,081

    If you're using Instancing, you should also make sure to have Render Settings>Optimization>Instancing Optimization set to Memeory. The default is Speed.

  • Leonides02Leonides02 Posts: 1,379

    Not to necro, but this is still happening with the Beta. 

    Has anyone found a solution w/o turning of Optix?

Sign In or Register to comment.