Progress is still going well, although I encountered a weird render-quirkiness problem this week.
I have my Daz library installed in two locations. On my NAS drive, and on the computer I use for posing. My render rigs pull their data from the NAS drive because it tends to load a bit slower, but the advantage is that I only have to maintain two libraries of 3D assets, regardless of how many render rigs I end up using.
But, for the scene I'm working on now, both the render rigs loaded the animations, but it seemed to lock down Daz completely. By lock down, I mean being completely unresponsive - and not in the way you might be familiar with when Windows notifies you a program is unresponsive and fades the window out while it waits for it to respond. It ran just fine, but I could not click anywhere.
My posing rig loaded the animations without problems, but with a notification saying I had to install the default assets.
This is normal Daz behaviour quirkiness, and it's been like that for years. It'll throw that window up, even if the default assets are installed. Click SKIP, and it's fine.
So, what I believe was the error on the render rigs is that Daz is waiting for me to click SKIP on that notification, but I can't see it anywhere, and enter/tab/alt didn't work.
I ended up writing a script that skips all error messages while loading, and voila. It worked. But the big minus is that I can't queue up animations anymore, so there will be downtime during rendering if an animation completes overnight, as I don't get up every two hours to check if an animation has completed and manually load a new one if it has. :)
So I consider this a temporary fix, and I hope moving on to the next scene after this one, things will go back to normal. Otherwise, I'll have to do something more drastic.
Anyway, 1,709 frames of animation and 82 story renders were completed this week.
And for a preview, I think this girl wants your attention.
Have a nice weekend. Stay safe out there.
// Drifty