Search

1. Re: Employer's feelings about external plugins

   

   Reply by RyanB · Dec 2010 · Home› General Discussion

   If your game is published by a big publisher that has a history of fighting against free software, you may not be allowed to use ANY free software, including plugins and scripts, to make the game. The terms of the contract will specifically say what can and can't be used. Installing software at work is generally a bad idea…

2. Employer's feelings about external plugins

   

   Topic by Maxim · Dec 2010 · Home› General Discussion

   Hey, I was wondering how to employers usually feel about external plugins and 3rd party scripts. For example I need to retopologize a model. Would they look down upon it (extra cost of plugin) if I were to use something like topogun? Keep in mind this is just an example.

3. Re: Employer's feelings about external plugins

   

   Reply by Mark Dygert · Dec 2010 · Home› General Discussion

   Well... even free plug-ins can cause problems. Do other people need the plug-in to open the files you've worked on? Does the plug in effect other tools or scripts. In general its a good idea to run it past someone higher up on the food chain than yourself, if nothing more than to make sure the blame doesn't fall on you.

4. Re: Employer's feelings about external plugins

   

   Reply by Eric Chadwick · Dec 2010 · Home› General Discussion

   Check with your technical artist, if you have one. Or whomever oversees changes/fixes to the artist pipeline. Sometimes a new plugin or script will cause unintended problems, because you work in a team environment, not just a lone dude. Others might need it in order to open/edit your files, you might need a site license,…