the Junkyard: 2845 Development Process Summary
 
Starsiege Series Tribes Series Halo Series
2845 Development Process Summary
 2845 Development Process Summary
Thu Dec 1st, 2005
Posted by: IVIaedhros at 08:56 AM link to this newspost

*Sigh* You know you're starved for new news when the most exciting thing going on with 2845 is RSS feeds. Makes me yawn just thinking about. However today, we have a new bit of info that is slightly higher up on the cool scale. Below is a summary of the weekly development process that the dev team goes through.


You sure do update your art assests a lot...

Yes, yes we do. The process works like this:
We have two seperate internal builds that we use, one for the art team and one for the coding team. This seperation is to make sure that if someone accidentally fubars something it doesn't completely halt production across the board.

On Sundays and Wednesdays the two internal builds are then combined into the team build that you see me listing the info for in this thread. We then have a few people run around in a server to test the team build and make sure everything is kosher, make suggestions on what needs to be tweaked/changed/dropped/etc.

The Art team build tends to get updated an average of about 10 times a day by various team members, sometimes more. Depends on whether or not some people are in school or out at the time. This can be everything from someone uploading a new level design asset to new weapon effects to new HUD art to new maps to whatever. For example yesterday I myself submitted 3 changes to maps I am working on.

The coding team build tends to move slower, due to having less coders than artists, and it's much more involved work. And that's it in a nutshell.



Okay so it's not that cool, but the ATR is supposed to be released soon *smash wood repeatedly* I do plan to try and get another exclusive something or other however, so don't despair 'k?

Comments >>

Powered by Sitekore