hi there, i still got some problems in the monitor and launcher:
launcher: actually there appear 3 slaves, but i just want 1. can´t delete the 2, created by deadline. take a look at this screenshot:
monitor: it´s not possible to sort jobs by submitting date. clicking on the column has no effect.
monitor: when i change the frame-range from - lets say - 100 to 10, deadline ignores the already rendered frames in the last task. the whole task seems to be re-submitted?
The menu items for removing the slave instances will be added again in beta 20. For now, you can delete them from the slave list in the Monitor while in super user mode. Just right-click on the slave, and select Remote Control -> Remove Slave Instance. Just note that the slave has to appear offline in the Monitor for this option to be available.
I can’t reproduce the sort order issue. What’s your time zone setting on the machine set to? We convert UTC times from the database to the machine’s local time. I wouldn’t expect there to be an issue, but maybe that has something to do with it…
Tasks are considered individual units of work. There currently is a way for Deadline to be aware of which frames have been rendered and which haven’t been for a chunked task. So if you are splitting one task into many, the new tasks are requeued. Now, if you are using a renderer that supports skipping existing frames, that can be used as a workaround.
Thanks! It actually looks like it’s the format of the date/time that is messing things up. I changed my regional formats to German and I can now reproduce the problem. We’ll look at fixing this for the next beta.
since beta 19 the monitor doesn´t open the preview when selecting: TASKS/VIEW OUTPUT/VIEW IMAGE. (nothing happens) previewsly we used beta 17, this worked fine.
Reproduced and fixed! The fix will be included in beta 20.
I can’t seem to reproduce this, and I’ve had the Monitor and Slave running together for over an hour on our OSX 10.6.8 machine. I’ll leave it running as long as I can to see if it eventually crashes.
The crash log doesn’t point to anything obvious. It’s also really weird that it only happens if the Monitor is also running. Does the slave ever crash if you just leave it running by itself?
