Level Design Pipelines!?

I dont work in the industry, yet, but i sketch the map, put the rough blocks out, then work from three. Eat 3d has a great UDK tutorial for this .

I'm not in the industry, but I'll give my 2c on Sketchup.

Sketchup is awesome for creating exact 2D layouts to proper scale, but kinda sucks for full-blown 3D. I've done both creating a 2D layout in Sketchup and building the actual geometry via BSP (in UE3) and gone the full blown 3D model in Sketchup and imported into the editor (in Source).

UE3 kinda throws you for a loop that only allows for additive geometry building (6 BSP blocks to create a square room) whereas UE3 allows both additive and subtractive (1 cube additive brush and 1 subtractive brush to hollow out the first cube).

To start out on your own, it's probably just best to do it how you're most comfortable, but learn a 3D suite so you can easily hop into a studio that exclusively builds in 3D suites and imports into the game engine (id Software, 343 Industries, Sony Santa Monica, etc.).

I've actually written an article about my workflow, you can read it here :

http://www.worldofleveldesign.com/categ ... enssen.php

It depends on a few things for me. At work, its such a team effort that the process is very long and involves alot of people doing specific things. In my case that is scripting.

I've messed around with alot of planning tools, sketchup, visio, illustrator, grid paper, whatever, but in my opinion the engine you will work in is a better tool for "planning" than anything else as it will tell you immediately if something is too big, breaks line of sight, isn't long enough, and so on.

A typical process for a personal project MP map for me is this:

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/dm-zharplista/skysilcox_dm-zharplista_bsp-build01.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/dm-zharplista/skysilcox_dm-zharplista_overview_0.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/dm-zharplista/skysilcox_dm-zharplista_bsp-meshpass1_0.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/dm-zharplista/skysilcox_dm-zharplista_terrain-meshblockin_0.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/dm-zharplista/skysilcox_dm-zharplista_massive01.jpg]

[Blocked Image: http://www.skysilcox.com/dev-blog/wp-content/uploads/2010/08/artpass_valvebase0010.jpg]

[Blocked Image: http://www.skysilcox.com/dev-blog/wp-content/uploads/2010/09/market00093.jpg]

SP stuff is bit different as scripting is the crux of the map, but I still tend to just hop in and start making stuff before thinking about it too much, opting to think as I work instead of before. Obviously in a professional environment, so many people are affected by what I do, more planning is needed.

This singleplayer Gears map designed itself as I went, adapting to the combat systems in Gears of War which require mostly flat surfaces with line battles to work well.

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/mr-toads-wild-ride/skysilcox_mrtoads-wild-ride_process_layout2.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/mr-toads-wild-ride/skysilcox_mrtoads-wild-ride_process_layout4.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/mr-toads-wild-ride/skysilcox_mrtoads-wild-ride_process_layout5.jpg]

[Blocked Image: http://www.skysilcox.com/wp-content/gallery/mr-toads-wild-ride/skysilcox_mrtoadswildride_overviewlayout_0.jpg]

The way I approach a professionally developed map is defined by how the studio does things for the most part.

For personal projects I usually do a little sketching on paper ahead of time to brainstorm, figure out some key gameplay ideas, etc. When I get some sketches that feel like they could be a good start, I go to the editor and whitebox. The whitebox always goes through a lot of iterations; I'll load it up in-game and run around in it whenever I add anything new or make a change, trying to put myself in the mindset of a player. At some point in iterating the whitebox I'll branch off a copy and start adding textures, props, decals, etc. to demo visuals and make sure they fit with the shape and dimensions of the map. Eventually the whitebox stabilizes and then I'll spend a few weeks on visual passes, lighting, vfx, etc.

For professional work it very much depends on the individual project. People can be assigned to work on levels at any point in development and you may have to do any combination of sketching, level building, scripting, and prototyping what you need art assets / lighting / vfx / sound etc. to do in the level to help communicate with respective disciplines. The job includes maintaining the level's vision on its own and within the context of the game, solving design problems with a cross-disciplinary team, as well as things like scripting, building and fixing bugs.

I have never used Sketchup, and in my time at Ubisoft, haven't seen many people touch it either. The main reason is that Ubisoft uses different engines that all incorporate better modeling tools, or ways to incorporate models made in Max or Maya faster than Sketchup.

If you end up working at Ubi, in Canada, you're likely to use one of three main engines: Dunia (Far Cry 2, other shooters), Anvil (Prince of Persia, Shawn White, Assassin's Creed, other games) or Unreal (Splinter Cell). And the latter is on its way out if not out altogether. Dunia is based on the CryEngine, and incorporates many tools to make your terrain a lot faster and compatible with the engine. And the solid/block tool is very good too. Anvil will have you model things in Max and will export things in two clicks, whereas Sketchup would take you through another extract process.

All the same, the process is a little bit the same for everyone in the end. You start by figuring out what you want to make (that means, professionally, what you have been told to make in many studios), you do your research to get inspired, talk to the concept artists and the art director about what their vision may be, and you go cracking. A 2D layout is always a great idea, and should be part of your research to get inspired. It may not have to be on paper if you're more comfortable with photoshop and or a tablet, but you get the idea.

Always focus on the gameplay, so white box your main path (that means use rough untextured blocks) to simulate the space you'll be navigating in and set that in stone before the artists get to work on your level. If you change anything substantial after they've art passed your level, you will cost a lot of man hours to your project and make a few people angry in the process. So get your stuff reviewed very fast, and every time you change something substantial. Get your lead to sign off on it, then get it to the artist that will spice it up.

Rinse and repeat, that's a level designer's job

NB: In some cases, you may work on games that require you to be a mission designer within levels that are already made. That's the case with all open world games, where the levels (the cities) are made by architects/artists to respect the overall integrity of the game. If that's the case, the process changes quite a bit as you won't be doing any of the blocking, and will focus on maximizing the existing space to make it fun. In Assassin's Creed for instance, that means you get to place the different platforming ingredients along the buildings and streets. It's quite a different process as you should be more focused on story telling and overall pacing than on lighting, scale or optimization.

Finally in some cases yet your work may be more akin to that of a game designer. When I worked on the flying wing in AC2, my process started by exporting the alpha version of the city of Venice into Max for the prototype that was made outside of the engine, and importing the non working, pure model of the flying wing into the engine, so I could just place it in the air throughout Venice to get inspired for the mission, set the path I would later use, change the scale of the flying machine, etc.

The very first time I presented my mission for the flying wing in AC2, I used a powerpoint presentation of different screenshots I took in game of the flying machine idling in the air. It still sold the idea rather well for what was to come.

Go to http://%7boption%7d and check out the interviews with LDs/LAs. Almost everyone said something about his workflow.

Just to clear up Furyo's reply; some teams do use Sketchup during the level sketch phase.The rest is spot on.

All of the above workflows sound pretty close to my workflow at work, one thing I like to do to start with before sketching or blocking out a map is to write down every sequence thats going to take place in the level in a logically order, for example it normally ends up looking something like this:

• 1 - Player Start
  2 - Starting Cutscene [write about what the cutscene is about]
  3 - Rest Section [write about what is keeping the player interested while no gameplay is taking place]
  4 - Enemy Encounter 1 [write about what type of encounter you want to take place]
  5 - Rest Section [write about what is keeping the player interested while no gameplay is taking place]
  6 - Puzzle Section [write about what the player has to do]
  7 - Enemy Encounter 2 [write about what type of encounter you want to take place]

I've found this method very good for determining the basic flow of the level. Also I wouldn't stick to a 2D sketch religiously, in my experience once its fully blocked out and people have reviewed it, theres generally alot that gets changed.