Sunday, February 28, 2010

Screenshots of the Alien Level using the UDK

These are some screenshots from the level that i was working on as part of my semester 2 submission. I generally don't like putting screenshots up because it doesn't give you a good enough feel of the level and game play that is involed within it and just how complex of a level it was to make. Not least of all the vast scale of the level. However for those of you that want something pretty to look at . . .








Semester 2 experience

For my semester 2 project i have been working on a commissioned Unreal level as mentioned in a previous blog, but I am also doing a placement designing levels. My original thought was 'great, i can do this, this is what I'm good at'. But with any real world experience you soon realise your not as skilled as you thought and you do have to start at the very beginning in order to work your way up. I went in with all these great ideas and at first had a problem condensing them down to fit a DS/PSP title. I had never had a problem with this before as i make the majority of my level designs in the Unreal engine. My work flow for this is 'if my computers still running I'll keep adding things'. Looking back this was not necessarily the best approach to take, although this was not a conscious work flow, because in the industry they have all the extra things like frame rates and budgets to take into consideration.

Because of the platform i was designing for (DS/PSP) i didn't think it would be too hard. Instead i thought 'great that's easy, i just wont add as many things and I'll be fine'. But my first few level designs, although consciously keeping in mind the platform i was designing for, were overly complicated. I started running away with the ideas rather than laying out a plan before hand and keeping it condensed. One idea lead to another and before i knew it my lead designer was telling me 'these are great ideas, but they are more suited in an Unreal or Halo environment'. I then had to take a step back and identify where my levels were getting so thick and strip away the fat whilst leaving a sold, fresh, interesting game to play. I had to start writing things down and planning out what i was going to do which as you probably know, I'm not used to. This was a difficult skill for me to learn, if asked in University to write out a plan for a level design i would have been able to write something down, but in my mind that level would suck and the only way i could resurrect it would be to physically create it so that i could visualise and get a feel the flow of the level. After quite a few attempts i was able to isolate sections of game play by not having too much on the screen at one, but the stuff that was on the screen, i thought, was really creative and interesting and most importantly different. I enjoy being able to take a different approach to game design and try not to be inspired by other games by playing every video game on the market but to be inspired by lots of different things around me instead.

Sometimes i may take the wrong direction at first, but once i get a feel for the flow of something i can pull myself back on the track and start to move in the right direction again. This may be a more time consuming approach, but i feel like i am creating something unique that no one has played before. On the rare occasion that i have a design idea and then later find out that its been used in a previous video game title, the only excuse i can make for myself is that i must create some awesome game designs!

Joanna Mowbray

This morning we had a lecture from a sculpture artist who mainly creates her work using steel. The main focus of the majority of her work seems to consist of the differences between light and dark and how different times of day and seasons affect the look of her work. I like the organic, natural nature of her work mixed with the harshness of the made made materials. I think that this creates a nice contrast and allows her work to be separated from other artists. Some of her main influences have been Eva Hesse and Robert Smith. When looking at their work you can instantly see similarities in her work and theirs but i think she has taken her ideas a step forward and created something totally unique. I particularly like her approach to design. She works spontaneously and with very little direction. She sets herself a goal and brief but the actual design process is a very fluid one which takes any direction she sees appropriate to go in. I like to take a similar design approach to my work by giving myself a brief and a deadline but whatever happens in between is undecided and its only when my work starts to take life that i can start to feel how the level with look and what it will contain.

A reoccurring theme that seems to be popping up in the Friday contextual lectures that we have been having is the idea that most of the artists and designers seem to find themselves looping back to the same work after a certain period of time. Because the game industry is still quite young compared to most other design disciplines its hard to analyse whether looping themes would apply to us as game designers, however i feel that it would not. The main reason for this is because i feel technology is advancing so fast that it does not give us the breath to loop back on ourselves and that changes games dramatically. People may argue that its the core of the game that really counts and the same design ideas are still being used now that were used in old arcade games, and this is true to some extent, but i feel now large game companies focus on technology rather than ideas. I see the same ideas being used over and over again being worn thin, so you could also argue the ideas never really go away and come back but rather stay the same and take a different form. Big companies would much rather have a beautiful looking game that sell millions of units with tired and used game designs rather than have a unique and challenging game which would only appear to a select market of gamers and not make as much money. This means that any chance of coming back to core ideas to take a fresh approach years after creating them goes out of the window with multi-million unit selling companies and huge advances in technology.

