Okay, this is what happened. I after installing (3_0_6_16a) I did immediately renders the frame 0-342 With 10 s / pix. All renderings were made and saved properly. That was for testing purposes.Veneris wrote:Thanks, I've installed (3_0_6_16a) and now the error no longer appears under the same conditions of the scene, the plugin have rendered and saved all the frames correctly. I hope to finish the animation without the error appears again.face_off wrote:The following debug build of the plugin adds a message in the Messages area at the bottom of the System tab if the render image fails to save. It will hopefully give us a clue as to why it's not saving. https://render.otoy.com/customerdownloa ... _Win64.exe
Paul
I like the way you are attentive, regards.
Renderings I have to do is 500 s / pix, render the frame 0 to 326 from 342. I got up there because I had me go. I turn off my PC and I left, everything was right.
When I returned, I render the rest of the frame 327 to 342. And the error appeared again. > http://imgbox.com/mVM5qJEe < and > http://imgbox.com/HERHy3o7 <
Later appeared a controller error. > http://imgbox.com/oScvheQw <
Translation: The display driver stopped working and recovered.
The display driver NVIDIA Windows Kernel Mode Driver, Version 364.51 stopped responding and recovered correctly.
I tried again > http://imgbox.com/tCqKz48u <
When I tried again I changed the route where the renderings would be saved, so that the folder was not any files. The error appeared again, the plugin only rendering the same frame again and again. And "Name Prefix" is changed like everything was right. For example: Render_010, Render_011, Render_012, Render_013, Render_014, Render_015 ...
But it was always the same frame Render_010. I can not render the other missing frames to 342.
UPDATE: I restart my PC and I could render without problems. I do not know if the error appears again later in other scenes. We'll see...
