Double Cross, modelling and level design - balancing the 2

After the presentation last week (that I think went quite well!) it's back into production. Over the next few weeks I feel we need to really focus on a couple of things.

#1 - Getting a working prototype out the door.
This is so, so important and thus far we haven't managed to do it. I wouldn't say it's any of our fault that this has happened. But we have such a nice mechanic and at the moment we don't have the technical abilities to pull it off. In short we need someone familiar with programming and is possible scripting for UDK. Now we have two options, hunt for someone who can do this or one of us learn to do it ourselves, possibly sacrificing other areas of the project. So I'm stumped. We have a meeting tomorrow so hopefully we can discuss a solution then.

#2 - Having a defined art style in engine.
By this I mean something within UDK that shows how are game is going to look. At everything apart from the actual static meshes is out of the box UDK (textures, skybox etc.) and it's painfully obvious that UDK is the engine behind the game, not good.



Here's a shot of what I've been modelling. Although it's not great because it doesn't show all the work I've done pulling models apart and making them re-usable... meh. The problem I'm having at the moment is balancing level design and asset creation. Trying to build the level without getting bogged down in details is hard. Of course I want the level to look nice but a lot of these assets need love to bring them up to a better standard. But at the same time I need to focus on the level over all and work on elements of the environment that are important to game play. Basically what I wanted to say is balancing these two is tricky. And I feel at the moment, especially taking into consideration the 2nd point I made earlier, focussing on the features important to game play within the level should probably take priority. As much as I enjoy modelling weird little bits and pieces....

And my website is down :(
Yesterday I posted my double cross dev diary & post mortem on Polycount which must have been read a few times because it killed my bandwidth. Which is a bit of a good/bad situation. I'm happy my site is getting traffic, but now it's dead! Also had some nice feedback from the people over at polycount!

anyway if you want to read the dev diary & post mortem here is a link to it on media fire: http://www.mediafire.com/?5fdfdbzsf69jhjo

Comments

Post a Comment

Popular posts from this blog

10 design lessons from 10 years in games

Image
10 years ago I started working in the games industry. Along the way I've picked up a few things that I wanted to record (for my own sake!) and share with you. 1. Understand the problem before chasing a solution Don't be tempted to start designing a solution when the problem is not fully explored and understood, take the time to focus on what you're trying to resolve. Make sure you understand what the solution needs to accomplish then formalize your findings, write them down. Develop goals. Present these to other team members, discuss and amend them as required. It's always better to debate the purpose of a feature than to debate a feature with no obvious purpose. 2. Don't pop an idea before it's fully inflated When a new idea or feature is proposed it's tempting to start immediately identifying flaws or concerns. Avoid writing ideas off or designing fixes based on these assumptions. Although these concerns are likely valid it's worthwhile giving the peop
Read more

first building basic modeling pretty much done

Image
The basics of the first building is done! There's a few things in there that I would (will) probably tweak and change. I'm not 100% happy with the walls, some of them are too solid looking and need to feel more like they have been nailed together with scrap wood and sheets of corrugated iron. Saying that the basic shape and layout of the building is down and that was what I was aiming to achieve. Next I'll be modelling the walkways along the front of the buildings and hopefully making some plans that I can re-use throughout the level. What I am slightly concerned with is that it's looking a bit too much like a pirate town at the moment but I hope when I add textures and props that it will start looking more like a slum. Maybe I will add some more partitions in the buildings to give a more cramped feel. The most difficult thing so far has been keeping a consistent scale that can be traversed in unity by the standard first person controller and looks right. Overall I'
Read more

Design Notepad: The Perfect Un-planned Feature

Image
Unplanned features, a concept that doesn't sit well with most game developers (producers I'm looking at you), and rightly so! Additional cost and bugs means they can be risky. After all, they are the very definition of feature creep. However, making games is a creative process. Things change during the course of development, inspiration strikes or something you've been experimenting with turns out to be a huge value add. Not all features are born equal, some are much more suited to being a last minute addition than others. What are the attributes of the perfect unplanned feature? How can we spot them and take advantage? Makes use of what's readily available If the feature can be created with elements from existing systems and assets it's immediately something that's worth at least considering. It's a "modder" approach, taking elements of the games that were created to do one thing and repurposing them to create a variation of a feature or even som
Read more