Timeline for How can I pause a render in progress and then resume it at a later time?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2013 at 15:08 | comment | added | gandalf3 | A python script to do stuff like this would be awesome. (I think i'm going to try and learn python now) but to able to define different numbers of samples for different parts of the render... :D | |
| Jun 7, 2013 at 21:00 | history | edited | Utas | CC BY-SA 3.0 | deleted 1 characters in body |
| S Jun 3, 2013 at 13:55 | history | edited | CharlesL | CC BY-SA 3.0 | Fixed grammar. |
| S Jun 3, 2013 at 13:55 | history | suggested | Daniel | CC BY-SA 3.0 | Fixed grammar. |
| Jun 3, 2013 at 13:54 | review | Suggested edits | |||
| Jun 3, 2013 at 13:56 | |||||
| Jun 3, 2013 at 10:54 | comment | added | jesterKing | You certainly can break up a render into parts this way (on Renderfarm.fi we use this to split workload between nodes), but it is quite a labour intensive way to do things if you don't have a good automation behind it (Renderfarm.fi has a Tomcat7 servlet running doing all this delegation and stitching). You can add that for Cycles you could render in batches of ie. 10 or 50 samples, and then average the results all into one (which I implemented on Renderfarm.fi as well ;) Just take care that each batch is rendered with a different seeds | |
| Jun 3, 2013 at 8:49 | history | edited | Utas | CC BY-SA 3.0 | deleted 1 characters in body |
| Jun 3, 2013 at 6:28 | history | answered | Utas | CC BY-SA 3.0 |