Hi, I was wondering how important it is (for modellers) to be very proficient with whatever program is specified by a hiring company. If all you are doing is modelling and you produce great works with, for example, silo and zbrush, but you can use 3DS Max well (which is what the company specifies)is that a big problem?
I would have thought that all that would be required is importing your work to the specified app, which seems straightforward in most cases nowadays given most import and export the main file types.
Would it be very difficult in most cases to get hired if you model in a different program than that specified by the company?
Replies
As for importing and exporting. The main reason companies stick to certain programs is because of the set workflow already estrablished and the compatability... also because they're not gonna spend a shitload of money for every modeling program out there... one of the reasons I sadly see many companies around me still mainly using MAX... its just too expensive of a program... most companies would rather go for cheaper ones like XSI and Maya (I'm not saying they're not good, so lets not turn this into a software war).
The best way to learn a new 3D app is the get hired by a company and then have their artists help you out; show you all the tricks and workflow. You'll be up and running in no time.
Modeling is also pretty standard in terms of the tools required to do the job. Different packages may put their own twists and variations on a tool and call it something funky, but it's all the same in the end, and therefore can be learned very quickly by a new artist.
These days though, there really is no excuse for not being at least a little bit familiar with one of the major apps. With all the free demos out there, I'd be asking you why you hadn't tried one of them in an interview.
If I knew a company was using Max or Maya in their pipeline, I'd get familiar with them before applying there. Just makes sense, and shows a bit of commitment on your part.
Would it be very difficult in most cases to get hired if you model in a different program than that specified by the company?
[/ QUOTE ]
Most competent hiring managers understand that an application is a tool, and they are hiring an artist familiar with game tech. The tool is not 'irrelevent' but it is secondary to the skillset.
limiting an asset pipeline to one modeling application saves a conversion step, but this isn't the most important reason,
There are two very good reason not to promote different modeling apps within a single assets pipeline that have less to do with asset creation.
The biggest two I can think of are:
a) Troubleshooting drawing and lighting problems.
b) Tools creation.
A technical artist would need to be profiecient in two aoppliactions to spot tech problems. It's taken me a while to learn max that well...and i'm nowhere close to where I'd like to be with spoting and troubklshooting tech problems. Now to do that with 2 apps? that would be confusing, frustrating and a waste of time. Not to mention more of a headache. Trobleshooting geometry drawing issues is already enough of a headache :P
When a tools programmer is writing scripts and such they would have to learn a whole new scripting language and make each tool twice.
-R
:summons Raven:
Anyway, i agree with pak, when he says "The tool is not 'irrelevent' but it is secondary to the skillset." allthough i'm fairly certain that my seconding him holds no weight what-so-ever, since i haven't had any experience in the field. I would say it seems most logical, though, for them to think that way.
Of course it's important. You don't want to have "lol i don't know 3dsmax BUT ILL HAVE FUN WITH AT WORK N LEARN DO THINGS" in your portfolio.
[/ QUOTE ]
What company do you work at again, Cheapy?
It gets even more complicated once rigging and animation are involved. But up until then, anything goes really. I've been using different apps for pure modeling work for over 4 years now with no bad consequences. It's a comfort thing really. If you prefer the tools or workflow in another program, use them, as it probably makes you more productive. Just know that there is a cut-off point where you will have to use what's in the pipeline - unless you have coders that actually want to support a second application (rare).
Anyway, I stand by my point because I've seen it work myself and I still do it today.
Some places will flat out force you to do it their way. That's short sighted and a bit too inflexible in my opinion. It says to me that the guys who established the pipeline don't know enough about the process to allow their artists a bit of room. Fine, that's the only time a single app becomes absolutely necessary - better to do what you're told than lose your job right? Glad I don't work in a place like that though. I like having a bit of choice in how I do my work. It makes me a happier employee. =]