GPU Renders 1st Animation Frame Only -- the Rest to the CPU?

RenderNovice

So I've read here of in-progress renders "falling back" to the CPU after commencing successfully on the GPU -- as an issue with the 4.12 release.  The issue I describe here may or many not fall under this category, so I'm hunting for answers, for any who may have insight and/or a solution.

I have a scene that falls well within my GTX 1080's (Driver ver. 442.19) memory limits -- rendering a low-grain image in less than 30 minutes.  That's for one frame.  When I tell Daz 4.12.0.86 to render an image series for an animation, however, it renders the first frame on the GPU only:  all subsequent frames are pushed to the CPU.  This makes creating an animation impractical.  (Days spent manually rendering one frame at a time simply to keep rendering on the GPU?)

My scene optimization skills to keep renders off the CPU may be a bit limited: to date, those skills include keeping the scene simple, bright -- but with a minimum number of light sources -- deleting all elements that do not appear within the frame.

However, exceeding my graphics card capabilty doesn't appear to be the problem here -- else, how could I render the first frame in any given render attempt on the GPU at all?

Any suggestions on how to solve or work around this would be much appreciated.  If its a 4.12 "fall-back" related issue, I'd say Daz just ceased to be a practical piece of animation software . . .  I never had this problem previously. 

Thanks!  

 

Chohole

https://www.daz3d.com/forums/discussion/comment/5274781/#Comment_5274781

RenderNovice

Awesome info, Chohole -- the very first item in your link for release 4.12.1.55 describes the fix.  The post is dated 16 days ago, I'm running 4.12.0.86, and it says "no updates found" when I click "check for  updates."  I presume, then, that I'm dead in the water until 4.12.1.55 is released?  That there is no work-around?  Does anyone have any sense when this fix will be released?

Richard Haseltine

DazNovice said:

Awesome info, Chohole -- the very first item in your link for release 4.12.1.55 describes the fix.  The post is dated 16 days ago, I'm running 4.12.0.86, and it says "no updates found" when I click "check for  updates."  I presume, then, that I'm dead in the water until 4.12.1.55 is released?  That there is no work-around?  Does anyone have any sense when this fix will be released?

That thread is about the current Public Build (beta), which is a separate version from the release build. You can install both ad use whichever you like at any time. https://www.daz3d.com/daz-studio-beta

RenderNovice

That's why I changed my online name to "DazNovice" -- I had no idea.  A public build, then, is out as a 'non-official' release -- to bring it to maturity as users run it on a trial basis?  I assume, Richard, that the animation fix under discussion here eventually finds its way into the 'Release' version?  Hopefully?

Richard Haseltine

DazNovice said:

That's why I changed my online name to "DazNovice" -- I had no idea.  A public build, then, is out as a 'non-official' release -- to bring it to maturity as users run it on a trial basis?  I assume, Richard, that the animation fix under discussion here eventually finds its way into the 'Release' version?  Hopefully?

At some point the current Public Build, or a later build, will be promoted to a General Release - which will be the same code, just installing to  different folder/using a differnt plist for its settings etc.