[bucky60]

Quote: Originally Posted by T4VERTS

Can't do that for one off large scale projects. You can't hire in a bunch of brand new people only to lay them back off after the project is complete without blowing a ton of time and money. Spending time to train them to take on the project in itself would be a huge resource sink. In cases like this where it is a project rather than a new division, you have to scavenge from within your current asset pool. It's just the way companies have to operate and part of being a business before anything.

Quote: Originally Posted by Cato06

This is very true. The only way this would work is if you were getting already proven talent from other companies that could handle the tasks and not have to be trained. Hiring more people and having to spend half your time training them just to get them up to speed will really effect the workflow and slow everyone down resulting in less actual work getting done.

Quote: Originally Posted by T4VERTS

No those are separate teams, so there is game play (Orlando) and CFM (Austin). In this case they borrowed assets from the CFM team to work on the frostbite transition because it was a "one time" large scale project. If you bring in a whole new team to take on such a project you have to train them on the intricacies of how the game is coded taking longer to get up and running. When they are done you then have to decide where they are going to sit full time or if your going to lay them off. From a business standpoint it simply makes more sense to use current assets to do the projects.

What does Frostbite have to do with CFM? How does CFM experience translate into knowledge of Frostbite?

I would bye into the point if it was the gameplay/presentation team with no gameplay/presentation improvements for the year. Isn't Frostbite more of a game animation/presentation engine?