Tweet
Hi, so this is kind of an unorthodox and layman-like wish perhaps, but I think all of us have at some point wanted to be able to do this, as it would make our lives a bit easier.
Would it be possible to discuss whether such a functionality would at all be possible?
There are multiple scenarios in my particular company where this would be useful. To name a few:
1. A render for some reason does not finish (power outage, crash, network connectivity lost), usually because something unexpected happens.
2. We render on both farm machines and workstations and sometimes when we come in to work in the morning someone may realize a render is going on their machine and so they cancel it because they need their machine.
What do you guys think?
Is it something that is practically out of the question or would it be possible to somehow find a long-term solution?
The idea came up when we were talking about whether you could jump off a DR render without ruining/halting the total DR render (we run the DR slave as an app which can be launched on any workstation on-demand and which would then join an ongoing DR render). The main objective would be to not have to restart the render from scratch, but instead keep going from where it was when it stopped.
Perhaps a file would get stored on the network drive (meaning; in the project), which would store all information necessary to pick the rendering up if it wasn't completed. If the render was completed, this file would get discarded after rendering. For us, the best place for the location of such a file would be inside the render folder, next to the output (e.g. EXR files).
Would it be possible to discuss whether such a functionality would at all be possible?
There are multiple scenarios in my particular company where this would be useful. To name a few:
1. A render for some reason does not finish (power outage, crash, network connectivity lost), usually because something unexpected happens.
2. We render on both farm machines and workstations and sometimes when we come in to work in the morning someone may realize a render is going on their machine and so they cancel it because they need their machine.
What do you guys think?
Is it something that is practically out of the question or would it be possible to somehow find a long-term solution?
The idea came up when we were talking about whether you could jump off a DR render without ruining/halting the total DR render (we run the DR slave as an app which can be launched on any workstation on-demand and which would then join an ongoing DR render). The main objective would be to not have to restart the render from scratch, but instead keep going from where it was when it stopped.
Perhaps a file would get stored on the network drive (meaning; in the project), which would store all information necessary to pick the rendering up if it wasn't completed. If the render was completed, this file would get discarded after rendering. For us, the best place for the location of such a file would be inside the render folder, next to the output (e.g. EXR files).
Comment