alpha 5 feedback

[MikeOwen]

Some really strong features in v5.1 so far and I haven’t even sent you my latest plugin creation yet

1. Deadline build number #45029 is out of sync with the forum download files which are listed as #45030.
2. Maybe its me, but I installed alpha 5 over the top of alpha 4 and my respoitory settings seem to have been lost? ie: there is no python paths in the python settings, repository options section?
3. Now that CPython is included, shouldn’t this path automatically be added to the respoitory options? ie: “C:\Program Files\Thinkbox\Deadline\python\2.6.7\x64\lib”, etc… x64 vs. x32bit, both? or just one bit build?
4. “Submit Draft Job to Deadline”, click on the “Utilities” tab, then click on the “Creat Menu Item” button. Perhaps improve the error message returned?
5. monitor, “edit themes”. the GUI looks a bit strange when you open it. Like the “Current Theme” section needs a “GroupBox” around it or something. Maybe its just me?
6. Total GHz processing power in the top-right slave list is not correct any more when you start up multiple slaves on 1 machine. The value calculation should take this into account?
7. right-click on a slave, remote control. It would be nice to have an additional function to “Start ALL Slaves” on this physical machine. Command should also work for multiple selections.
8. Within SMTD, can we add sticky/default settings to all the new Draft settings?
9. When I “start new slave with specified name on selected machine”, if I type “mi ke” with quotes but with the space, the subsequent error message needs improving as it states…“The Slave name “” bla bla” which doesn’t help?
10. If I have 2 slaves running on 1 machine and set 1 slave to “restart upon current task completion” or “shutdown upon current task completion” what happens to the other slave if it is still rendering when this event occurs?
11. Can I run multiple slaves in NT service mode?
12. I would like to see some kind of option to control the naming convention of any slave instances, otherwise things are going to get confusing very quickly.
13. Would be nice to globally disable slave instances being started up by a “normal” or “power” user.
14. monitor - “modify job scheduling” - click on the 2nd radio button (one time only) and click on the “…” button. For me, the calender GUI elment is too small and looks screwed up. ie: can’t see “right” arrow to forward by 1 month.

Mike

[rrussell]

Thanks for the feedback!

1. Meh, it’s just alpha. We’ll make sure this is correct in the first beta though.

2. Hmm, we didn’t notice this when we upgraded our test setup here. Some repository options were changed for the new layout, but python settings wasn’t one of them…

3. It was actually supposed to be added under the hood, but the code that did that was still commented out in alpha 5. This will be fixed in beta 1. We didn’t want to add it to the repository options because the client can do a better job figuring out where the bundled python install is.

4. Thanks for pointing this out. We can add a better error message.

5. I see what you mean. I’ve logged this as a minor issue, but still targeted for 5.1.

6. Good point. Logged.

7. Another good point. Logged.

8. Yup. Logged.

9. Maybe it’s just me, but The Slave name ““mi ke”” contains invalid characters… seems to make sense. Not sure how we would improve it…

10. This is something that’s still on our todo list. We need to figure out how to handle this situation properly.

11. Should work fine.

12. Already logged (I think you brought this up before), but unlikely for 5.1 me thinks.

13. We agree. Logged.

14. Ack, that’s a bug! Logged.

Thanks again!

• Ryan

[im_thatoneguy]

We lost all of our Path Remapping on install but otherwise everything seemed to remain intact.

[rrussell]

Weird, because we didn’t touch that either. I wonder if maybe it’s just certain settings that are effected…

[MikeOwen]

cool. thanks for the notes Ryan.
Scrap #9, I can’t seem to replicate the issue any more.
Mike