Server Interruption Question - AccuRender nXt2024-03-29T09:23:56Zhttps://accurender.ning.com/forum/topics/server-interruption-question?commentId=6293855%3AComment%3A129214&x=1&feed=yes&xn_auth=noOk, well we only run Path T o…tag:accurender.ning.com,2017-10-27:6293855:Comment:1292142017-10-27T16:52:00.804ZAndrew Unohttps://accurender.ning.com/profile/AndrewUno
<p>Ok, well we only run Path T or Hybrid so that's a plus in a sense. I'll keep that in mind though about the restarts.</p>
<p>Ok, well we only run Path T or Hybrid so that's a plus in a sense. I'll keep that in mind though about the restarts.</p> All of the above are possible…tag:accurender.ning.com,2017-10-27:6293855:Comment:1292112017-10-27T16:14:09.398ZRoy Hirshkowitzhttps://accurender.ning.com/profile/RoyHirshkowitz
<p>All of the above are possible, with one exception-- a task that had begun will never resume-- it will need to restart. There may be some valid output from the run, there may be some tasks remaining in the job queue which will get picked up, or everything could be toast and the whole job require a restart. You're more likely to get something valid with the Path T, or Hybrid engines since you can always average together any results. Not true when you're using the Standard engine since it…</p>
<p>All of the above are possible, with one exception-- a task that had begun will never resume-- it will need to restart. There may be some valid output from the run, there may be some tasks remaining in the job queue which will get picked up, or everything could be toast and the whole job require a restart. You're more likely to get something valid with the Path T, or Hybrid engines since you can always average together any results. Not true when you're using the Standard engine since it renders strips. </p>
<p></p>