CTD at the start of render- can't tell if the problem is DAZ or my Graphics card.

ChallyII

Ever since I updated my DAZ installation from the install manager, I've been having a problem with certain scenes initialising the render and then DAZ simply blinking out of existance. I've been running 1.2 (64bit) ever since I bought a new graphics card and I've had no problems so far, beyond the occasional crash which usually comes with an error message.

On looking at the log file in troubeshooting, it tells me that the CUDA core failed to allocate memory:

 

2020-02-23 18:32:38.699 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(340): Iray [ERROR] - POST:RENDER ::   1.0   POST   rend error: A CUDA error occurred: out of memory
2020-02-23 18:32:38.699 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(340): Iray [WARNING] - POST:RENDER ::   1.0   POST   rend warn : Failed to allocate device memory, falling back to CPU

 

 

Now, with my old card when I rendered without the CPU checked and the scene was too big for my card to handle, I'd just get a black screen, not a complete crash. And the scenes themselves aren't that big. Looking at the log window for the render engine, the most recent one to crash was only about 139 MiB in geometry data- that was the final message before the thing crashed. I re-loaded an old scene I'd successfuly rendered and saved, with about five figures, costumes, props and scenery: This had over 550 MiB in geometry data. It initialised the render without issues. 

 

I'm baffled as to what is causing the issue, but at the moment I've just started a new project and although some of my renders have worked fine, others using the same characters and scenes, stubbornly refuse to work, and I've definitely ruled out that the scenes are too large. I'm used to being able to cheerfully render four or five fully kitted figures and a scene, and at the moment some of the scenes that are crashing only have two. I'm desperately hoping that the graphics card isn't to blame: It's a GTX 1660 ti, and it wasn't cheap- I've only had it for about eight months so it can't have worn out already. Is it a bug in the newest version of Studio 1.2? I'm wondering if anyone else has run into a similar issue, and whether there many be a solution.