I've gone ahead and test rendered a simple animation scene. Things seem promising at this point, however I encountered an issue that could be related to GPU options that messed up one of my animation renders. If I can reproduce all the errors I got, I will submit bug reports to t_3.Spectralis wrote:I'm really relieved there's been a pre-xmas update. It feels like a final release might arrive in the first quarter of new year. I've stuck with v1.2 as, so far, v2 hasn't been as reliable for animation. Has anyone testing the new release tried rendering animation and if so how has it been?
The scene consists of 200 frames of animation. It's very crude, I only spent about 5 minutes setting it up; very bad timing, no polish at all... it's not intended to impress by any stretch
I also added a bit a of camera movement to test the camera motion blur. The camera focus has been set to follow the bouncing green sphere (f-stop 1.5 ; focal length 65)This is my first test. I have both object and camera motion blur set to "on" in the OcDS Animations tab. I used both of my GPUs to render this, I toggled "use prioritization" on for one of them. I watched both the OcDS and DS viewports as the animation was rendering and both were updating as they were supposed to. As you can see, the motion blur is crazy strong... don't know yet if we can control it, but at least we know it's working.
My second test, this time without motion blur. I was curious to see what would happen if both GPUs are set to "use prioritization", so I toggled them all on. A curious thing happened; in the OcDS viewport it said 2 GPUs were used but the animation was rendering significantly slower as though only using one GPU. And even though both viewports were updating just fine while it was rendering, the rendered images showed something different; it seems objects had stopped updating after frame 44 while the camera kept going. Whether or not this is related to the change I made to the GPU configuration is unknown.
I tried again, but this time I unchecked one of the "use prioritization" boxes, other than that all settings remained the same. This time render speed almost doubled and objects updated properly in the renders. Again, I didn't do a frame-by-frame check, but I see no "craziness" here, at least nothing that I can see.
So far there's been no objects or camera "teleporting" randomly somewhere across the frames or disappearing while rendering - one of the issues with animation that I encountered in 2.12 4th pre-release and 1.2.
I'm going to do an animation test with a human figure and conforming items soon and report back.Dkron wrote:Now if only the plugin would update the geometry after rendering a frame in the animation tab, this would be the best version of the plugin.
it depends on how the graft was put together. if it works for one product it may still completely fail for another one. that's why it is that hard to get right. i can only say for sure, that i'm building the geometry right, but the mat linking is, well, random. my usual test case is bot geneses, and if you look at the masses of new and in-place geometries that are created, along with tons of materials, you'll probably get a taste what it means to resolve that mess programmatically...
