Search the Community
Showing results for tags 'production'.
Found 4 results
Update by Brandon Adler, Literal Task Master Welcome to my world... As a producer, one of my jobs is creating and understanding the game's master schedule. It's a never-ending task that requires constant refinement and adjustment. Anything that is added or changed can cause a cascade of unintended consequences which is why as game developers we have a responsibility to vet everything that goes into the game. Today I'd like to give you a glimpse into how we approach game development from a scheduling perspective and what our typical thought processes are when figuring this stuff out. You will be able to see how each part of our area creation fits into the schedule and why changes and modifications can lead to difficult decisions for the team. Hopefully, it will give a bit more insight into the tough decisions that we make each day when crafting Project Eternity. The Schedule One thing to remember is that when we are in the middle of production the schedule has already been created for just about everything in the game. What I mean by this is that we have identified all of the major tasks that will need to be accomplished and allotted time and resources in our budgets to match those tasks. Depending on the team's familiarity with the type of game we are creating, this can mean anywhere from a tiny bit of guesswork to larger amounts of... estimation. With Eternity we are very familiar with what it takes to make an isometric, Western RPG with branching dialogues and reactivity. It's Obsidian's bread and butter. Because of this our initial estimates are good approximations. Since most of our features and assets are budgeted at the start of the project, any changes to those items have to be accounted for in the schedule. This can mean a few different things - anything from reducing time spent on other tasks, to changing previously scheduled items, to outright cuts - and when changes need to happen project leads consult with each other to try and figure out the best option. Keep this in mind when I start talking about changes to features and assets later on in this update. One Small Interior Dungeon Alright, let's stop talking in generalities and get into the meat of what it takes to create a first pass area in Eternity. I'll discuss a generic small interior dungeon area. This area will have the following characteristics and constraints: Uses an existing "tileset." We don't have tiles in Eternity, but we do have sets of areas that share similar assets. Will have one unique visual feature in the area. This visual feature is something that will make the area stand out a bit. It doesn't have to be incorporated into the design, but we may want to do that to get the most bang for the buck. An Average complexity quest uses this area. "Average" is a flavor of quest in Project Eternity. It refers to the overall complexity of the quest. Quest complexity is determined by the amount of dialogue, branching, and steps a quest has. This is a 3x3 interior. A 3x3 interior is the equivalent of a 5760x3240 render. An easier way to think about it is that a 3x3 area is nine 1920x1080 screens worth of content. You can imagine that making an area even a tiny bit larger can actually lead to enormous amounts of work. As an example, a 3x3 is nine screens of work, where a 4x4 is 16 screens of work... almost double the number of screens. To create our small interior dungeon area, the following has to occur: An area designer (Bobby Null, for example) puts together a paper design for the area. This is usually part of a larger paper design, but for this purpose we can say that it is a separate element. For a small area like this, a paper design wouldn't take more than a quarter of a day. Material concepts for a high wealth interior. After the paper design is constructed, it is passed to the area design team for revisions and approval. For the most part, this goes fairly quickly and normally wouldn't take more than a quarter of a day for a small area. A concept artist (Hi, Polina and Kaz) creates a concept for the unique visual element of this area. Let's say for our purposes the unique element is a cool adra pillar that is holding up a portion of the ceiling. This takes half a day to a day, depending on prop complexity. This may seem like a luxury, but making sure that the areas feel cohesive can save lots of revision time down the road. After the concept work is completed, it is reviewed by the Art Director (Rob Nesler) and the Project Director (Josh Sawyer). Any necessary changes are then made before being approved. Overall, it probably takes about a quarter of a day for review and any revisions that need to be done. An initial pass on a blockout before it has had a review. After the paper design and concepts, an area designer creates a 3D blockout of the area in Unity. This allows the designer to walk through the area and make sure it flows well. This also helps to give the environment artist assigned to the area an idea of where the various elements should be laid out. A full blockout of a 3x3 area normally wouldn't take more than half a day. This is an extremely important part of the process. Sometimes an area seems great on paper, but in practice it is clunky or frustrating. Once the blockout is finished it's passed along to the area strike team for review. The area strike team includes people from most disciplines. This is the point where revisions are performed and the layout becomes finalized. The changes can be as simple as moving some props around or as complicated as redesigning major portions of the layout. Again, for a small area of this size, we aren't looking at more than half a day for all of the feedback and revisions. With the blockout in place, the area can move to environment art (For example, Hector "Discoteca" Espinoza) for the art pass. This includes putting together existing pieces and creating new assets to make the area. A large portion of time allotted to an area is spent in environment art. A 3x3 area that uses mostly existing assets would typically get three days of environment art work, but, because we want to have a cool, unique piece in the area we will add about a day of environment art time. This gives a total of four days for the initial art pass. Like the blockout, the art pass is usually reviewed by the area strike team. Revisions can vary wildly depending on how everyone feels about the area, but it isn't uncommon for another quarter to half a day to be spent on review and revisions for this size of area. The blockout above with revisions, 2D render, and initial design. Now with the 2D render in place, the area is ready for the real design work to be done. An area designer will typically get about three days to do the first pass on the area. This includes things like a loot pass, encounters, trigger setup, temp dialogs, etc.. Because this area has a quest that is running through it, though, it will get an extra day to work out all of those kinks. That puts us at four days for an initial design pass on the area. Remember the part about this area having a quest? Well, now is when a creative designer (Like Mr. Eric Fenstermaker, for example) comes through to write the dialogs. To be completely honest, this usually comes much later, but it works for our purposes. The narrative designer creates the NPC dialogs, quest dialogs, and companion interjections for the area. Usually an area designer will stub these conversations out and the narrative designer will come in and complete them. Depending on the amount of dialog this should take around a day or two for everything. Finally, a concept artist will take a pass at painting over the final 2D render. This pass is used for "dirtying up" an area and adding in the little details that might be difficult for an environment artist to create. As an example, we can cover up texture seems, add in variation on repeating textures, paint in lighting highlights, and even add things like patina or moss on objects. Due to Photoshop magic from Kaz, we can even propagate those changes into our diffuse maps so they show properly in any dynamic lights. This is a fairly low cost procedure and Kaz can cover a small area like this in about half a day. There are other considerations (Like animation, sound effects and visual effects, for example), but we will stop for now. So, for those keeping count at home, to get a first pass area that is borderline Alpha (as in no bug fixing or polish work) it costs the project about 13 man days. This is little over one half of a man month of time for a small, simple area. Larger areas with more content take significantly longer to develop. Our time estimations used for scheduling are determined in preproduction (prepro) phase. Our vertical slice (the end of prepro) is the culmination of the team identifying what it will take to make the game and then actually doing it. We get these numbers by seeing how long it takes the team to perform those tasks in our prepro, and then we can extrapolate those numbers over the course of the time we have budgeted to understand how much work can get done. Tough Choices A milestone will have 15 to 20 areas of varying complexity going at a time. A minor change in an area can cause a domino effect that starts schedule slippage. Remember that on a small team like Project Eternity we have a limited number of people that can work on any one part of the game so taking someone off of their current task to work on changes can gum up our pipelines and prevent others from completing their tasks. We can get around that by switching up the tasking, but it can quickly get out of hand and lead to inefficiencies. That being said it's the team's responsibility to give our backers what they have paid for. If we are playing though part of the game and something feels off from what we promised to our fans, we need to seriously consider making changes - even if it pushes us off schedule. There have been times where an update leads to some serious discussion on the forums and within the team about a direction change. Ultimately all of that gets added into the equation as well. Taking that into consideration, the team has to make difficult choices every day. Do we go through and do another prop pass on a level? What does that cost us in the long run? Will we lose an entire area in the game? These are questions that the leads struggle with everyday. We are always weighing the cost of assets and features against everything that still needs to get done. Luckily, like I mentioned above, we have a bunch of smart, talented, experienced people working on Eternity. The pitfalls we have experienced in previous games give us a leg up when we are trying to navigate this project's development. I wanted to send out this update to give the fans a little insight into our daily processes and demystify what probably seem like arcane decisions. If you enjoy these types of updates, let me know in the forums and I will try to write more of them for you.
NeoGAF got an email today about their $5000 tier Inn. The email was posted in the forum and contained the following news: This might be a telling sign for tomorrow's update.
Today's update is different from what we've done so far, and is to give you a look at what's going on at the studio. During the making of Project Eternity we want to give you an idea on how our games are made. Making games is not magic - game development just boils down to a lot of work from a lot of talented people. I would like to pull back the curtain, and give you the who (the talent) and the what (the work that they do) to make Project Eternity a reality. The Stuff RPGs are large and complex games that have a ton of stuff, and much more stuff compared to most games. Characters, companions, dialogues, areas, monsters, abilities, spells, items, weapons, armor, sound effects, visual effects, interface art, music, crafting recipes, animations, textures, crates and quests are the bits of stuff in Project Eternity... and the list goes on and on. At the time that we finally ship the game, we will have hundreds of thousands of bits of stuff in the game. Managing and creating this stuff is one of our major problem when creating RPGs. Our task is to make all of the stuff as efficiently as possible with a high level of quality. Right now we are knee deep in pre-production. Pre-production is the period of time at the beginning of development where everything is planned and prototyped, production schedules are made, and pipelines are constructed. I'm not talking about oil pipelines here - I'm talking about asset pipelines. An asset pipeline can be described like an oil pipeline - First the asset is made by a content creator (like an artist), next the asset is processed by a tool so that the game understands what the heck it is, and finally the asset is placed into the game world in its final location. All of the different types of assets (stuff) require a custom pipeline. Pipeline creation is one of the many problems we are tackling right now in pre-production. The Team We have many different roles (sometimes called "hats") on the Project Eternity team. Most of the team fall into three categories: content creators (makers of stuff), programmers (making the stuff work), and production (making sure the stuff gets made). Our role percentage breakdown is a bit different than what we typically have on a project. If you look at my fantastic pie-charts below, you can see that we are content focused because we have larger design team, and since our team size is small we don’t have the need for a large production staff. All of these roles are equally important and are all vital for making the game great: Art Animation: Animation adds life and movement to the game. Every moving object in the game requires an animator to be involved. Effects Art: Spell effects, sword swings, fire, smoke, and blood are animated and designed by an effects artist. Environment Art: The environment artists make the world look beautiful. They do a pretty good job at it. Character Art: Character artists create the characters, companions, and monsters. They also model and texture all of the weapons and armor. Concept Art: Concept artists paint and illustrate environments and characters that fit within the art and design vision. Their art is used by the rest of the team for reference on style, mood, color, size and proportion. They also paint the 2D portraits and touch up the 2D pre-rendered environment scenes. User Interface Art: All of the buttons that you push, the interfaces that you interact with, and all of the mouse/item/weapon/spell icons in the game are designed and crafted by the UI artist. Audio Audio Design: Audio design is responsible for any and all of the audio that comes out of your speakers. This includes the creation and production of all of the music and sound effects, and making the character voices sound great. Design Area Design: All of the cities, towns, dungeons, and wilderness areas that you can explore are designed by area designers. They take the environments and characters made by the artists to construct a rich and believable world. They also fill the game with quests and combat encounters. Narrative Design: RPGs contain thousands of lines of branching dialogue and huge non-linear storylines. The world, story, companions, factions, lore, and themes are created by the narrative designers. System Design: Rules and systems specialists. They like numbers and spreadsheets. Combat, abilities, spells, non-combat skills, and items are designed by the systems designers. Production Production: The producers organize the team. They make sure everything is running like a well-oiled machine. Producers have the responsibility for making sure the game is delivered on time, on budget, and is awesome when it's shipped. Programming Engine Programming: The engine programmers deal with system, rendering, and physics code. Unity handles a lot of our engine-level programming for us, so we can focus our programming time and energy on gameplay. Game Programming: The game programmers implement the game design including the rules, combat, and abilities. They also code up gameplay systems like dialogues, quests, stores, and create artificial intelligence for monsters. Tools Programming: Pipelines and tools used by the team are made by the these programmers. Most of their code lives "outside" of the game code. Quality Assurance Quality Assurance Testing: The QA tester reports in-game problems to the rest of the team. They make sure that all the stuff is working together and functioning properly. We want to go into more detail on what each person does on the team in future updates. A two sentence description trivializes the responsibilities for each team member, so in the future we will dig deeper and take a closer look into the disciplines. Next week Josh has an update with lore and other fun worldly things. Update by Adam Brennecke
Couldn't find the appropriate topic on the subject, but I was thinking just how long a game of this scope might take to produce. In my opinion, it will be no less than two years, which is unfortunate since there's a few games that I would want more than a BG/PT/IWD spiritual successor. Truthfully I shouldn't think about this game because upon realizing the production hasn't even stared yet makes me want to forget I even know of its existence