IF I were a freelancer, I'd sort out my I/O first and foremost. Basically have the ability to take in commonly exported formats like .bgeo/partio/alembic/.skp plus the occasional 2D formats for camera and pCloud stuff and have it so that these span a few versions back. I feel like once this is established, you're free to use the best tool for the job or leverage the resources already in place at the facility. The real value of a freelancer comes from being able to integrate seamlessly into a pipeline while providing value via your expertise. The ability to break off your work so others can pick it up as well as take on where others have left off while still using the tools you're most adept with is incredibly useful.
-Lu On Mon, Jan 14, 2013 at 7:38 PM, Andy Moorer <andymoo...@gmail.com> wrote: > Hi all. I'm interested in what people consider as the essentials for a > small studio Softimage pipeline, in terms of essential tools, scripts and > customization. I have my own ideas and opinions but want to get a sanity > check in case I'm missing some cool workflow or toolset, and just out of > interest. > > I'd also be interested in hearing what people have in their personal > toolkits. For instance wherever I bring along a personal workgroup which > contains a plethora of ICE nodes, a small script library of example code > and esoteric tools, a set of useful addons by others, and a custom menu > with a set of more personal tools, mostly little time savers, things like > general purpose models and lighting rigs, etc. > > A lot of these things are little but I'd hate to be without 'em. For > instance a simple menu command which removes screen widgets and makes the > BG dark grey is so trivial but I'd really miss it. Same goes for Ciaran's > signed distance field emitter, I love that thing... >
