PDA

View Full Version : Distributing tools to outside companies


Hobbs
04-20-2012, 03:59 PM
I'm just wondering what type of setups you guys use to distribute tools to outside companies or clients. Right now we are having issues with Windows 7 and permission distributing through an .mzp. And just general issues with making sure people are up to date, etc.

Just curious to what else is out there, or what else is being done.

Thanks

denisT
04-21-2012, 01:22 AM
first of all i want to say that is very important subject. i wanted to start a thread myself about this matter. and i really want to hear big guns.

the phone is not right device for long posts, so tomorrow i will try to give my vision of this issue.

denisT
04-21-2012, 01:22 AM
first of all i want to say that is a very important subject. i wanted to start a thread myself about this matter. and i really want to hear big guns.

the phone is not right device for long posts, so tomorrow i will try to give my vision of this issue.

muhammadfredo
04-21-2012, 09:04 AM
in my studio i use batch file+maxscript+inifile, before that I categorize my script to macro,library,plugin and tools
I have two inifile, one in server and one in every local pc. every 3dsmax launch my update script will compare local inifile and server inifile (version).if server>local then maxscript will launch batch file and update all script in every pc in my studio.
and in outside studio case maybe you can use dropbox as server script. i`ve done this for one year production and no trouble at all

martinez
04-21-2012, 09:57 AM
I do a few things to help.

1. If you use the UserScript, UserMacro, UserIcon, UserStartupScripts, and Temp folder you don't run into permission issues.
2. If you put on the tool installer interface to run Max as an Administrator you won't have permission issues.

Here is how I work:

In source control make a userScript, userMacro, userStartup, and userIcon folder. Have people run a set up script that simply remaps the user folders to source control. When you check in updates they will be propagated as soon as everyone gets latest. No need for mzp files, exe installers, or permission issues.

If an outside studio is getting a copy of the source control it will be just as easy to set up.

jonadb
04-21-2012, 11:39 AM
A while ago Pier and I started this project http://forums.cgsociety.org/showthread.php?t=982471

That would solve most of the issues. As a company you could setup a repository and clients could install the latest versions, update notifications included.

But it's on hold now for a while since Pier is reworking Outliner and I'm tied up doing to many projects.

It's on github, so if anyone has some sparetime to finish it please do so :)

Pjanssen
04-21-2012, 12:42 PM
Yes this is/was an interesting project indeed. It had a bit of a revamp a few months ago when I teamed up with another mate to write a generic (cross-platform) version of it in python. However, we both started our thesis projects, so it slowed down considerably since then..

CGTalk Moderation
04-21-2012, 12:42 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.