Hi,
As of beta 4, is Draft now re-included in the repository/client installers for Windows?
Thanks,
Mike
I’m pretty sure we still left it out.
We realize installing it on all of your slaves individually is kindof a pain, and we were wondering if it would be feasible for you guys to try installing it on a Network-accessible location (just in the Repo would work, even), and pointing the Draft Install Path in the plugin config to that location.
My initial tests showed that this should work fine, but I’m not sure if/how that would impact performance under load…
Cheers,
-Jon
this is how we did it and it works well…
it´s also much more convenient to update a version this way.
(we have nuke and c4d installed in the same way btw)
Timor
Is this a documented ‘feature’ ? if not, should it be?
It wasn’t something we had specifically planned for, just something Ryan thought of with the last release 
It’d be worth mentioning in the setup docs I would think.
Hi Jon,
Sure, I can install it on a network location to test. But I’m struggling to understand why you wouldn’t want to include it in the repository installer when you want to encourage users to start using it, perhaps with a limited ‘demo’ mode when no Draft license is present? If Draft is included effectively for free for anyone on active Deadline support contract, I would expect it to be included as part of the main installers? Now that Python is no longer in the repository installer, I would have thought the overall size increase would now be acceptable? I would have thought showing potential users of Draft what functionality it has for existing Deadline customers would be a major sell-in point for including it in the main Deadline package?
Maybe I’m missing something here?!
Thanks,
Mike
Hm. I do have Draft under C:\Program Files\Thinkbox\Deadline\bin\Draft. Not sure if it’s remained there since Beta 2, but I only discovered it after updating to Beta 4 and installing Draft separately under …\Thinkbox\Draft on each node.