Hello,
I’m used to deadline 5.2 and the task refresh was really snappy and accurate. I only render on my machine (the client is also the slave), and I usually setup the refresh to 3 or 4 seconds. Now that I upgraded to Deadline 6.1, when clicking on a job, it takes 30 seconds to load the tasks (even if it’s just a one frame render), and with a quick refresh rate of a couple of seconds, I only get 2 or 3 updates of the tasks: once when it starts, once in the middle of the render, and once when it’s done rendering.
Is that the normal behavior?
Cheers.
Hi,
This is most definitely not correct. When you click on a job, the tasks should be loaded pretty much instantly! Can you share your monitor settings as per this screen-grab?
Also, could you confirm what OS and OS language/region you are using on your machine?
Mike
I’m using windows 7 professional SP1 (english language).
Here are my update settings, I only changed them to 2 seconds and enabled manual refresh to see if it would improve it.
Ah, by enabling the manual refresh, it won’t automatically refresh anymore and it will actively block you (you can see this in the console panel), if you try and refresh more than once every 10 seconds.
I would disable the manual refresh and then in the bottom right-hand corner of monitor (after a restart), you should see that the monitor “Last Update: X seconds” counts up to 2s. If this isn’t happening, you might need to just chill this setting out a bit and put it back to the default of 5 seconds.
Clicking on the tasks panel for a newly selected job, should update the tasks pretty much instantly. If not, can you open the “Console” panel in Deadline monitor (it’s just like the other panels in monitor) and copy and paste any error message it may be displaying?
Even with the manual refresh enabled, the window was updating every 2 seconds (according to the last update info at the bottom right). I removed it and saw no difference. But there is indeed plenty of things in the console:
2014-03-22 16:17:32: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
2014-03-22 16:17:32: Error occurred while updating task cache: Input string was not in a correct format. (System.FormatException)
2014-03-22 16:17:45: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Task Importer).
2014-03-22 16:17:46: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Slave Importer).
2014-03-22 16:17:46: Error occurred while updating slave cache: Input string was not in a correct format. (System.FormatException)
Ah, this looks like a little bug which is in v6.1 and is now fixed in v6.2 (beta), which is available if you would like to test? If so, please send an email to beta@thinkboxsoftware.com to sign the NDA and gain access.
Alternatively, there is a quick fix/workaround, which is to ensure the OS region “decimal symbol” of the “full-stop” symbol is used and not a “,” for example. Of course, this is not ideal as your keypad on your keyboard might not behave as you expect. However, this is all resolved in v6.2. See image below for how to change your “decimal symbol”. Ensure you restart before opening up monitor and testing again.
Sorry I should have said that I was using French formatting, even if my Windows is English. That did the trick, thanks a lot.
I was interested in testing the beta, especially because I use Redshift from time to time, but I thought I would be useless as I just use Deadline to render on my own machine for my indie movie, and I assumed you would get more interesting feedbacks from big companies with huge renderfarms.
I’ll consider it though, thanks for the great support (on a Saturday) 