There are also similarities behind both of our disciplines in the way that we create interactive art work. Joanna likes to create sculptures that people can interact with and walk around experiencing different emotions from different angles rather than if it was stationary. The interactive element of the design definitely interests me more than any others and taking the hands on approach using welding equipment and bolts helps you to connect and appreciate the work more knowing how long they took making the piece. Although there is no real conclusion to make about this blog its a good way to see how Joanna's work flow was used to create such individual and unique pieces and how her work flourishes from the spontaneity that she allows herself.



Monday, February 22, 2010

..another unreal level

As some of you may have noticed, this is my first blog post in a while. There are many reasons for this, mainly because I've been working hard trying to meet deadlines and haven't found the right time to write anything, partly because I've not stepped foot in a lecture hall for 3 weeks and to some extend i felt i had nothing useful to say. Not much has changed on the last point but nevertheless I will hopefully be updated my blog on a regular basis from now.

The first thing i want to write about is the work i have been doing in Unreal this semester. I ended semester one saying that i wasn't going to touch the UDK this semester and that I wanted to get back to basics in terms of level design, back to pen and paper and learning to write things down, plan and then iterate my ideas into a level design document. I also wanted to pull out the key factors of what level design documents consist of use my own interpretation of these to reformat the LDD. The reason for doing this is because sometimes when i read a LDD I do not fully understand what it is trying to achieve. Sometimes this can be because the designer has no communicated it well enough, but i think the main reason for this is the lack of understanding junior designers have when it comes to presenting the work as it needs to contain all the information that, not only the designers need, but also Animators and Artists. This is a hard thing to teach and its only really from experience that you can gain an understanding of what is needed in a document to hit all the criteria that a team needs to make your level. I will go in to more depth in a later post LDD's but for now back to semester 2.

So i started the year with a brief to create an Unreal level that had to be Alien looking, with lots of triggers and fun things to do. Without it mustn't be too complicated, but easy to navigate and also to have a constant loop so that the player could be playing for X amount of time without the game ending. The way that my mind works is to start a level with no real direction. I know the brief and what the level must contain but i don't know where I'm going to place each mechanic or what the level is going to look like. This is no doubt a bad design mentality to have, and i wouldn't argue with anyone that called me lazy for doing so. It is also questionable whether my levels would turn out better if i did plan them. But for me creating a level is all about how it feels to me at the time and i like to add things when I can visualise the mechanics and feel that they fit into a specific scenario. I don't think this can be achieved on paper but that's an argument for another day.

The level itself was one of the most challenging I have done in the Unreal engine for many reasons. The main reason was because the requirements were so specific in terms of game play the kismet (the best way to describe kismet is the scripting of the level, doors opening, lifts moving etc) i had to create i had no idea about and it was only through trial and error that i could meet the brief. The main mechanic was creating 6 triggers that when all 6 were triggered would randomly trigger off until the player decided to quit the game, i.e having no ending. This was a new concept to me because when designing levels i normally have a start point and an end point and whatever happened in between was entirely up to me. This in itself was quite a simple concept to get around however implementing it was another issue. It would have been easy to cheat the player and let the player trigger the 6 and then manually turn off different triggers after different amounts of time, however adding 'random' to the equation was a completely different issue. To add on top of all this, the player had to know which trigger had been turned off and in what location so that they could go and turn it back on. The player also had to visually see the triggers triggering on and off. To tackle this i added a Matinee sequence which consisted of a camera actor so that when the trigger changed state it would play a small matinee camera animation which showed the trigger so that the player knew which location the switch was on. I also added a simple coloured light, that turned off by default, and when the trigger was active the light would come on. This seemed to work well and wasn't too difficult. However another issue arose from this was when the trigger played the matinee, you saw the character stood there, in normal circumstances this wouldn't be an issue, but because of the concept of the level (a drone navigating a spaceship) seeing a high poly Unreal 3 character with a huge gun stood there ruined the atmosphere. I got around this by toggling a cinematic mode which hid the player and also disabled movement. Problem solved. After testing it became apparent that the player must be invisible whilst navigating the level because when you pressed the trigger there was no one stood next to it. To address this issue i used a static mesh from an existing Unreal asset which was a gun turret off of an Unreal vehicle. This worked well and i added these at every trigger and had them hidden in the game, but when the trigger was active it would become unhidden whilst the camera played and then became hidden again.

I wont go into every little detail about how i got to the end result of the unreal level but i think its a good example of how one problem in a game can turn into multiple issues. I think, as a designer, you have to ask yourself how much certain issues will affect the overall game play and how much time they would take to fix. Time is a crucial factor because when working to a short deadline like i was, you need to distinguish between issues that need fixing as they will have a large impact on the game play and factors you would like fixing but wouldn't affect the game play too much.