Jump to content
Show all categories

Articles

Lovely MapCore articles
  • General Vivi
    THE DOOR CHALLENGE!
    I want to start out by welcoming you to the 2ND Door Challenge! It’s been a little over 7 Years since we held the first one! A lot has changed in our industry and new engines have made level design more accessible than ever before. With all the fresh talent coming into our industry, I think it’s important that we challenge ourselves and each other to push our creative thinking.
    This challenge is meant to be for everyone to join in, from your first time level designer to your Senior and Lead Designers! Everyone is in a different place throughout their careers and it’s always fun to hone your skills on one of the most old school puzzles of our time “Get the Door Open!”. The last time we did this we had a fantastic turn out of completed and submitted puzzles! Especially since we are focusing on JUST design and scripting and NOT on art!
    As this is a scripting challenge, you are encouraged to use Dev textures or simple greyscale materials and only what art assets are absolutely necessary to communicate key ideas. The point is to focus on your Scripting / Presentation / Storytelling / Puzzle Making skills.
    Most entries generally took a few days to build from start to finish, so don't sweat worrying about the deadline. If you would like to get a better idea, check out some of the entries from the first door challenge.
    Remembering our Past
    SOLEVAL - First Place
      Magnar Jenssen - Participation
      Robert Yang - Participation
    Jason Mojica - Participation
    Rules and QA
    Build a puzzle and craft a story to creatively open “The Door”! It doesn't matter whether you're entering, exiting, or just moving from one room to another - just get that DOOR OPEN!
    Acceptable Engines : UE4 / Unity / Source SDK
    For UE4 or Unity, you will be REQUIRED to provide an EXE of your game
    For Source SDK, a simple bsp will do with info on the game you built it in. (Eg. Half-life 2, Portal 2, CS:GO, TF2)
    We encourage you DON’T use Art unless needed to sell your idea. Simple meshes / Dev textures / grey textures should do fine.
    You are ALLOWED to use Templates to start yourself off. Example: UE4 has a FPS , Third Person , and VR template.
    You are ALLOWED to use existing scripting/ blueprints or Code to help you make your puzzle.
    You CAN choose - First person, Third Person , Virtual Reality (VR)
    DON’T submit anything larger than 250 mbs , we want simple entries that everyone can download.
     
    The challenge will begin Friday, August 10th, and end Sunday, September 16th at 11:59PM US CENTRAL time (GMT -6)
     
    Must Haves :
    A zip file including your EXE or map file
    2 screenshots of your scene (ATTACHED! This will help us archive our entries for posterity)
    A video showing the puzzle's intended solution (hosted on youtube would be fine)
     
    Optional :
    Full Name (optional)
    Website or Portfolio (optional)
    The original level source (and any other relevant files) for inquiring minds to examine your scripting
     
    Judging : We will start judging the day after closing, Everyone will get 3 votes and then we will vote on the top 3 one week later. Things to think about when judging or making an entry.
    Innovation - More than just a simple Door!
    Theme - How close did you stay to the idea of the challenge
    Readability - Was your idea clear and easy to understand?
    Humor - Did you make someone laugh or enjoy your entry?
    Overall - Wrap everything together! Was it awesome?
    Door - Q: How much Door you got? A: Hell yes
    Prizes
    As with the previous challenge, there will be no prize other than the pride of knowing people thought you were awesome. Woo!
     
  • The Making of Murky Station: Payday 2
    Payday 2 is a four player cooperative first-person shooter with RPG elements that centers around robbing banks and stealing rare loot. It was released on August 13, 2013 and has since shipped over 50 DLC packs and counting. With a thriving subreddit, it has consistently been in the top ten games played on steam. Today, I wanted to talk about my adventures designing stealth levels for Payday 2 before leaving Starbreeze in January 2018. While parts of this article are specific problems and solutions for Payday level design, I made sure to discuss them in a broader sense. The skill level of this article is for junior to mid-tier level designers, if you are a senior designer some of this article may sound familiar to you.
    I'll start off by saying that Payday's stealth mechanics are not perfect and can be flawed in some areas, but I wanted to focus on the decisions behind the map design, specifically for the heist Murky Station. I'll also break down how we consider using RNG (randomization), and the ways we apply it to objectives and mechanics to keep the level fresh and replayable. This map took 6 weeks to make between 2 people. My partner took the role of Level Builder / Environment Artist and I took the role of Designer / Scripter. Between the two of us, we figured out the scale of the project based on the needs of our studio. The idea was to create a small heist that took around 10-15 minutes to finish with high replayability. There's a lot to go over, so let’s get started!
     

     
    Let's start from the beginning
    Before we start drawing or building layouts, we make the call if we are going to create a Loud level (combat only), Stealth level (avoid combat), or Mixed style map. For the short period of time given to us, we decided to stick to stealth only. Making this decision early on helped us create better movement options for the player and focus our efforts towards balancing patrols and objective placement. We decided that the theme of the level was a small train depot run by a group of mercenaries shipping large weapons. The main objective was to infiltrate the depot and steal an EMP bomb. Keeping the objective simple and intuitive is important in multiplayer games where players can drop in and out of the experience at any point in time.
    We decided to shoot for 10 - 15 minutes of gameplay. Breaking down our main objective into smaller sub-goals that could take about 2 minutes each (this is based on our extensive knowledge of payday 2). It should be noted that this time assessment will change once the player has completed the level a few times. These numbers tend to get cut by a third, or in some cases, by half. With our main objective in mind, we can construct a simple flow diagram for the heist and start to think about possible dynamic and RNG elements that can be used to create a re-playable experience.

    (This is a scripting example from our editor, each entity has it's own function)
    Testing your ideas before scripting them? Wait... What?
    Since 90% of Payday levels are hand scripted, it's important we don't waste time building the wrong things. Testing your objectives and complicated RNG elements has to be fast and efficient. The last thing you want to do is build an entire system and find out it sucks. Most of the time you don't even need animations or even a model to properly test your ideas. At such an early stage some floating debug text will do just fine. You might be asking, what if I don't have debug text or the ability to script? When playtesting levels for Payday 2, a lot of the time we'll get a simple block-out done and then ... here it comes ... pretend we're doing the objectives.
    It might sound crazy (and not everyone can get through it without laughing) but we'll have one of the designers act out the role of Bain, our mission giver, and just spout objectives at us. We'll move through the space and pretend to see guards or hack laptops and delay time based on things we expect to happen. You can basically break down how your systems might work and try out a few possibilities. For example, knowing that you might have two escapes at either side of the map gives you enough knowledge to make pretend decisions. Telling your fellow devs the van is arriving up top and pointing out where to secure loot can help you find out if a location is interesting for the escape or not.
    Even though the artists might giggle, or people from the other teams walking by stop and wonder why they can't see that hoard of enemies. It really works, and can often steer the level in the right direction and prevent us from investing too much time on the wrong objectives. Now, I know this approach won't work for all studios or situations, but all I gotta say is... don't knock it till you try it...  
       
     
    Constructing our Sandbox Layout
    Now that we've pretended to run through our objectives and have gotten used to our basic block-out, let's talk about the layout we built for Murky Station. We went for what i'd like to call "the onion approach", which is pretty much what it sounds like. You'll have multi-layered rings that give you the sense of progression towards the center (or a goal). Essentially, we use the outer layer as the player start and each sub-objective is based inside a different layer until the player reaches the main objective (at the figurative center). This approach is very useful when working with sandbox type levels, especially when the player can virtually go anywhere they want.

    Side Note: We also layer our music track each time a sub objective is finished, creating more suspense and a sense of agency.

    You can see that the outer onion layer is the player spawn (colored green) on the overpass which gives them a full view of the trainyard. From here they can study patrol routes, train-car positions, and possibly objective locations. The overpass can also be used by a player with a sniper rifle to mark guards in the different lanes, helping provide accurate information on guard positions for the players on the ground floor.

    The next layer is breaking into the train yard through a fence around the perimeter. The fence is here to guide the player and give them a visual boundary for the "safe zone" (where no guards patrol). The next layer is searching the train cars to discover where the main goal is hiding, followed by breaking through the vault doors inside of the trains themselves. These onion layers have to be carefully managed to give the proper impression to the player. Too many layers and you might confuse the player or make them forget what they're doing, too few and you might leave them feeling unchallenged or unaccomplished.
     
    Player Mobility is key!
    Mobility is key to providing players opportunities to express themselves and make better decisions while traversing a level. I felt that it was pretty important for Murky Station to allow for different play styles ranging from slow and methodical to fast and dirty. The last thing I wanted was to force players to play a certain way or for the routes to become predictable and linear. In order to do this, I spent the first week of development prototyping and testing out different layout ideas that would maximize paths and choices for the player.
    (Here is a simplified top-down of the routes in the train yard area)


    It became obvious that we would need to allow players to traverse through and under the trains as they cover most of the real estate in the train-yard. Unfortunately the older train assets were not built to go underneath, but lucky for us, the nighttime setting of the level would cover up this fact. There being only 2 of us on this project, I took a crash course in Maya and cleaned up the bottom half of the trains by removing collisions and remodeling them for readability purposes.


     
    The next challenge was to teach the player they could hide under trains and be safe. Payday players haven't been under the trains in any other heist up until this point, so we needed to call attention to that but also show them it was a safe place. Making these spaces dark and in the shadows helped create an illusion of safety but also made it harder for players to find them.
    To help solve this issue we added yellow caution tape as a trim and a dim red light under the wheels to catch the players eye. These combined elements would then be used as visual vocabulary in other parts of the level to teach players something should be explored.


    One of the other ways we added more routes to the level was to build a ventilation system in the lower tunnels. Leveraging the fact that this was a stealth level to create these smaller spaces, especially since they didn't have to accommodate 40+ police officers. The vents allowed players to safely view guard patrols, search for objectives, and move loot. To prototype this, I built a modular vent system using basic mock-up units that allowed for rapid construction and testing. Funnily enough, the first iteration of the vents was too small and caused players’ bodies to clip through the floor. I was able to rework my mock-up units and we settled on standing height instead of a crouching one. Once again we used yellow caution tape as our visual vocabulary to highlight the vent entrance on the wall.
    Modifying the trains and vents is one of the factors that contributed to the map’s success and gave new players more confidence to explore the trainyard and lower claustrophobic tunnels. So now that we've explored the different possibilities for movement and giving the player more choices, it's time to buckle down and get our randomization system built.
     


    Randomizing Objectives to Maximize Replayability
    RNG is one of the core pillars of Payday, so every decision we make is looked at through a lense of RNG. We strongly believe randomization should be meaningful to gameplay and not just added for the sake of it. It’s important to ask questions like: was it worth changing all the cups in your level? Did you gain anything from swapping out all of your cars and buildings? Was creating a third entrance valuable to the level? Maybe one day we'll completely randomize every object in a building down to the smallest cups, but in a game like Payday I personally feel these types of things have diminishing returns and can often ruin a planned design.
    When working with RNG it's important that you ask yourself as many questions as possible to start with a strong foundation, especially if you plan on finishing on time. Something I often see junior to mid-tier level designers forget is to build for scope and set priorities on their objectives. It might sound trivial, but forgetting your priorities can send you down a black-hole that eats away all of your time.
    So how did we go about adding RNG into Murky Station? Breaking down our objectives, we can start to consider what RNG options are available and doable within our one month time frame. I've also labeled them with my personal priorities (low - high).
    Break into the train yard randomize breach locations (low) Locate the Bomb Train randomize train configurations (high) Hack into the train randomize panel to flip sides (low - medium) Open the Vault 4 different vault door / key types (high) Find the Vault keys The map supported up to 40 hiding locations (med - high) Secure the EMP bomb parts 2 escape locations, 1 chosen per playthrough (medium) I focused most of my efforts on randomizing the train configurations, vault doors and key placement. These objectives were critical in influencing how the player would move through the main space and how they could tackle the same area in different ways through multiple playthroughs. In order to accomplish this, I broke down my sub-goals into digestible points of interest and isolated them into their own prefabs (shown below). Doing so allowed me to script one prefab and teleport it to as many locations as I wanted. This approach made the randomization more manageable to script and cut down the amount of bugs that might have formed if I built everything by hand each time.

    Side note: We gave each one of our key / vault prefabs its own unique visual and audio so that players could identify them from a distance or listen if they were close by. Providing them with this level of feedback is critical in helping them make proper decisions while traversing the level.



     
    Now that we have our vault doors and keys figured out, I can begin the planning process of placing them throughout the level. When placing them, each location must meet certain conditions before being finalized. The main goal is to provide the player with a challenge and also encourage them to be creative in tackling the surrounding area. Having designed the layout to have many interesting choke points and traversals, it was fairly straightforward where I could place them. Collecting the keys is one of the more RNG based objectives in Murky Station, sometimes all of the keys are in different corners of the map and other times they are all next to each other. Eventually there was a script clean up to prevent overpowered locations or terrible RNG possibilities, but overall it was a huge success for the level.
    We generally kept the key locations central to the layout and tried not to place them too close to the player’s safe zones. Placing several keys along the outskirts was a nice change of pace from the main lanes, providing a different type of challenge due to the openness of the layout.
    This is what the upper train yard looks like and how the keys are distributed. The lower tunnels have the same amount of keys placed.


     
    We also used the same method for spawning the train interiors and vault doors. By creating one prefab and scripting it four times inside the level (one per vault door type) we were able to randomize the location of the players’ main goal with little effort. The engine also allows us to rotate our prefabs, giving us the option to flip the train interiors.  This added a whole new layer to their configurations, since some of the interior layouts were asymmetrical.
    We ended up with roughly 600 train configurations, 2000 vault door combinations, and 256 sub objective configurations. With 1 of 2 exits being chosen randomly each playthrough, this really changed what types of decisions got made by the players. It also influenced how they would flow through the level and took advantage of their diverse set of movement options.
    On top of that we use non-linear objectives, which basically means you can do multiple objectives at the same time or in some cases, different orders. In Murky Station, players can simultaneously be looking for keys, searching through trains, marking guards from the overpass, and securing extra loot they find. This allows 4 players to comfortably split up to cover more ground and work off each other. A well coordinated team might have two players hacking into the trains to find the EMP bomb, while the others are looking for the vault keys. I find it very important to provide all players an opportunity to contribute towards the main goal.
    Side note: With all of this randomization, you might be wondering how QA can test it all. The short answer: they don’t. We need to build efficiently to insure 90% of the level is solid, and then catch as many edge cases as possible. On the Payday team, the frontline of defense for QA is the designer making the level, It’s our job to test our own work thoroughly! The way the systems above were built would only required 1 prefab to be maintained for each example. This provides us the freedom to go nutty with the customization in the level, knowing it has a low chance at affecting our prefabs. So, as long as we build smart we can cut down the amount things QA needs to test and help speed up production.

    With the objectives off to a good start, let's take a look at how RNG might affect our guard patrols and cameras in the level.
     

     
    Guard Patrols and RNG
    Randomization can have a large effect on how smooth or frustrating a level turns out to be. One of the things we have to keep an eye on when designing stealth levels is frustrating the player through poor patrol placement, amount of guards, and how long they pause at each location. The goal is to create a fun puzzle-like challenge, not a terrible waiting game. Bad RNG might have you sitting in a corner for one minute waiting for the guard to leave, only to have another guard take his place when that minute is up. It's our job as the level designer to help prevent such situations from happening by adjusting our timings, reworking the layout, or possibly the level’s mechanics. This is why it's so important to create a solid base for player movement options from the beginning.
    Since we don't want our guard patrol RNG to get out of hand, we need to be careful about how they flow through a space. Doing this requires it's own personal attention and multiple iterations. Tilt too far in one direction and you'll end up with bare areas that have no guards, tilt too far in the other direction and you'll have too many guards stacked on each other with no wiggle room. The last thing you want is the possibility of a death chain reaction. This is caused when you kill 1 guard, only to have another guard 10 meters away spot that body... forcing you to kill that guard, who eventually gets spotted by the next, ect. In Payday 2, players have a limit of 4 guards they can kill before the alarm goes off (on all difficulties). In our levels, we have to actively manage the amount of crossover between paths and how often guards might meet.
    In the first test pass for Murky Station I ended up with a good amount of coverage for my level, but the downside was that some sections could randomly get 8 guards piled up.  After a bit of playtesting and redesign, I decided to break up my patrols into smaller loops and add more points. This increased the amount of coverage and kept the patrols more consistent. It also lowered the maximum guard stacking to around 4 and drastically reduced the amount of death chain reactions that could happen.

    First pass patrol locations

    Second pass patrol locations

    (the new paths provide the same amount of level coverage with a less chance of guard over-stacking) 
    A fresh take on an old mechanic
    In most of our stealth levels we use random static security cameras to challenge the players’ skill at avoidance or sabotage. The players have multiple mechanics in order to deal with them in a variety of ways, but we hit a brick wall when discussing options for Murky Station. Due to the hallway nature of the layout and the surrounding structures, we were left with very few options when it came to camera placement. With so few options, the cameras would be no longer modifying the level in a positive way. We also found them at odds with the design of the level, since you were supposed to be searching for a specific train car. If we had cameras pointing at it, you would be able to identify it too quickly and negate the challenge of finding it.

     
    So how did we fix these issues? Getting rid of the cameras was not really an option, so we began brainstorming and looking for assets that might be of use. It's important the core camera functionality remain intact and also continue to meet our core pillar of randomization. We discovered an old drone asset for one of the previous levels and began prototyping a few ideas. The design we ended up going with provided us the coverage we needed, while also creating a new challenge for the players to overcome.


     
    Each train can spawn up to two drones, which will then fly around the perimeter of the train and scan for players and bodies. Randomly throughout the level, three to four drones will be activated to begin their scan. The loop takes about 30 seconds before they return to their trains and deactivate. The cycle continues like this every few minutes until the level is finished.
    On harder difficulties, more drones will spawn and they will become indestructible.
    What's great about the drones from a design perspective, is that we can dynamically modify how the level gets played and prevent players from getting comfortable in using the same routes each play-through. Some players will avoid lanes with drones, more skilled players will dodge them using their movement options, and some players might even get trapped and need to think of a new routes. Let's take a look at the patrols and drones in action.
    (This clip is sped up about 8x and set to the hardest difficulty to help illustrate pathing and drone movement)
    Closing thoughts
    Murky Station was such an enjoyable experience to work on that I still play it to this day. When you break down the objectives and how they influence one another in a co-op space, you can begin to see the bigger picture and how a well-planned level with controlled RNG elements can stay fresh and replayable. Experimenting with different types of RNG is something I find very interesting, especially when you combine it with level design. I hope my article gave you some more insight into how we build with RNG and why we consider it one of our core design pillars. If you found this article helpful, let us know in the comment section!
    Thanks for reading, here is my Info :
    Twitter: @generalvivi 
    Email: generalvivi [at] gmail . com
    Website: www.generalvivi.com
    Before you go!
    If you enjoyed this article and would like to hear how we used RNG in other ways, check out Patrick Murphy's article on the Payday 2 level "Hoxton Breakout".
    I also have a  speedrun (1min) of the level for you to check out and a playthrough on the hardest difficulty (10 mins) by one of the pros from the community.  
    Fastest time 2018 (warning to lower volume)
     
    10 min gameplay video showing off a lot of variety in the heist. 
     
  • Level Design in Max Payne: Roscoe Street Station
     
    Max Payne is a third person shooter developed by Remedy Entertainment and published on July 2001. At the time of its release, the game gained critical acclaim for its use of the bullet time mechanic - a special ability that slows down time around the character. Inspired by Hong Kong action films and hard boiled detective novels, the game focuses on intense action sequences and the protagonist's internal struggle as he attempts to avenge his murdered family.
    The game's story is structured under three parts, each containing several chapters. For the purposes of this article, we will take a look at Chapter One: Roscoe Street Station, from the first part of the game, and deconstruct the level progression as well as state design decisions when encountered.
     

     
    The level begins with a cutscene of Max riding the subway train towards Roscoe Street Station to meet with his friend Alex. As soon as Max gets off the train, he remarks that “The station was drenched in gloom. Alex was a ghost nowhere to be seen. I’d have to look for him”. Although we aren’t given much information to work with, it’s enough to build a sense of mystery and give the player a goal.
    Taking control over the character, we discover that our main path is blocked and are forced to explore a side area where more narrative is to be revealed. As we burst open the doors of the personnel room, we stumble over the body of a transit police officer. Once again, a quick cutscene centers on Max while he delivers his lines and sets the tone accordingly: "Death was in the air at Roscoe Street. I'd have to find Alex fast." At this point, Max pulls out his pistol and we can either return to the starting area or explore the room for hidden ammunition and health. Doing the latter teaches the player that exploration is rewarded through much needed supplies.
    On our way back, we encounter our first two enemies and notice that the main path is no longer blocked. Though, If the player takes his time and waits around the corner before engaging the enemies, bits of story will be delivered by them, explaining their reason for being there or informing on the overall situation. And as trivial as that sounds, it can have a major impact on immersion and believability. Clearly this is something the developers have identified early on and implemented throughout the game. Giving the player the option to advance at his own pace goes a long way and makes for a more dynamic experience. Those who want to rush through the levels can do so. Others that want to explore and listen to bits of story can do that as well. It’s an ideal situation that satisfies both worlds.
     

     
    After our first encounter, we can proceed through the main path where we immediately find two more enemies. As previously mentioned, we have the option to directly engage in combat or wait for the enemies to reveal additional information. An important thing to make note of is that despite the fact that the gameplay space is tailored around the player’s needs, the environment always feels natural. A good example is this specific bit, where the player is now emerging from a set of stairs and can dive on his side towards a nearby mail box for cover.
    When designing a space that is supposed to represent a real life location, it's essential for the level designer to always keep in mind that everything placed in the scene must abide by the real location's logic. Of course, adding something unusual or out of place is a good way to draw the player's attention, but in general we all have expectations of what kind of objects to find in most environments. Meeting those expectations is key to creating a believable game world.
     

     
    Going down the corridor, we hear another enemy, but this time located behind an inaccessible gate. Although his placement seems odd, this set-up accomplishes two things. Firstly, it creates an audio cue to draw the player forward. Secondly, it gives the illusion that the environment is much larger than it actually is. It's a simple trick and probably one of the oldest in the level design book, one which the developers have used extensively throughout the game to their advantage. If you find yourself creating a fairly linear level, simply adding a few inaccessible areas is a quick and painless way of providing some visual depth to your environment. As in real life, there are plenty of areas that we cannot access.
    Continuing with the idea of guiding the player, we begin to notice even more ways of doing that. This time our direction is implied through arrow signs in combination with an enemy audio cue. And after encountering the said enemy we acquire a new weapon type, the pump action shotgun, as well as discover the Subway Control Room. Unable to access it, Max elaborates that “The security panel let off a mocking cackle. I’d need the right code”. Without knowing specifically why need to gain access, we can nonetheless conclude that opening the Subway Control Room is somehow tied to the level progression in some way. Turning to our immediate left, we begin to descend to a closed station.
     

     
    At this point, having also acquired the shotgun, the difficulty starts to increase as we encounter three enemies on our path. Once they have been dealt with, we find ourselves in a fairly elaborate space with two options for exploration:
    Taking the path to our right, we end up in a room designed to replenish the player’s ammunition and health. Going to the back of this room, we locate a corridor leading to a locked grate door. Even though we cannot open it, reaching the end will deliver additional information through the means of dialogue between two enemies situated on the other side. In contrast to previous encounters, this time we have the option to kill our enemies by shooting a nearby propane canister. After dealing with them, Max notes that "The gate was locked. I would need to find another way to get to the tunnel". This gives us a hint as to where we need to go in order to progress with the main goal.
    Opting for the path to our left, towards the end of the station, we locate a personnel room, a bright yellow maintenance train and a small supply room. Checking out the maintenance train, Max states that "The power to the rail had been cut. I'd have to get it back on to get the train moving". Looking to the opposite side of the train, we notice a tunnel blocked by a series of wooden boards. Putting two and two together, we must find a way to power up the maintenance train and crash though the boards to reach the level's final area. Of course, now we realize why we must gain access to the Subway Control Room. Turning our attention away from the train, we open the door to the nearby personnel room. Inside, we find a transit police officer held at gun point by an enemy. After killing the thug, the officer informs us that he can access the Subway Control Room and so we begin to backtrack. Having reached the security panel, the officer unlocks the door, but is shot dead by an enemy already on the inside.
     

     
    Reopening the door, we notice the enemy has retreated to a secondary room. Pursuing him, we encounter 3 additional thugs, totaling 4 enemies, the most we have yet to fight at once. It's important to notice that, as we advance through the level, the number of enemies we encounter at a given point increases, but in a manner that is fluid and balanced. So far, the pattern has been to include single enemy encounters between group encounters. This way, the player doesn't constantly feel overwhelmed and has time to recuperate before a larger fight. 
    After dealing with the enemies, we discover a third smaller room to the back. Inside this room there is an electric panel that controls the subway power lines, a cabinet with health supplies and a series of camera displays. Using the button on the electric panel triggers a green line to rise on it's display, giving the player visual confirmation that power is now back on for that specific line. Additionally, using the nearby camera display will show an image of the bright yellow maintenance train and compel Max to state that "The train lit up like a Christmas tree. The power was back on". 
     

     
    We then proceed to backtrack to the train. Backtracking again. Sometimes, and especially if overdone, this design decision can become tedious and potentially confuse players. However, when used sparingly in design and with a bit of logic, forcing the player to go back and fourth between parts of the level in order to progress can make the environment seem more connected as a whole. Backtracking can also prove to be a good way of making the most out of a given environment by squeezing as much gameplay as possible.
    Once we have reached the train, we can either immediately operate it or explore the area behind it for ammunition. Manning the wheel, the train begins to accelerate and shortly crashes through the wooden barricade. Advancing in the tunnel, we encounter 3 enemies and reach the area seen previously from the locked grate door. Our only path to follow now is through a rusty door leading to the next level. While we didn't accomplish our primary goal in this level, we still managed to gather information about the situation, be it directly from Max's lines or indirectly from the enemy dialogue. 
     
    Conclusion
     
    Despite it's ever growing age, Max Payne still proves to be relevant even today. Examining how the gameplay unfolds in Roscoe Street Station, we can only conclude that the people at Remedy Entertainment are without a doubt true masters of their craft. And for those passionate about designing single player levels, here are 10 principles that we can learn from them:
     
    Story is revealed in small amounts to keep the player interested for more Exploration is rewarded through useful items Inaccessible areas can give more depth to the environment Players that want to be engrossed in the game world are rewarded with additional information Environments are designed with a certain logic to meet player expectations  Players are guided through subtle visual language, audio cues or lighting and colour Progression obstacles are designed to be relevant to the story Intelligent backtracking uses the gameplay space to it's full potential and makes the environment seem more connected Interaction with the environment is reinforced through audio-visual feedback Properly balanced difficulty allows the player moments of rest and doesn't constantly overwhelm with enemies  
  • Intro
    Titanfall 2 was one of the best FPS titles of 2016, featuring a very strong single-player campaign with interesting combat and puzzle gameplay for both players and their Titan. Additionally, each level featured its own special twist: "Effect and Cause", for example, presents players with a memorable time-traveling mechanic.
    The time-travel mechanics of "Effects and Cause" serve couple of purposes, influencing not only the way players traverse the environment and its associated obstacles, but also how they fight through the level's combat scenarios. Two different time periods are a threat to the player, so the designers decided to allow players to see where the enemies from the past are located.
    Once you move from past to the present, enemies leave a small blue particle in the place where they had been standing. Although the effect lasts no longer than two seconds, it’s enough to help players plan their next move. This twist on encounters makes them much more interesting and dynamic.
     

     
    For "Effect and Cause", the developers created distinct enemies archetypes with different engagement distances and attacks for each time period. In the present (a destroyed version of the map) the player deals with robots and wildlife. In the past, players face armed guards in the facility. Eliminating the danger in one reality does not make it disappear in the other, forcing players to think constantly about their position versus the enemies in the different time frames.
    Let’s discuss three selected encounters from "Effects and Cause" in-depth to see how they work in action!
     
    Encounter 01
    The first encounter where players freely use the time-shift mechanic starts shortly after players exit a lab area. Here, enemies are located only in the past, when the facility is operating and functional. This prevents players from becoming overwhelmed with two types of enemies in two different realities within the first big encounter of the level.
     
    Layout

     
    Combat space
    This encounter is set up in two distinct spaces. The first space is a big room with a single entry point in the form of a double door opened by a panel, with combat focused at the far end of the room. The second space is a large corridor with a pocket in the middle and a security room at the end. A panel in the security room must be used in order for the player to progress.
    Both encounter spaces are divided by a time-shift puzzle, the only way to continue onto the next arena. This time-shift puzzle serves as combat gating and also adds variety to encounters that are otherwise only about shooting. The gating also teaches the player that some spaces cannot be traversed in any time period, and that the only solution to the obstacle is to find alternative routes.
     

     
    Enemies
    There are eleven enemies in this encounter: four located in the first room, and seven in the second room. Once you eliminate the two enemies in the first room, the remaining two enemies get into position. The second space has a fixed number of soldiers, with no additional waves. All the soldiers are using guns or rifles. The advantage/challenge to the player in this encounter comes from the number of the enemies, not their abilities.
     

     
    Encounter design
    Once the player enters the first space, they see two soldiers talking to each other. It’s up to player to start the fight and pick their preferred attack method. Once the first two enemies are eliminated, players enter an area with clearly defined architecture and a no-man’s-land inbetween. Players should also see a weapon lying on the desk, a gameplay "carrot" which helps to draw players into the fight. The enemies will hold their positions and try to shoot the player from behind the safety of cover.
    The second area gives players more options, and also allows them to scan the area earlier (both from the first room through the lasers, and also from a vent). The designers ramp up the difficulty here, introducing more enemies into a tighter space.
    With the time-switching mechanics at hand, players can prioritize threats in order to set up their own tactics. It’s clearly up to player how to plan and play this encounter. As there is no threat in the past timeline, players can experiment with going back in time without punishment, ‘escaping’ the combat at any given moment in order to reload, reposition and jump back to the action. This encounter is memorable as it is the first time that players fully use their time switching mechanic, functioning as a safe environment to learn. In other words, it's a skill check and a preparation for what lies ahead...
     
    Encounter 02
    The second encounter worth analysis is much more varied with how it positions enemies throughout the level. It also places enemies in both time periods, serving as a playground for prioritization strategies and other interesting player tactics. This encounter also features more verticality, which helps prevent players from feeling too overwhelmed with enemy forces, while also allowing players to use more of their Titan-piloting skills.
     
    Layout

     
    Combat space
    This encounter is located in a fairly large room with ample verticality. Players enter the space on the upper floor through a single entry point and continue their way onto a balcony, letting players familiarize themselves with the space from above. At the far end of the room, players will spot a staircase going down to the lower level where elevators are located. This area has two big areas of standing cover, accessible on both heights, and a variety of crouch-height cover such as railings, desks and potted plants. This space also has a small side-room allowing further tactical options. This whole area is gated with an elevator door which does not open until the combat encounter is over.
     

     
    Enemies
    This encounter is quite varied in terms of the enemies players face. In the past timeline, players face eleven soldiers: nine regular soldiers and two heavy soldiers with shields. These soldiers come in four groups of two or three each. The solders come with short intervals inbetween each wave, so that the player has time to react and make more intellectual choices.
    In the present, players face three robots appearing almost at once when they walk along the balcony at the top of the space. Once the player goes down, they have to fight four prowlers which appear one after another with a couple of seconds delay between each new spawn.
     

     
    Encounter design
    We start the encounter in the present timeline, with the gate blocked in the past timeline. On the way to the staircase, three enemy robots spawn but do not pose a big threat to players. Once players move down, their attention is drawn to a desk with guns. This helps players to immediately position into a location in front of the elevators.
    Once players shift to the past, enemies start to appear from the elevators. There is not enough cover to fight off all of the attackers, forcing players to prioritize and switch in time to better position themselves for attack. Once players go back into the present, prowler enemies will start to appear, forcing players to continue constant movement.
    This encounter may feel a bit hectic, but it is a good test of both pilot skills and thoughtful time switching. It's the first encounter which forces players to prioritize which enemies they want to deal with first in different time periods. Due to the designer's smart use of the elevators, vents, and robot storage, enemies are brought into the field in an interesting way. But at the same time, enemies are introduced to the player with clear sound and visual cues, so they remain alert to upcoming surprises.
     
    Encounter 03
    The third encounter I want to breakdown is by far the most robust yet. It features different height levels, space divided into two areas, and flanking paths which can be accessed only through certain time periods. It serves as the "final skill check" for all of the pilot abilities and time-shifting gathered thus far in "Effect and Cause".
     
    Layout

     
    Combat space
    This encounter is spread across two areas of vertical space, connected by multiple paths that create nice loops for players to use to their advantage. There is one clear entry point with a wide view of the whole combat space and one exit located in the second area, but the space inbetween offers a great deal of choice in terms of how players can tackle the encounter.
    Playing through the encounter, players will learn that there is a geometry difference between the two different time frames that can be overcome with some of the pilot skills at their disposal. A big catwalk goes around the whole room with additional rooms with guns and ammo on the bottom level, for example. The amount of space available is needed, because the combat space is packed with enemies.
     

     
    Enemies
    In the past, players have to fight twelve soldiers: nine regular soldiers and three heavies with shields, as well as three robots. The enemies are spread out across the whole space of the encounter, but because the areas are connected with each other through multiple paths, the enemies will try to chase and eliminate the player. This means that the encounter feels very dynamic and tense.
    In the present, players face robots: eight prowlers inside, and even more of them outside fighting with BT (the player's Titan). The enemies in the present are hostile to each other, showing players an example of how the enemy AI can actually fighting eachother: information which players can then use to their advantage.
     

     
    Encounter design
    Players enter this area in the past, where they witness a single back-facing enemy, instantly inviting them to perform a takedown. From this point, the encounter is very open to experimentation: the player can either continue in the past and fight a big wave of soldiers coming through the main path (a staircase in the middle), or they can switch to the present, where they will find open flanking paths on both sides of the level. Going with the latter option offers a moment to breathe before prowlers are spawned, but it will also disable an ammo dispenser in the first area, adding consequence to player choices.
    Staying in one place will result in a massive pile-up of enemies in the area, so players are motivated to move around a lot, time shifting when needed. The second area of this encounter is one of the level's biggest in-door combat spaces. If players choose to go into this second area in the past, the encounter will be quite vertical with soldiers located both on the ground and on the upper catwalk. Switching to the present will cause a bigger concentration of enemies on the ground floor.
    Players are given enough space to fully use pilot’s zip-line ability to create shortcuts across the room, accessing the various loops and ammo dispensers needed to create a fair fight despite overwhelming enemy forces. There are very few conditions placed upon this encounter, so players can leave the area and jump into his Titan to deal with different threats at any time. Overall, this encounter serves as a test of everything learned previously, with players having the option to ‘lower’ the difficulty of the encounter using their titan.
     

     
    Conclusion
    The above examples are just a slice of Titanfall 2 gameplay contained within the excellent level "Effects and Cause", but in my opinion clearly shows how this great game was enhanced by its time shifting mechanic. The idea is fairly simple: time-shifting is nothing more than teleportation between two different levels, one layered on top of another, but the strong execution makes for a memorable experience that really stands out in comparison with other shooters. I highly recommend playing "Effects and Cause" as it is both challenging and fun, a level where Titanfall 2's time-shift mechanics comes into focus, providing additional depth to the whole game.
     
    Thanks for reading!
  • (New logo by Yanzl)
    I'm sure that by now most of us have our sleeves rolled up and are ready to tackle yet another year, but before we move forward let's take a moment to look back at what 2017 meant for our community. It was a time of immense growth for both professionals and amateurs alike. A time when everyone seemed to have surpassed their former selves. And without slowing down, some have even managed to land their first job in the industry. I don't know what this new year holds, what challenges to overcome will arise, but I know for certain that I'm excited to see everyone become even greater!
     
    2017: Mapcore's Year in Review
     

    Overwatch - Oasis
    by Phillip K, Bram Eulaers, Helder Pinto and others
     

    Dishonored 2: Death of the Outsider - Curator level
    by electrosheep, kikette and others
     

    Payday 2 - Brooklyn Bank level
    by General Vivi
     

    Sniper Elite 4 - Regilino Viaduct
    by Beck Shaw and others
     

    Counter-Strike: Global Offensive - Offtime
    by Squad
     

    Team Fortress 2 - Shoreleave
    Art pass, props and sound by Freyja
     

    Wolfenstein II: The New Colossus - Farmhouse
    Modeled, textured and composed by BJA
     

    Half-Life 2: Downfall
    by marnamai
     

    Counter-Strike: Global Offensive - Studio
    by ZelZStorm, TanookiSuit3 and Hollandje
     

    Portal 2 - Refraction
    by Stract
     

    Counter Strike: Global Offensive - Breach
    by Yanzl and Puddy
     

    Counter-Strike: Global Offensive - Berth
    by grapen
     

    Counter-Strike: Global Offensive - Kaizen
    by Andre Valera and Jakuza
     

    Counter-Strike: Global Offensive - Asylum
    by Libertines
     

    Half-Life 2: Episode 2 - FusionVille: The Shadow over Ravensmouth
    by Klems
     

    Unreal Engine 4 scene
    by Dario Pinto
     

    Counter-Strike: Global Offensive - Grind
    by The Horse Strangler, `RZL and MaanMan
     

    Counter-Strike: Global Offensive - Aurelia remake
    by Serialmapper
     

    Counter-Strike: Global Offensive - Tangerine
    by Harry Poster
     

    Counter-Strike: Global Offensive - Abbey
    by Lizard and TheWhaleMan
     

    Counter-Strike: Global Offensive - Apollo
    by Vaya, CrTech, Vorontsov, JSadones
     

    Counter-Strike: Global Offensive - Sirius
    by El Exodus
     

    Unreal Engine 4 scene
    by Corvus
     

    Counter-Strike: Global Offensive - Subzero
    by FMPONE
     

    Counter-Strike: Global Offensive - Biome
    by jd40
  • This article may contain slight spoilers   DOOM's Argent Tower is a superb Single-Player level. The Argent Tower motivates players with an obvious goal, expands in scope (almost unbelievably), and masterfully controls pacing. A playground for new a ability and a giant environmental puzzle, the Argent Tower is the best level in this excellent reboot of the franchise.   Now, let's explore the reasons why this level feels so memorable!   OBJECTIVE   Players will know their goal from the outset: climbing the Argent Tower. In addition to verbal instructions, the level's construction and composition never fails to aim you upward. Warm lighting moves up vertically, so that players' eyes are always drawn upwards.     Even the item you acquire in the level's prelude is a double-jump upgrade, which the level then associates with an oft-repeated green light motif. Players will be doing a LOT of double-jumping in the Tower, so the game articulates a method to guide them.     While players may or may not consciously respond to this green-light motif, the designers clearly believe it works as a navigational aid: it is repeated with brutal consistency throughout the level.   SCOPE   When players reach the Tower's inner core, the vast power of DOOM's engine is indisputable. Great music kicks in, monsters spawn all around the player, and the game "gates" engagements without muddying players' central, long-term gameplay goal.     The symmetrical, circular design of the Tower's core proves extremely useful in several respects. Because players can only progress upwards, they get to experience fun combat engagements and jumping puzzles before they are neatly stuffed into small corridors adjoining the main core.   This contrast between the core's verticality and its cramped side passages makes for easily controlled progression through the level and amplifies the awe of returning to the core. In one side area of the Argent Tower, players experience a "monster closet" ambush, a classic DOOM design trope in which a demon emerges from a closet adjacent to a corridor. Here, the designers chose an exploding demon for extra "oomph"!     There's just something timeless about monster closets. That the game dives down to its most granular level (the monster closet) additionally provides contrast to the heights of the massive core.      PACING   DOOM carefully reminds players of their progress ascending the Tower. In one cramped side-area, players are faced with the seemingly trivial task of shooting canisters that underpin an elevator blocking their path. After destroying the canisters, the elevator falls down its shaft.      Half-Life 2 used similar imagery to convey the scale (and ongoing destruction) of The Citadel:     An additional point of this elevator diversion was to slow players down, to keep them away from the showpiece core a little while longer.    New players will take a minute to identify the canisters overhead and discern that they need to be destroyed, because this is a novel task and because FPS players notoriously fail to look upward. Later in the game, the designers repeat the canister mechanic before providing players the BFG, the defining weapon of the series. Without the subtle change in momentum the canisters provide, gaining access to the Tower's rooftop or the BFG would feel too straightforward and simplistic.    Having artificially lengthened the break players take from the core, the designers have guaranteed that environmental contrast will enhance perception of the Tower's scale AND that player intelligence and momentum has been challenged by a new problem. (...but because this is DOOM, problem solving is still ultimately about destroying shit.)     Players complete more than six different jumping tasks including riding a flying drone to climb the Argent Tower and enter a portal into Hell.      Such a variety of jumping puzzles and hazards makes the level memorable and is another technique enlarging perception of the Tower. To be clear, jumping puzzles are universally terrible in every FPS game, but their annoyance here is dulled by the focused grandiosity of the level and the ability to grapple onto ledges. The designers ultimately cared a lot more about giving players a memorable locale than sparing them falling deaths.   CONCLUSION   After reaching the top of the Argent Tower, players are greeted by a giant, climactic battle which ends with a wonderful fade to white.   Only now are players ready to enter Hell confident that they've truly gotten to experience Mars.      It's important to remember that, fundamentally, the Argent Tower is about going from point A (the foot of the tower) to point B (the top). Faced with a similar Tower-landmark, some designers might path this route with nothing more than a simple elevator cinematic or miss countless opportunities to do something special. DOOM's designers, however, missed nothing: they recognized the need to offer players dense and varied challenges, careful pacing, and spatial design rich with contrast.   Later, when players return to Mars, the destroyed husk of the Tower provides an instantly recognizable landmark re-orienting players on their adventure and a tantalizing hint that things are different now.   The Argent Tower goes to show that great levels are not about the destination, but the journey -- and all the controlled chaos along the way!     Thanks for reading!    
  • The following article contains quotes from interviews with Todd Papy, Design Director at Cloud Imperium Games, Geoffrey Smith, Lead Game Designer at Respawn Entertainment, Paul Haynes, Lead Level Designer at Deep Silver Dambuster Studios and Sten Huebler, Senior Level Designer at The Coalition. A big heartfelt 'thank you' goes out to these guys who took the time out of their busy schedules to answer my questions!
    On the MapCore.org forums many amateur level designers ask for feedback on their portfolios or for advice on how to break into the games industry. But once you have signed your first contract and you have your foot in the door you will realize that this step marks merely the beginning of your journey. It is a winding path with many diverging branches and without much information available on the road ahead. This is the reason why I decided to interview professional designers in Senior, Lead or Director positions to share their personal experiences and advice with others trying to navigate this field. It is worth mentioning that the questions were not selected and phrased with the goal in mind to compile a ‘how to get promoted fast’ guide. Instead I wanted to give level designers insights into the careers of others - who have stood at the same crossroads before - in hopes that they get the information to pick the path that is right for them.
    Hands-On VS Management
    At the beginning of his career, Todd Papy started out as a “designer/environment artist” – a job title that dates back to times when team sizes were much smaller and one person could wear both hats at the same time. As the project complexity and team size grew, he specialized in level design at SONY Santa Monica and worked on the God of War titles. During his time there he moved up the ranks to Lead Level Designer, Design Director and eventually Game Director. From level design to directing a game - a career thanks to careful long-term planning and preparation? “It wasn’t even on my radar” says Todd. “I just wanted to build a game with the team and soak up as much information from the people around me as possible.” 
    So how do level designers feel who step into positions where the majority of their daily work suddenly consists of managing people and processes? Do they regret not doing enough hands-on-work anymore? Todd says he misses building and crafting something with his hands, but instead of going back to his roots, he decided to look at the issue from a fresh perspective: “As a Lead or Director, your personal daily and weekly satisfaction changes from pride in what you accomplished to pride in what the team has accomplished.“ Today Todd is designing the universe of 'Star Citizen' as Design Director at Cloud Imperium Games.
    Geoffrey Smith - who created some of the most popular multiplayer maps in the Call of Duty and Titanfall series and who is now Lead of the ‘Multiplayer Geometry’ team at Respawn Entertainment - says his output of levels remains unchanged thus far, but he can “easily see how being so tied up with managing would cut into someone's hands-on work”. Geoffrey calls for companies to provide the necessary training to employees new to management positions: “Managing people and projects is hard work and is normally a vastly different skill set than most of us in games have. Maybe that is why our industry has such problems with meeting deadlines and shipping bug-free games. A lot of guys work for a long time in their respective disciplines and after many years they get moved into a lead position. They certainly know their craft well enough to teach new guys but managing those guys and scheduling would be something brand new to them. Companies need to understand this and get them the training they need to be successful.” At Respawn Entertainment, the studio provides its department leads with training seminars, which helps the staff immensely, according to Geoffrey.
    Sten Huebler, currently working as a Senior Level Designer at Microsoft-owned The Coalition, in Vancouver, says he definitely missed the hands-on work when he worked in a Lead capacity on 'Crysis' and 'Crysis 2': “I was longing for a more direct creative outlet again. That is why coming to The Coalition and working on Gears of War 4, I really wanted to be hands on again.” To Sten it was the right move because he enjoyed working directly on many of the levels in the game’s campaign and could then experience his fruit of labour with others close to him: "After Gears 4 shipped, playing through the campaign, through my levels with my brother in co-op was a blast and a highlight of my career. He actually still lives in Germany. Being able to reconnect with him, on the other side of globe, playing a game together I worked on...So cool!"

    'Gears of War 4'  developed by The Coaliation and published by Microsoft Studios
    Paul Haynes, Lead Level Designer at Deep Silver Dambuster Studios, encourages designers to negotiate the amount of organizational tasks and hands-on work before being promoted into a position that makes you unhappy: “I always told myself that I wouldn’t take a Lead position unless it could be agreed that I retain some hands-on, creative responsibility, after all that’s where I consider my strongest attributes to lie. I agreed to both Lead positions (Cinematic/Level Design) under that principle - I never understood the concept of promoting someone who is good at a certain thing into a position where they potentially don’t get to do that thing anymore, as they spend all their time organising others to do it. So far I’ve managed to maintain that creativity to some degree, though I would imagine it’s never going to be quite the same as it used to be, as I do have a team to manage now. On the flip side though, being able to control and co-ordinate the level design vision for a project and having a team to support in fulfilling that is quite an exciting new experience for me, so not all the organisation and planning is unenjoyable.”
    Specialization VS Broadening Skillsets
    For the level designers who aren’t afraid of management-related tasks and who are willing to give up hands-on work for bigger creative control, what would the interviewees recommend: specialize and strengthen abilities as an expert in level design further or broaden one’s skillset (e.g. getting into system design, writing etc.)? Paul believes it doesn’t necessarily have to be one or the other: “I think it’s possible to do both (strengthening abilities and broadening skillsets) simultaneously, it would really depend on the individual involved. I would say that a good approach would be to start with the specialisation in your chosen field and then once you feel more comfortable with your day to day work under that specialisation, take on work that utilises different skillsets and experiment to see if you find anything else you enjoy.” He started out as a pure level designer but subsequently held roles that involved game and cinematic design at Codemasters, Crytek and Dambuster Studios. “I’ll always consider myself a level designer at heart”, says Paul, “though it’s been incredibly beneficial for me to gain an understanding of multiple other disciplines, as not only has it widened my personal skillset but it has enabled me to understand what those disciplines have to consider during their day to day job roles, and it has helped me to strengthen the bond with those departments and my level design department as a result.” This advice is echoed by Todd who encourages level designers to learn about the different disciplines as “that knowledge will help solve issues that arise when creating a level.”

    'Homefront: The Revolution' developed by Dambuster Studios and published by Deep Silver
    Sten also gained experience in related disciplines but ultimately decided to return to his passion and do level design. He explains: “It’s a good question and I feel I have been wondering about this myself regularly in my career. I think those priorities might change depending on your current situation, your age, your family situation, but also depending on the experience you gain in your particular field. (…) In my career, I was fortunate enough to try out different positions. For example, I was a Level Designer on Far Cry (PC), Lead Level Designer on Crysis 1 and Lead Game Designer on Crysis 2. Each position had different requirements and responsibilities. As a Lead Level Designer I was more exposed to the overall campaign planning and narrative for it, while on Crysis 2 I was more involved in the system design. However, my true passion is really on the level design side. I love creating places and spaces, taking the player on a cool adventure in a setting I am crafting. My skills and talents also seem to be best aligned on the level design side. I love the combination of art, design, scripting and storytelling that all come together when making levels for 1st or 3rd person games.”
    Picking The Right Studio
    As you can certainly tell by now, all of the interviewees have already made stops at different studios throughout their career. So each one of them has been in the situation of contemplating whether to pass on an offer or put down their signature on the dotted line. This brings up the question what makes them choose one development studio over the other? To Geoffrey it depends on what stage of your career you are in. “If you're trying to just get into the industry for the first time, then cast your net wide and apply to a lot of places. However, ideally, someone should pick a studio that makes the types of games they love to play. Being happy and motivated to work every day is a powerful thing.”
    This is a sentiment that is shared by all interviewees: the project and team are important aspects, but as they have advanced in their career other external factors have come into play: “It’s not just about me anymore, so the location, the city we are going to live in are equally important.” Sten says.
    Paul is also cautious of moving across the globe for a new gig. “The type of games that the company produces and the potential quality of them is obviously quite important – as is the team that I’d be working with and their pedigree.  More and more over the years though it’s become equally important to me to find that balance between work and life outside of it. Working on games and translating your hobby into a career is awesome, but it’s all for nothing if you can’t live the life you want around it.”
    And it is not just about enjoying your leisure time with family and friends, but it will also reflect in your work according to Todd: “If my family is happy and enjoys where we live, it makes it a lot easier for me to concentrate on work.” He also makes another important point to consider if you are inclined to join a different studio solely based on the current project they are working on: “The culture of the studio is extremely important. I consider how the team and management work together, the vibe when walking around the studio, and the desk where I will sit. Projects will come and go, but the culture of the studio will be something that you deal with every day.”

    'Star Citizen' developed and published by Cloud Imperium Games; screenshot by Petri Levälahti
    But it goes the other way around, too: When it comes to staffing up a team of level designers, these are the things that Todd looks for in a candidate: “First and foremost, I look for level designers that can take a level through all of the different stages of development: idea generation, 2D layouts, 3D layouts, idea prototyping, scripting, tuning, and final hardening of the level. People that can think quickly about different ideas and their possible positive and negative impacts.  They shouldn’t get too married to one idea, but if they feel strongly enough about that specific idea they will fight for it. People that approach problems differently than I do. I want people that think differently to help round out possible weaknesses that the team might have.  People who will look for the simplest and clearest solution vs. trying to always add more and more complexity.“
    For lead positions, it goes to show yet again how important a designer's professional network is, as Todd for example only considers people that he already knows: “I try to promote designers to leads who are already on the team and have proven themselves. When I am building a new team, I hire people who I have had a personal working relationship before. Hiring people I have never worked with for such positions is simply too risky.”
    Ups & Downs
    While the career paths of the designers I interviewed seem pretty straightforward in retrospect, it is important to note that their journeys had their ups and downs as well. For instance Geoffrey recalls a very nerve-wracking time during his career when he decided to leave Infinity Ward: “We had worked so hard to make Call of Duty a household name but every day more and more of our friends were leaving. At a certain point it just wasn't the same company because the bulk of the people had left. The choice to leave or stay was even giving me heart palpitations. (…) After I left Infinity Ward, I started working at Respawn Entertainment and by work I mean - sitting in a big circle of chairs with not a stick of other furniture in the office - trying to figure out what to do as a company.” But he also remembers many joyful memories throughout his career: Little things like opening up the map file of multiplayer classic ‘mp_carentan’ for the first time or strangers on the street expressing their love in a game he had worked on. To him, shipping a game is a very joyful experience by itself and the recently released Titanfall 2 takes a special place for him. “The first Titanfall was a great game but we had so many issues going on behind the scenes it felt like we weren't able to make the best game we were capable of. (…) After all the trials and tribulations of starting a new game company, Titanfall 2 is a game I am very proud to have worked on.”

    'Titanfall 2' developed by Respawn Entertainment and published by Electronic Arts
    As a response to the question of what some of the bigger surprises (good or bad) in his career have been thus far, Paul talks about the unexpected benefits of walking through fire during a project’s development and the lessons he learnt from that: “It surprised me how positively I ended up viewing the outcome of the last project I worked on (Homefront: The Revolution). I’d always thought I would aim to work on big, successful titles only, but I guess you don’t really know what’s going to be a success until it’s released. Obviously it was a disappointing process to be part of, and a lot of hard work and effort went into making it, despite the team always knowing that there were some deep lying flaws in the game that weren’t going to be ironed out. We managed to ride the storm of the Crytek financial issues in 2014, coming out on the other side with a mostly new team in place and yet we carried on regardless and managed to actually ship something at the end of it, which is an achievement in itself. I see the positives in the experience as being the lessons I learnt about what can go wrong in games production which stands me in good stead should I decide to take a more authoritative role somewhere down the line. Sometimes the best way to learn is through failure, and I don’t believe I’d be as well rounded as a developer without having experienced what I did on that project.”
    Last Words Of Advice
    At the end I asked the veterans if they had any pieces of advice they would like to share with less experienced designers. To finish this article I will quote these in unabbreviated form below:
    Geoffrey: “I guess the biggest thing for guys coming from community mapping is figuring out if you want to be an Environment Artist or a Geo-based Designer and if you want to work on Single-Player or Multiplayer. Each has its own skills to learn. I think a lot of guys get into mapping for the visual side of things but some companies have the environment artists handle the bulk of that work. So figuring out if making the level look great is more enjoyable to you or thinking it up and laying it out is, will help determine which career you should follow. Other than that, just work hard and always look to improve!”
    Todd: “BUILD, BUILD, BUILD.  Have people play it, find out what they liked about it and what they didn’t.  Build up a thick skin; people will not always like your ideas or levels. Try out new ideas constantly. What you think looks good on paper doesn’t always translate to 3D.  Analyse other games, movies, books, art, etc. Discover what makes an idea or piece of art appeal to you and how you can use that in your craft.”
    Paul: “The games industry is not your regular nine to five job, and everyone is different so it’s difficult to lay down precise markers for success. Different specialisations have different requirements and you can find your choices leading to different routes than your fellow team members. You need to make sure you carve your own path and try everything you can to achieve whatever your personal goals are within the role; success will come naturally as a result of that. You need to be honest with yourself and others, open to criticism and willing to accept change. I’ve seen potential in people over the years hindered by stubbornness, succeeding in the games industry is all about learning and constantly adapting. Also it’s important to keep seeing your work as an extension of a hobby, rather than a job. The moment it starts to feel like a means to an end, you need to change things up to get that passion back.”
    Sten: “I always feel people should follow their passion. I firmly believe that people will always be the best, the most successful at something they love. Of course, it is a job and it pays your bills, but it’s also going to be something you are going to do for gazillions hours in your life, so better pick something you like doing.”
    Written by Friedrich Bode for mapcore.org
    What are your personal experiences? Do you agree with the statements made by the interviewees? Any advice you would like to share with fellow level designers or game developers in general? Let us know in the comments!
  • Payday 2 is a cooperative first person shooter where players band together to commit various crimes in the endless pursuit of wealth, infamy and cool masks to cover their criminal faces with. The game recently celebrated it’s third birthday, yet it still retains a steady player base. How then has the game kept players engaged throughout the years? The many and regular content updates are surely a big part of it. Another draw must be the fleshed out progression systems that offer tons of customization. I would argue that the lifeblood of the game is its dynamic level design; it is what keeps the game replayable and fun. In this article I will discuss what dynamic level design is and how it was used to build “Hoxton Breakout”, one of the game’s most popular missions.
     

    Payday 2, Left 4 Dead 2 and even XCOM2 all use some form of dynamic level design.
     
    What is dynamic level design?
    Dynamic level design is all about creating levels that are as replayable as possible; it is about retaining the challenge and keeping players on their toes. This is achieved by introducing elements that change between playthroughs, things that make the level a bit different each time you play. Dynamic levels are still designed and built by hand, so to speak, which makes them different from procedural levels which are created from automated algorithms.
      Dynamic levels are useful in games where the developer wants the levels to provide more gameplay than a single playthrough would. This approach has the added benefit of allowing different players to come together and enjoy the same level, irrespective of whether they have played it many times before or not at all. This can make dynamic level design ideal for co-op games and it can be essential for retaining players over longer periods of time, just like Payday 2 has done.
    Building a dynamic level
    The process of building a dynamic level certainly differs from more traditional single player level design. Instead of crafting a linear experience in meticulous detail, a designer must seek to create a broader structure of what will happen in the level and then design dynamic elements, things that change between playthroughs, within that structure. These dynamic elements need to be designed with care, so that the level actually changes in meaningful ways between playthroughs. The process of making a dynamic level will vary from game to game; it all depends on the game's mechanics, setting and other details. By sharing the design of a Payday 2 level I hope to illustrate what a dynamic level can look like and also showcase the overall possibilities of dynamic level design.
     
     

    Hoxton in all his glory, featured here in this promotional art. Shortly after his breakout, he leads a daring break-in at the FBI to uncover who ratted him out.
    Hoxton Breakout
    In the Payday 2 mission “Hoxton Breakout” players are tasked with breaking their old heisting comrade Hoxton out of custody. During the breakout Hoxton shares his suspicion that his capture was caused by an unknown snitch. To uncover the truth, the PAYDAY gang set their sights on the headquarters of the Federal Bureau of Intervention (not to be confused with any real life organization...). This sets the stage for the mission’s second level and the one I will be discussing here.
     
    Level Structure
    In this level, the players will enter the FBI headquarters together with Hoxton (an NPC). They will fight their way to the “Operations Room”; the place where the FBI servers are kept and where the Payday gang is hoping to find the information which reveals the identity of the snitch. Hoxton will search through the servers and when he has found what they need, the gang will escape. No matter how many times you play the level, the overall structure will stay the same. Instead, it’s the dynamic elements within this structure that change and make it replayable. What are those, you ask? Let’s take a look!
     

    Clockwise from top right: The FBI HQ lobby, a central area in the level. The FBI director hides behind his desk. Hoxton and the Payday gang enter the lobby.
    The Operations Room
    Players will spend a lot of time in the FBI Operations Room. Hoxton will be hard at work searching through the servers, leaving players to defend him from relentless police assaults. The combat space will change in a number of ways between playthroughs.
      Entrances - Most of the entrances to the Operations room are selected dynamically in various combinations, which changes which choke points the player must defend.
    Windows - The ‘Operations’ room is two floors in height and the second-floor windows overlooking the room are placed in different positions. Players must watch them for enemy fire.
    Fuse box - The fuse box, which enemies use to cut the power to the servers and pause your progress, can be placed in a few different positions. Players must defend it.
    Ceiling breaches - SWAT troops can breach the ceiling of the ‘Operations’ room and rappel down right into the thick of it! There are a few places where this can happen (it doesn't always).
      These dynamic elements will vary and change independently. This can be very desirable, as it will give you a large set of different combinations and improve the replayability of the level. For example, even if the fuse box is in the same location in two separate playthroughs, the positioning of the entrances and windows will change how the players approach the situation, which will help reduce level fatigue.
     

    The Operations Room. The Servers are kept in the room under the illuminated FBI logo. 
    The Quests
    There are four servers Hoxton must search through in the Operations Room. Between the searching of each server, Hoxton will need the player's assistance and send them on a “quest”. There are five different quests, though only three are selected and used in each playthrough. They can be selected in any order and combination. Each quest and its gameplay have been designed to have a slightly different flavor.
      Security Office - The next server happens to be heavily encrypted. You need to break into the Security Office, download the encryption keys and get them back to Hoxton.
    IT Department - The next server is missing and the log states it was taken to the IT Department for maintenance. You must locate the IT Department, find the missing server and bring it back to Hoxton.
    Archives - Hoxton finds a reference to some physical files kept in the archives. You need to go down to the basement, search through the archives and bring the paper files to Hoxton.
    Forensics - Hoxton learns that the FBI has evidence related to the traitor. Players need to break into the evidence locker, find the right piece of evidence and then scan it in the nearby laboratory for clues before returning to Hoxton.
    Director’s Office - Hoxton encounters some files on the next server that can only be accessed by gaining direct approval from the FBI Director. You must head to the director’s office and use his computer to approve all of Hoxton’s security clearance requests.
      What this means is that players won’t know exactly which “quests” they will tackle each time they play the mission, or in which order they will face them. As the difficulty slowly ramps up during the mission and the players’ supplies generally are lower towards the end, completing the same quest as either your first or last one can become quite a different experience, even though the quest itself doesn’t change that much. Allowing the quests to be arranged in any order and combination simply gives the mission a slightly different flow each time.
     

    The five quests, clockwise from top right: IT Department, Security Office, Archives, Forensics. Center: Director's Office
    The Combat Now, it’s about time we talked about the combat. It is essential for the replayability of a level that the combat isn’t static and that encounters vary between playthroughs. To solve this, Payday 2 has a spawning system that serves up dynamic enemy encounters. The system unburdens individual level designers and creates a consistent and tweakable way for the game to spawn enemies in all levels. For those of you who have played the Left 4 Dead games this may sound very familiar. The system isn’t completely automated and the level designer can control a few variables.
      Difficulty - The player selects the overall difficulty of a level before starting, but a designer can tweak the difficulty to a factor between 0 and 1. This can be adjusted at any point during the mission and can be tied to certain events.
    Spawn locations - A designer designates spawn locations manually. The designer can toggle spawn locations on and off, change how often they can be used to spawn enemies and which kind of enemies are allowed to spawn from them.
    Enemy Wave Mode - Police assaults occur regularly and this is generally handled by the system, but a designer can force a police assault or a complete break from them.
    Snipers/Harassers - The placement of snipers and so called harassers, regular SWAT troops who harass players from vantage points, is done manually. It is up to the designer to place them in challenging, but fair, positions and script logic which decides when and if they appear.
      What this all means is that while the spawning system does the heavy lifting and creates varied combat encounters, a designer can fine-tune the experience and still direct the combat somewhat. For example, in Hoxton Breakout the difficulty is slowly ramped up after each completed server, the spawn locations are continuously tweaked throughout the mission to make fights fair and when it is time to escape an endless police assault is forcefully triggered to increase the stakes!


    A dynamically spawned enemy squad moves towards the Payday gang.
    The keycard economy
    In Payday 2, keycards are single-use items that are occasionally used to open certain doors. In order to add depth and strategy to the level, I added something to this level which I like to call “the keycard economy”. In every playthrough, players can find 3-4 keycards which can be used, i.e. “spent”, on a variety of options like overriding doors to seal them off from enemies, unlocking rooms that contain precious resources or opening doors that lead to objectives. The value of the different options can change between playthroughs, depending on dynamic variables and which loadouts the players have. Since players can’t have all the options, they must choose wisely. This allows players to refine their strategy over the course of multiple playthroughs, adding to the level’s replayability.
      The little things We’ve discussed all the major dynamic elements of the level at this point, but it is worth mentioning that replayability also arises from smaller dynamic elements too. These smaller surprises can throw players off and force them to adapt accordingly. A good example can be found in the Security Office, where the police sometimes pumps in tear gas when players are trying to complete the objective inside. This forces players to leave the relative safety of the room and charge head first into the police forces which are surely waiting outside. Part of making a dynamic level should be to identify and implement these little game changers!
     

    Clockwise from top right: The Security Room fills with gas. A keycard has been used to seal a security door. An innocent keycard. A SWAT team rushing to thwart the payday gang.
    Discussion
    To summarize, the level we’ve looked at is about defending a location and completing short “quests”, with both activities changing in different ways between playthroughs. In addition to this variety, enemies are dynamically spawned, occasional surprises appear and players are able to learn and master the keycard economy over the course of multiple playthroughs. These dynamic elements, this variety between playthroughs, is what turns the level into a dynamic one.
      This level was made for Payday 2 and, as mentioned, dynamic levels will look a bit different depending on the game and its needs. The Left 4 Dead games have less emphasis on objectives and focus more on linear progression through a level, with dynamic enemies, items and minor path changes along the way. The Killing Floor games have arena levels that suit the game’s wave-based horde mode and these levels feature fairly simple dynamic elements: enemy and item spawning as well as the location of the weapon and item shop. The revived XCOM franchise uses levels which have designated areas or “slots” where different buildings and structures can fit in and shift the layout accordingly. The XCOM games also allow different missions to be played on the same level, enabling levels to provide even more gameplay mileage.
      The dynamic level design approach may fit these games, and others like them, but it is not suitable for all kinds of games and it definitely comes at a price. Since dynamic levels are designed to be replayable, heavily scripted story moments and set pieces may have to be deemphasized or removed outright. Playing through such sections may be thrilling once or twice, but they generally lose their appeal very quickly. Furthermore, some degree of polish is generally lost in the process of making dynamic levels. The fact that you are making an experience that can’t just happen “in one way” means you can’t necessarily polish, and control, every moment of gameplay to an insane standard, like you would expect in an Uncharted game for example. Additionally, an incredibly strong core gameplay loop is almost a requirement for a game with dynamic level design. Since the levels can’t be overly scripted, directed and set-piece heavy, the levels can’t compensate and “lift up” a slightly weaker core gameplay. Finally, one must also consider that creating dynamic elements in a level takes time, time which could be spent polishing or making more non-dynamic levels.
      These drawbacks must be weighed against the potential benefits. After all, the value of replayability should not be underestimated. As I mentioned in the beginning of the article, dynamic levels seem to be almost ideal for co-op games. Playing games together definitely adds something to the experience and this can help to compensate for some of the potential drawbacks like the lack of set-pieces. Adversarial multiplayer games, i.e. player vs player, don’t necessarily stand much to gain with the dynamic level design approach as the element of human unpredictability and challenge is usually enough to keep players engaged and entertained. By looking at XCOM, we can see that dynamic levels can be used to great effect in a game that isn't a shooter nor a cooperative one. And if we compare them to procedural levels, dynamic levels requires less sophisticated technology to create, but more human labor, and can offer something that feels a bit more handcrafted and unique. Ultimately, game makers need to look at the dynamic level design approach, its pros and cons, and ask themselves: is it the right approach for us?
  • An open map?
    Source engine, which is funnily a Quake engine on steroids (a bit of exaggeration but still), inherited the same limitations of its parents in terms of visibility calculations: BSP and PVS. This fact makes Source, as was Quake engine before, more suitable to rooms and hallways separated by portals where the BSP shines in all its glory.
    Inheritably, Source does not like large open maps where the PVS is of considerable size and the over-rendering is a real issue.
    If you work with Source engine, then you already know the importance of optimization in a large, detailed map. Optimization becomes even more imperative when the said map is open.
    What’s an open map? Good question. The word “open” is an umbrella term to denote any map that does not have traditional hallways and corridors that connect indoors to outdoors. The map is mostly large, outdoors with an unbroken skyline; in other words, the same stuff that source engine nightmares are made of in terms of PVS and BSP.
    In a traditional “hallway’d” map with twisted corridors leading to open areas followed by other hallways, and even if you “forgot” to place hints and areaportals, the geometry itself allows the engine to cut visleaves and limit visibility; granted the visleaves’ cuts will be subpar and messy and the PVS will be in excess, but still, the visibility and fps will be relatively under control. A twisted hallway is a remedy to long sight lines after all.
    In an open map, and without hallways and enough geometry to help the engine, the PVS risks to be huge and the whole map could be rendered at once from any point (over-rendering). We are talking here about a severe fps killer and a potential slideshow on a medium to low range computer. Source does not like over-rendering; I repeat, Source does not like over-rendering.
    I believe a screenshot should be welcome at this stage to illustrate an open map. I’ve chosen a nice medium-size map from CSGO to showcase the issue: de_stmarc.

    The shot is taken in Hammer obviously, and you can immediately see that the skybox is one big unbroken body from one edge of the map to the opposite one. This is the classic definition of open map.
    Let’s see this map in 2D view from the side.

    I have highlighted the skybox in blue so you could see the continuous sky body all over the map. Please note that an open map can have varying skybox shapes but I’ve chosen the simple and classic one to showcase my point where it is easier to see and visualize the concept of open map.
    In contrast, a “traditional” map will have several skyboxes, often not connected directly but rather through a system of indoor rooms or hallways, varying in size and shape.
    I will have my map de_forlorn as example here.

    I have also highlighted the skybox in blue and you can easily notice several skyboxes for CT spawn, T spawn, and Mid/bombsites. These skyboxes are not directly connected to each other but the areas related to them are linked on the lower levels through various indoor locations, some vast (like garage, tunnels…) and some small (like lab hallway…).
    If you are not that comfortable with source optimization or feel that certain terms are alien to you, then please read my previous optimization papers and articles before proceeding further in this article (Previous papers can be found here Source Engine Optimization roadmap).
    The necessary tools
    I’m not revealing a secret when I tell you that the same tools used to optimize any map in Source are exactly the same ones used for optimizing an open map. If you were expecting some magical additional tools, I’m sorry to bust your bubble.
    Since the tools are the same (nodraw, func_detail, props, hints, areaportals, occluders…), it is more about how to use them in open maps that makes all the difference.
    So, how to properly optimize an open map? Well, you could always pay me to do so for you (joking…not…maybe…I dunno!!)
    If the above option is off the table, then read on the rest of this article .
    Horizontal hints
    While in a traditional map one might get away without using horizontal hints, it is virtually impossible to skip them (pun intended) in an open map unless you want to witness single digit fps burning your eyes on the screen. They are of utmost importance to negate the "tall visleaves across the map" issue.
    In a traditional map, even if you bypass adding horizontal hints, the damage in fps will mostly be local since the skyboxes are not connected and areas are mostly autonomous in terms of PVS. In case of my map “Forlorn” and referring to the 2D diagram above, if I remove horizontal hints from CT spawn, then only this area will suffer from tall visleaves and over-rendering. Obviously, this is not cool in terms of optimization, but at least the effect will be somehow restricted to this area only.
    In the case of “Stmarc”, you can certainly see that not including horizontal hints will have tall visleaves seen from across the map as the skybox is one unit. The PVS will grow exponentially and the over-rendering will take its toll on the engine.
    Let’s move on to some screenshots and diagrams, shall we.

    This is our glorious open map in side view. The blue lines denote the skybox, the dark grey one is the ground, and the green rectangles represent solid regular world brushes such as building bases for example. The red starfish little-man-with-arms-wide-open is the player. The orange hollow rectangles denote the various visleaves that the engine would probably create in the map (most go from ground level to skybox level and this is what I refer to as “tall visleaf”).
    If you know your optimization, then you certainly remember that BSP relies on “visibility from a region” approach (for a refresher, please consult my papers Demystifying Source Engine Visleaves and Source Engine PVS - A Closer Look. This simply translates to the following: the player is in visleaf A and visleaf A has direct line of sight to visleaves B, C, D, E, F, and G. The PVS for A in this case would be stored as BCDEFG. Once the engine recognizes that the player is in A, and regardless of the exact position in A, it will proceed to render the whole PVS content. Everything in visleaves BCDEFG will be rendered even though the player is at the extreme end of A and has no line of sight to most of this content.
    You can immediately notice the extent of damage you will inflict on your open map if you neglect adding horizontal hints: excess PVS with additional useless content to be rendered at all times.
    Now that we established the importance of these horizontal hints in open maps, the question remains: where shall I put these hints?
    In the diagram above, the most logical places would be on top of the 3 green rectangles.

    We added 3 horizontal hints (H1, H2, H3) on top of the 3 regular brushes in our map (the hint face neatly resting on the top of the regular brush while other faces are textured with “skip”). This will create more visleaves as can be clearly seen in the above diagram, and vvis will take more time to calculate visibility due to the increased number of leaves and portals but this is done for the greater good of humanity your map’s fps.
    Now the player is in visleaf A1 and the PVS is reduced to (sit tight in your chair) A2, A3, A4, B1, B2, C3, C4, D1, E4, F3. On top of the nice result of a greatly reduced PVS (and therefore content to render), keep in mind that leaves A4, B2, C4, D1, E4, and F3 are mostly empty since they are way up touching the skybox.
    Some folks will start complaining and whining: what the hell dude, I don’t have 3 green rectangles in my map; where would I put my hints?? My answer would be: deal with it!!
    Joking aside, open maps will greatly differ in size, shape, geometry, and layout. What you need to do is choose 1 to 5 common height locations in your map where you would implement these hints. Medium maps with mostly uniform building heights can get away with 1 horizontal hint, while complex, large maps with various building heights can do with 4-5 hints.
    If your map has a hill made of displacements that separates 2 parts of the map, then it is also a candidate for horizontal hints. You just need to insert a nodraw regular world brush inside the displacement to be used as support for the horizontal hint (the same technique can be used if you have a big non-enterable hollow building made mostly of func_detail/props/displacements).
    Vertical/corner hints
    These might not come into play as much as their horizontal siblings, however they could see a growing potential use depending on the map’s layout, geometry tightness versus openness.
    I cannot go through all combinations of open maps obviously to show you how to lay vertical and corner hints; what I will do is choose one diagram representing a typical open map scenario with some scattered houses, streets, and surrounding fields. Once you see how I proceed with these hints, it will become a lot easier for you to implement them in your own map regardless of the differing geometry and layout.

    Here’s our typical map viewed from top with grey lines being map borders, green rectangles being houses (solid world brushes), and our tiny red player at the rightmost part of the map. The map has a main street that goes in the middle between houses but the player is not restricted to this path only.
    The diagram below shows how I would proceed with my hints for such setup.

    This is basically what you get when you give a 5-year-old some crayons.
    Seriously though, I just gave each hint a different color so you could discern them on the spot, otherwise it would be hard to tell where each one starts and ends.
    Most of these hints go from one side of the map to the other while going from ground level to skybox top; don’t be afraid of having big hints that cross your entire map.
    Notice that we have both straight vertical hints (shown from above in the diagram obviously) and corner hints; what I did is that I compartmentalized the map so wherever the player is, chances are they will have the least amount of leaves to render in the PVS (this is just a basic hint system and more fine tuning and additions could be done but you get the gist of it).
    To get more details on hint placement, please refer to my paper Hints about Hints - Practical guide on hint brushes placement
    Areaportals
    If your map has enterable buildings, then it is imperative to separate indoors from outdoors using areaportals; this is top priority.
    Make sure to slap an areaportal on each door, doorway, cellar door, window, roof opening, chimney, etc. that leads inside the house in question.
    What about outdoor areaportals? Good call. In an open map without much regular world brushes to maneuver, it could get very tricky to set up an outdoor areaportal system to separate areas. However, you should always strive to have one, even if it is one or two areaportals across the map. The reason is very simple: the view frustum culling effect, which, coupled with hints, will yield the best results in cutting visibility around the map.
    Continuing with our previous diagram, a simple outdoor areaportal system setup could be as follows (top view).

    This setup will make sure that the map is split into 4 areas and whenever you are in one of them as player, the view frustum culling effect will kick in to cull as much detail as possible from the other areas.
    Let me show you the setup from a side view to make it easier to visualize.

    This is the same areaportal that was closest to the player in the top down view diagram but this time viewed from the side. Unlike hints where it’s fine to have one big hint going across the map, for areaportals, it is best to have several smaller ones that tightly follow the contour of the geometry eventually forming one big areaportal system.
    Another possibility for outdoor areaportal system is to have a combination of vertical and horizontal (yes horizontal) areaportals.
    If your map is a village for example with a highly detailed central square where most of the action takes place, a potential system could be made of several vertical areaportals that sit in every entrance to the square from adjacent streets, and a horizontal areaportal that “seals” the area and works as a “roof”.
    For a practical guide on areaportals placement, please check out my article Practical guide on areaportals placement
    Props fade distance
    This is a really, really important tool when optimizing large open maps. In case you got distracted while I was making the announcement, I’ll go again: props fading is definitely vital when tackling open maps optimization.
    What you need to do is to set an aggressive fade distance for all trivial props that do not contribute to gameplay. Players will look closely at how detailed your map is when they check it out solo on the first run; however, when the action starts and the round is underway, adrenaline, focus, and tunnel vision kick in, and all the details become a blur.
    During an intense firefight, players will not notice small props and details up close, let alone at a distance. We need to use this to our advantage to fade props thus releasing engine overhead; a faded prop is not rendered anymore and engine resources will be freed and allocated elsewhere.
    Your map geometry will dictate the proper fade distances, but as a rough guideline, small props could have a fade distance anywhere from 800 to 1200 units (flower pot on a window sill, small bucket at the back door, a bottle on the sidewalk…), while medium props could do with 1400-1800 range (a shrub, a power box on the wall, an antenna on the roof, wood plank, gutter pipe, fire hydrant…).
    Be very careful though not to prematurely fade critical props used for cover or game tactics (car in the middle of the street, sandbags, stack of crates, dumpster on the sidewalk…).
    Cheap assets
    Many people forget about this technique which is more than needed when it comes to open maps that tend to have larger average PVS than traditional maps.
    I showcased in a previous article of mine the fps cost of cheap and expensive assets (Source FPS Cost of Cheap and Expensive Assets).
    Get in the habit of using the low-poly model version as well as the cheap texture version in the distant non-playable areas and the high unreachable areas where players won’t have much of close contact with the environment. Potential candidates could include a distant field, the unreachable opposite bank of a river, a garden behind hedges/walls, high rooftops, the 3D sky…).
    Fog/Far-z clip plane
    This technique, when correctly used, can provide a big boost to your frame rate as parts of the world beyond the opaque fog won’t be rendered at all.
    For this technique to work properly, your map should have a foggy/rainy/stormy/dusty/hazy/night setting (use as applicable) where a fully opaque fog won’t appear out of place. Obviously, if your map takes place in a sunny and clear day, this technique won’t work much and it will look inappropriate.
    Using this is simple: For example, if your map is set in a rainy and foggy day, you just need to set the fog end distance while having its density set to 1. You will then set the far-z clip plane to something slightly higher than the maximum fog distance (if the fog end distance is 8000 units for example, the far-z could be set to 8200).
    3D skybox
    This is another good technique to reduce engine overhead and the cost of rendering.  
    It is true that the 3D sky is used to expand the limits of your level and decorate its surrounding, however, since it is built at 1/16 scale (and expanded in-game), it is also a nice way to decrease rendering costs. Use this to your own advantage and relocate assets in the non-playable areas with limited player interaction to the 3D sky.
    One thing to keep in mind though, the 3D sky’s visleaf is rendered at all times on top of the PVS in the playable area. Do not go overboard and make an extra complex, highly expensive 3D sky or you would be defeating the purpose of this optimization technique.
    Occluders
    You thought I forgot about occluders? Not a chance as these are the big guns when it comes to large open maps with little world brushes to use for other optimization techniques.
    Let’s clear one thing first; if your map is made mostly of brushwork and displacements with little to no props, then there is absolutely no need to resort to occluders as they’d be totally useless in this case. Only when the map is loaded with models and props in an open setup with little regular world brushes that occluders come to play in force.
    To place occluders, you would search for areas where these occluders could make the most impact (low fps, high traffic, props abundance) since they run in real time and are expensive, otherwise their cost would outweigh their benefit in terms of frame rate variation.
    Remember that occluders rely on the player’s position and field of view relative to the occluder to calculate what gets culled. You need to place them in a way to maximize the number of props to be culled behind them when the player stands in front of these occluders.
    Let’s see some examples.

    We go back to our famous top down diagram; the occluder is dark blue placed on the left wall of the large house while the little black stars represent various props and models. The 2 diagonal black lines denote the player’s FOV relative to the occluder. Anything behind the occluder and within the view frustum will be culled.
    That’s nice; we are able to cull 4 props but is it enough? It is not optimal as we can still do better. What if we move the occluder to the right wall of the house?

    Much better if you ask me. 5 additional props were added to the culling process meaning less overhead and fewer resources to render for the engine. That is why I said earlier it is all about maximizing the impact of the occluder by placing it in a way relative to the player’s position that maximizes the number of culled models.
    Here’s another example (still top down view).

    The player has moved to the middle of the central street, and beyond that L-shaped house is an open field with a lot of props scattered around. One way to implement occluders is as showcased in the above diagram. Notice how I arranged 2 perpendicular occluders along the walls for the maximum occlusion effect as all of these props in the field are not rendered from that player location.
    Another way to arrange occluders in this case would be diagonally across the L-shaped house (split into 2 or 3 occluders if needed to accommodate the nearby geometry; they can be floating without the need to seal an area).
    If you’re feeling brave enough (you should be after reaching this far in this article), you could also add an extra occluder along the wall of the house to the left of the L-shaped house to further enhance the view frustum occlusion effect and cover more props in the field.
    The most common places to add occluders in open maps include a displacement hill that separates parts of the map, a hedge that stands between a street and a field full of props, a floating wall between a house garden and the street, the walls of a large house, the walls of a tall building, a ceiling when it separates multiple levels…
    To read more about occluders placement and cost, please consult my article Practical guide on occluders placement
    In conclusion
    The foundation of optimization in Source engine will be the same whether it is a traditional map or an open one. You will heavily rely on func_detail, nodraw, displacement, props… to achieve your goals but it is the way you use these tools in an open map that makes all the difference.
    One might get away with being a bit sloppy with optimization in a traditional map, however, make no mistake that an open map won’t be any forgiving if you decide to skip a beat in your optimization system.
    Talking about different open maps and formulating varying optimization systems for them could fill articles; I hope this article has shed enough light on the open maps optimization approach to let you easily design a system for your own map.
  • Creative Airlocking: streaming in action games
    This article will discuss the loading and unloading of areas in linear single-player action titles, and look at contemporary examples of how the best games mask these so they appear seamless.
    Background
    When designing levels, Level Designers and Environment Artists must consider that their assets all have to fit within memory at once. While older action games like Wolfenstein 3-D and Doom would load the entire level with a Loading Screen at the start of each map, games like Half-Life started a trend of loading smaller sections gradually so they could squeeze in more detail and also provide a more seamless experience for players, making the game feel like one long adventure.
    At the time, going from one space to the next in Half-Life resulted in a seconds-long hitch with the word “Loading” on screen. There was no warning that it was going to happen, although Valve’s Level Designers oftenplaced these level transitions in smart places; usually down-time between combat and in a natural chokepoint. In later years, with faster computers, these load times decreased and are now almost seamless.

    Half-Life displays a small loading message when transitioning between levels.
    Currently, blockbuster series like Gears of War and Uncharted provide truly seamless transitions. After one long initial load for a new chapter with a completely new location (with new art) – sometimes masked behind a pre-rendered movie – “buffer” Streaming Sections are used, in which the previous area is unloaded, and the next loaded, on the fly. Since a lot of the globally-used entities are already loaded, and the environment is usually the same, assets can be shared, which can reduce these transition load times to much less than the initial level load.
    Essentially, these games take the smaller loading bar/screen of a more continuously-laid-out game like Half-Life, Portal 2 or Fallout 4 and make the player spend that time in the game world. If done creatively, players won’t even notice it. They might even enjoy the down-time if it’s well-paced, like The Last of Us where it can be spent on a thought-provoking puzzle or with the characters discussing something interesting.
    Overview
    Most action games budget out large areas, and then connect those with these smaller Streaming Sections.
     

    Section (A) is a huge space with lots of combat, Section (C) is another. Players in Streaming Section (B) can’t see into both (A) and (C) at once. Section (B) is where Section (A) is dropped from memory and (C) starts to load in. Section (A) being dropped shouldn’t happen in view of the player, and unless the game supports backtracking it is wise to place a back-gate to stop players returning, for maximum efficiency. As soon as Section (A) has been dropped, Section (C) can start loading in. It must have been loaded by the time the player exits Section (B), so it is also wise to front-gate players in case they rush through.
    The best way to think of a Streaming Section is as an airlock; the “door” behind the player is locked, the next area is loaded, and the “door” ahead opens. Ideally, these sections aren’t literal airlocks but instead nicely-disguised puzzles or narrative spaces between the action.
    Back-gating, and Unloading
    Back-gating, as the term suggests, is when the player is prevented from returning to a previous area. The ‘gate’ behind them is closed, in a lot of cases locked. This doesn’t have to be a literal gate or door, though. A ceiling can collapse causing debris to block the path behind the player, the player can fall through the floor and not be able to climb back up, they can pass through a one-way portal and not get back.
    Back-gating after entering the Streaming Section is usually done around a corner where the player can’t see Section (A) being unloaded.
    One-way animations are the main manifestation of these in modern action titles. Think of how many doorways your player character has held open, only to have it collapse behind them. The level section behind that door is now being unloaded, to make space in memory for the next large section. In co-op games, these animated interactions are a great way to bring players back together so that Player 2 isn’t left behind, only to fall through the world, in the section that is just about to be unloaded!

    The Last of Us has a huge variety of bespoke, painstakingly-animated back-gates.
    A cut-scene can also serve as a good back-gate, as long as it makes sense in the context and/or story so as to not feel tacked on, and is within development budget!
    One-way drop-downs are also a great and less flow-breaking back-gate. If the L-shaped area just before the drop-down can be kept in memory, as soon as the player drops down a ledge they can never climb back up, the previous area can be unloaded. The only down-sides to this softer back-gate are that they can feel contrived unless the game’s art and world can support it (terrain and collapsed structures are great for this), and that co-op players may have to be teleported to the dropping player so that they don’t fall through the world when Section (A) is unloaded.
    Slowing the player down, and Loading
    As Streaming Sections are usually connectors between two larger areas, they naturally make for slower-paced breaks in the action. Since Section (C) is being loaded in, slowing the player down in (B) – either literally as with Gears of War’s infamous forced walks or cerebrally with light puzzle gameplay – can be more efficient and interesting than just making a large footprint which has to cater for a player, say, sprinting for 30 seconds.

    Even when rushed, this plank puzzle in The Last of Us takes time and offers a nice respite.
    “Popcorn” encounters with just 1-2 enemies can be a good trick to allow loading to finish and slow players down and prevent them from simply rushing through a short Streaming Section. They also keep players on their toes and vary the flow from, for example, combat to puzzle to combat.
    Interactive Objects such as the slow-turning valves in Killzone 2 and the Gears of War games can also buy some loading time, as can environmental obstacles such as jumps or mantles or animations where the player’s buddy looks around for, and then finds, a ladder to kick down for the player to climb (also a good front-gate).

    Interactions like the valve in Gears of War slows players down and can also act as a front-gate.
    These approaches can also be combined in ways that fit the feel of the game, such as a Grub locking the player in a room and flooding it with frightening enemies in the first Gears of War game.
    Batman Arkham Asylum does a great job with additional ‘softer’ methods of slowing players down by playing a captivating well-acted taunt on a monitor from The Joker, or by encouraging exploration with The Riddler’s location-specific riddles or any number of collectibles.
    Front-gating, and Loaded
    As with Back-gates, front-gates are quite self-explanatory – the exit to the area the player is currently in is locked until certain conditions, such as all the enemies in the room being dead or the next area having loaded in, are met. Again, this doesn’t have to be a literal gate or door, just an obstacle in the world that can change its state from closed and locked to open.
    A lot of games from the Call of Duty series to Killzone 2 to The Last of Us extensively use friendly characters to unblock a front-gate; chain-link fences are cut through, doors are kicked open, wooden beams are lifted. New waves of enemies can also open a front-gate for the player and offer the bonus in that noisy, gun-firing AI attract players, like carrots on a stick, to the newly-opened exit. Many action games have excellent examples of enemies blow-torching open a door to get in or a huge monster bursting in through a wall; not only are these cool enemy entrances, but oftentimes their new unorthodox entrance-ways become cool exits, sign-posted by their un-gating event.

    Previously-locked doors in Halo often flash and make noise when opened by new enemies.
    Not all games front-gate the exits of their Streaming Sections because the time needed to load a Section (C) can usually be accurately gauged, and the acceptable fallback is a slight hitch. However, front-gates do provide that extra failsafe to ensure the next area is loaded before leaving a Streaming Section – in this case, a player with a scratched disk or corrupted file could see out of the world, at best, or get stuck or fall out of the world, at worst (though it could be argued someone with a scratch or corrupted files might see worse issues regardless).
    The biggest issue here is that front-gates need to fit the game or the level art – neat doorways or bottlenecks aren’t always possible. The other big issue is repetition; if a specific door interaction animation is always used, the game needs to provide a lot of variety in that animation!
    One trick that can be used to alleviate repetition, however, is if the front-gate is out of sight near the end of the Streaming Section (A). A check can be done to see if Section (C) has loaded, and if it has, the door can potentially be pre-opened saving the player another potentially-repetitive interaction but also holding as a true front-gate if a player does rush through.
    Batman Arkham Asylum had an interesting front-gate in the penitentiary sections; a security camera scanned Batman once before opening the door. Given the backtracking-heavy structure of the game, when racing through at full pelt, if the next area had not finished loading, the camera would loop the camera’s scanning animation. This is a great compromise because the camera scan completely fits the fiction of the world, and an extra scan animation would probably go unnoticed by many players.

    Batman Arkham Asylum’s Penitentiary’s doors only open when loading is complete.
    Conclusion
    In most linear action games, keeping the player immersed in the world is preferable to seeing a loading screen. If developers can create interesting activities, take advantage of slower pacing through narrative, or just make smart use of assets and an interesting space to traverse, Streaming Sections can be part of the world and not feel like generic winding corridors that stand out even to uninitiated players as padding.
    Copyright © Martin 'Alf-Life' Badowsky 2016
  • Participants have from the 15th of September 2016 until Midnight (GMT) on the 22nd of December 2016 to create, test and upload an original or Day of Defeat inspired map for Day of Infamy (www.dayofinfamy.com)
     
     
     

     
    Prize Structure
     
    1st place
     
    $3,000 cash
    Map included officially in game
    Corsair Hardware
    Void Surround Sound Headphones
    Strafe Keyboard
    Katar Mouse
    M330 Mouse Pad
    All Wall Worm Source Modelling Tools
     
     
     
    2nd place
     
    $1,500 cash
    Corsair Hardware
    Strafe Keyboard
    Katar Mouse
    M330 Mouse Pad
    All Wall Worm Source Modelling Tools
     
    3rd place
     
    $1,000 cash
    Corsair Hardware
    Katar Mouse
    M330 Mouse Pad
    All Wall Worm Source Modelling Tools
     
    4th place
     
    $500 cash
    Corsair Hardware
    Katar Mouse
    M330 Mouse Pad
    All Wall Worm Source Modelling Tools
     
    (*All prizes are subject to participant eligibility. No cash value. The contest Organizers and Sponsors reserve the right to change or remove the prize structure at any point with or without reason.)
     
     
     

     
    Sub-Prizes
    In addition to the prizes stated above, GameBanana will also be offering a sub-prize for the best development blog, work in progress or tutorial created throughout the process. 
    This is an entirely optional part of the contest and is open to members of all communities.
    To enter simply create either a development blog / work in progress page OR a level design tutorial / guide for Day of Infamy on either GameBanana, MapCore or the Insurgency Forums.
    Entries must be uploaded on or before Midnight (GMT) on the 22nd of December 2016, and include “[DoI Contest]” in the title. Entries will be judged by members of the GameBanana team, as they appeared at the deadline.. No changes or updates are permitted during the judging phase.
     
    Rules and Frequently asks Questions
     
    The submission must be a playable map for the PC version of Day of Infamy.
    Remakes of existing maps are not allowed, however maps inspired by classic DoD maps are encouraged.
    Entries must be submitted to the Day of Infamy mapping contest section of BOTH GameBanana.com and the Steam Workshop before the deadline.
    Multiple entries are permitted, however submissions will be judged on individual quality rather than quantity.
    Team based entries are permitted, however the entrants will have to agree how to split any prizes awarded, prior to prize claim and dispatch.
    It is essential to thoroughly test your submission before the deadline as entries cannot be modified during the judging phase.
    Exceptions: Changes to the submission profile are permitted after the deadline, provided they are purely aesthetic and that the map file does not change. (E.g. Editing the description / screenshots)
    Maps that were under creation prior to the announcement of this contest can be entered, provided a completed version has not been released for public Download.
    All custom textures, models or code must be contained within the download file or embedded into the .bsp.
    Authors are free to share their content on any other websites or services they wish, however the file must remain free to download and play, without requiring membership or payment.
    If the submission is distributed on an external website or service, it must clearly state that the submission was created for the "GameBanana / MapCore Day of Infamy Mapping Contest 2016”.
    Authors must be able to accept cash payments via paypal and will be required to fill in a prize claim form prior to payment. Winners of hardware and physical products will also be required to provide a valid shipping address.
    Judges and individuals associated with organising this contest cannot enter or assist entrants.
    Entries must clearly state which game mode the level is designed for.

     
    Eligibility
     
    Participant eligibility: The “GameBanana / MapCore Day of Infamy Mapping Contest 2016” is open to any individual, or teams of individuals, provided they comply with the following:
    Participants may not be an employee of the “Organiser” or “Sponsors”.
    Participants may not have taken part in the preparation or announcement of this
    Contest.
    Participants may not be a direct relative, spouse, direct employee, or long term
    partner of any of the above definitions (a - c).
    Legal Age: This contest is open to any individual who meet the above “participant eligibility” criteria. In the event of participant who has not reached the legal age in his/her state winning one or more prizes defined below, he/she must provide contact details for the legal guardian who will claim the prize(s).
     
     
    Submitting
     
    TWO (2) copies of the map are required for this contest, and must be uploaded on or before the deadline. The primary version (used for judging) must be submitted to GameBanana.com and placed in the “Day of Infamy > Mapping Contest 2016” category.
     
    http://gamebanana.com/maps/cats/8989
     
    The second version must be uploaded to the Day of Infamy Steam Workshop
     
    http://steamcommunity.com/app/447820/workshop/
     
    No changes to the downloadable file can be made during the judging phase. Please remember to ensure that all relevant custom content is included, and that your map is thoroughly tested.
     
     
     

     
    Judging Criteria
     
    Maps will be judged by the developers at New World along with the staff at MapCore and GameBanana. Each map will be scored on the following categories, and given a total score out of 100.
    Gameplay (40 marks)
    Visuals (30 marks)
    Originality (15 marks)
    Performance / Optimization (15 marks)
  • The Epic Games and Mapcore Unreal Tournament Level Design contest for Showdown has come to an end. After months of hard work we ended up with 28 Phase 2 submissions out of the 74 Phase 1 submissions. Starting something is easy, finishing it is hard! This makes the number of participants even more impressive. Especially considering that for many of you, Mapcore isn’t your home on the Internet (but we do hope that you stick around). Now, without further ado, here are the winners:
    1st Place:
    DM-Unsaved by Matthew 'Heresiarch' Beal 

    Prize: ($1650) + Swag
    2nd Place:
    DM-Croft by Ben 'Scinbed' Edney

    Prize: ($850) + Swag
    3rd Place:
    DM-Batrankus by Óscar 'TheGlecter' Crego

    Prize: ($500) + Swag
    4th Place:
    DM-Vacant by Christopher 'NATO' Morris

    Prize: Honorary Mention (Swag)
    5th Place:
    DM-Exo by Ryan 'Tidu' Garis

    Prize: Honorary Mention (Swag)
    Disclaimer:
    Since Unreal Tournament is still in active development maps will have to be recooked after each new build in order to continue working. Due to the maps having been build for an older version of Unreal Tournament, we are currently unable to provide download links.
    Stream:
    I’ll be contacting the winners to get their details so that they can receive their prizes. Epic will be reaching out to participants who’s maps are deemed fit to make it into the game or the marketplace. The full announcement stream, including feedback on the Top 5 maps, can be watched on the Unreal Tournament's Twitch channel or through the Youtube video below. It runs for over an hour and is definitively worth the time. If you can’t wait to get to the announcements, here’s an overview of when they were announced:
    03:00 - The stream starts and new exciting features for Unreal Tournament are discussed.
    13:50 - Intro to the announcements.
    15:32 - 5th place is being announced and discussed.
    22:40 - 4th place is being announced and discussed.
    31:30 - Stacey shows off the swag.
    33:12 - 3th place is being announced and discussed.
    43:02 - Epic talks about what will happen if maps are deemed fit for the game or the marketplace.
    43:42 - 2nd place is being announced and discussed.
    53:00 - 1st place is being announced and discussed.
    Play testing:
    You can also check out the Epic's blogpost with the results and a look at some of the swag. Now, don’t feel bad if you didn’t win. The Top 10 wasn’t that far apart and overall we had a lot of quality in this competition. Epic and Mapcore strongly encourage the participants to continue working on their maps. Epic will a host a community play test event where you can play the maps on their Hub servers. This will be announced at a later date and we’ll reach out to anyone interested to make sure their maps work on the latest build. Due to limited time and resources, we won’t be providing feedback for the rest of the submissions but please, don’t let that discourage you!
    Credits:
    Mapcore would like to thank Epic Games, the Unreal Tournament community, all the participants and our audience for trusting us to run this contest. We appreciate your support and dedication. On a more personal note, I would like to thank everyone for their compliments and especially Epic for their humbling shout out to me during the announcement stream. Last but certainly not least, a big thank you to the Mapcore Staff for support, reviews and generous donations!
    Thank you!
  • Almost two months have passed and we have a little more than one month to go until the July 4th 21:00 GMT+1 deadline. Phase 1 was a big success with 74 submissions.
    The following 28 maps have been uploaded to Epic's UT Hub servers:
    Alpine, Bridge, Croft Alpha 2, Cascade, Crossbridges, Deuterium, Dome, Eternal, Exo, Fall, Foundry, H09, Outbilette, Oxide, Plaster, Purification, Quay, Rust, Scoria, Silo , ShipRekt, Thaw, Traina7, Trustfall, Vacant, Malestrom, SuperCollider, RadioActive.
    The following 6 maps failed to load due to technical issues (various reasons):
    SD_pitfight, TS-swampforts, TSD-Contestmap, Royals, Batrankus Bastion, Karusel.
    Please keep this feedback in mind for your Phase 2 submission:
    Keep the name of the pak file the same as the name of the map you have posted. Many maps submitted have a completely different name than what was submitted to Mapcore.
    Add a screenshot to your map (in game). It will help encourage people to actually play it. 
    Have all files available to download on a site that doesn't require sign-ins.
    Make sure the prefix on the maps are DM- or CTF-. For showdown they should be DM-.
    Disclaimer:
    Also, I've lost quite some time chasing everybody down to submit in time, get the download links to work, etc. I understand that we have a lot of new people who don't call Mapcore their home yet. But keep in mind that it's your own responsibility to check in and see if new updates regarding the contest are posted. We use the forums and social media to reach as many people as possible, but it's easily missed. So keep your eye on our UT Contest FAQ or the UT Contest Discussion thread. Besides the forum and social media, I won’t be reminding people personally for their Phase 2 submissions. 
    Play testing:
    Now, onto the good news. Here’s how you can setup your matches on Epic’s UT Hub servers:
    Start Unreal Tournament.
    Select 'Find a match'.
    Select a random hub (has an Epic logo in front of it) that supports Showdown.
    Press 'Join' in the lower right corner (do not join a specific game mode, join the hub).
    Select 'Start new match' and then select ‘Custom’.
    Select your map, wait or invite players and have some fun!
    Entries:
    Let’s finish with some random screenshots of our Phase 1 Submissions.

    DM-Oxide by Mangley

    DM-H09 by Heresiarch

    DM-Rebel by Numb

    DM-Oubliette by Phantazm11

    DM-Croft by Scinbed

    DM-Eternal by Friechamp

    DM-Maelstrom by Maul

    DM-Cascade by Flikswich
    Good Luck!
     
  • This article is the first installment in a three-part article that looks at the considerations for creating a single-player combat space, using a walkthrough of the first battle in ‘Killzone Mercenary’ as a working example.
    Creating a Single-Player Combat Space Part 1
    This article will explain how to create a combat space for a single-player campaign, using my work on ‘Killzone Mercenary’ (hereon referred to as KZM) as an example.  There is already a fair amount of literature on the different methods you can use for creating a combat encounter, but I felt that none of it really discussed how to arrange the layout in closer detail, nor did they discuss where the different elements were appropriate.  In my early work I tried to jam in all the concepts for encounter design without fully understanding how they affected the player’s experience.  As strange as it sounds, I discovered there were times when it was better to restrict the number of elements being used to provide a much more focused and coherent experience; sometimes less is more. I will take you through an example to explain what I mean and how this can be the case.
    I will use the very first combat arena in KZM as it’s a small encounter where I can explain in depth what goes into even the most basic combat space. This encounter is a fight against assault troopers who are trying to stop the player from escaping the building and reaching the objective building; the ‘Halls of Justice’. I designed bigger encounters that featured many flanking opportunities and complex circular navigability but focusing on a simple encounter allows me to explain certain techniques in detail and where I purposely removed some elements to balance the difficulty and give the player different experiences.
    First of all I will explain two important aspects that must be considered for combat creation; AI metrics and weapon choice. I will then take you through a step by step walkthrough of this first encounter explaining in detail the reasons how it was designed and constructed for optimum player experience.
    Metrics
    The design mantra ‘form follows function’ should be the basis when creating an arena layout; that is that the arrangement of geometry should derive from its purpose. The arrangement should support the function not only of the style of experience you want to create (is it a tight corridor section with close quarters combat or an open space with multiple routes and options, for example) but it should also support the main element that makes up the combat encounter; the enemy AI.
    When considering the layout for the AI or non-player characters (NPCs) that will populate your environment you have to consider their metrics. These are the numerical values for how the NPCs move around and use the environment and the differences between various NPC enemy classes. This isn’t something people tend to talk about and so it can be easily forgotten or missed, yet it directly affects how your enemies will move and react.
    For example, in KZM the standard enemy NPC class were the Assault Troopers. These soldiers could be given patrols and animations to perform whilst they were in an ‘unalerted’ state, just like every other enemy class.  However, when they were in an alerted state their behavior changed so that they used cover points to move around the combat space. The maximum distance between cover points that an assault trooper would move was 10 meters. This meant that any cover point that was further away would not be considered, so we needed to make sure when creating combat spaces which used assault troopers that there were enough cover islands so they could move around. If there weren’t, the assault troopers would just stay in the same spot and could risk looking less intelligent.
    The assault troopers also tried to maintain a distance of 15m whilst they were trading shots with the player. The behavior was that if the player got closer than this range, but not so close that they were in melee combat distance (5m), the assault troopers would retreat to this mid-range distance of 15m. They would also never choose a cover position that was closer than 15m to the player, so when we created combat spaces we had to make sure that there was enough variety of cover positions in the >15m range.
    For the production of KZM we used the ‘Killzone 3’ engine and modified it for the PS Vita. In ‘Killzone 3’ the assault troopers picked their cover within a range that was further than 25m from the player, but we discovered that this was too great a distance for the enemy to still be clear and readable on the PS Vita screen. In our modified version of the KZ engine we had to reduce the combat distance to 15m, which meant that the original combat spaces we had created using the ‘Killzone 3’ metrics also needed adjusting in order for the NPCs to still work. It is an unfortunate truth that the game metrics, be it for the AI or otherwise, can change within a game’s development, which means that your combat arenas will also need to be adjusted.
    Weapon Consideration
    The metrics for both the player and enemy weapons were also considered. As this is the start of the game we can be more certain that the player is using the default starting weapons, at least on their first playthrough, before they have earned enough credits to buy a new arsenal. Therefore, the combat distances of enemy placement were considered to be comfortably within range for the player’s assault rifle.
    The enemy assault trooper archetype used assault rifles that were balanced to have a short range of <10m, and a long range of >20m. This meant that their behavior was to try and keep the player within these ranges and would thus move around the environment to try and maintain this. This was important to consider when building the environment so we could determine the amount of movement the troopers were likely to perform. This is important for balancing difficulty as a moving target is harder to hit.
    Foreshadowing
    As this was the opening of the game, we wanted to make it compelling in order to grasp and hold the player’s attention; we wanted to start with a bang. If the first lot of encounters in the game only included assault troopers with nothing else to differentiate them it may not have been so compelling. Therefore, we decided to include a significant Killzone enemy vehicle; the Helghast Dropship.  Of course it would have been far too difficult to fight a Dropship at this point in the game, so instead it was used as an impressive introduction of enemies into the arena using the rappel ropes from the ship itself.
    Using the Dropship at the end of the encounter, it was important to foreshadow its existence prior to its introduction. The level’s opening cut scene introduces the buddy character, Ivanov, and the narrative that he and the player are infiltrating the building whilst trying to avoid the searching eye of the Dropship.

    The foreshadowing of the Helghast Dropship
    Once the player has control they make their way up a flight of stairs learning how the movement works and feels whilst being in a safe environment. Once at the top of the stairs they enter through a door where they are introduced to the new melee attack which utilizes the touch screen on the PS Vita.
    First Wave
    After a successful melee attack the player enters through the door to the first combat area. The composition shows the exit of the arena in the top left third of the frame.  Central to the player’s view is where the first pair of enemies enter from, ensuring that their arrival is not missed.

    The exit to the arena is in the top left section of the opening composition
    Starting on the level above, the two assault troopers vault down into the gameplay space, to give their presence a more dramatic opening than merely walking in through a door. Their animation and movement also ensures that they catch the player’s eye if they aren’t looking in the desired direction. These vault down animations were 4m high, the standard height for a room in KZM, which meant this was a metric we had for the balcony and floor above.

    Two assault troopers drop into the environment from the level above
    Once the assault troopers had landed in the arena they became a lot less mobile than their standard behavior so that they were easier to shoot because, as previously mentioned, a moving target is harder to hit.  As this is the very first section of combat the player encounters in the game it was important to ensure that it was easy to get to grips with.
    None of the enemies were waypoint/navmesh restricted to certain areas in order to limit their movement as this could potentially lead to NPCs not behaving correctly under differing circumstances. In fact, there were only a very select few instances where we waypoint/navmesh restricted any characters in the whole of KZM; we instead crafted the environments to support the behavior we wanted from the NPCs. This was important for consistency; if you restrict areas and zones for the AI then they won’t behave consistently with what the player has learnt. This would lead to the player not being able to predict their behavior and therefore won’t be able to plan how to attack effectively.
    Here, in this first section, the two assault troopers took cover at two upright pillars of high cover and an overturned sofa of low cover. They didn’t tend to venture further into the environment unless the player had for some reason retreated to the edges of the level. The reason they wouldn’t move and advance on, or flank the player was because the other cover options in front of them were within 15m of where the player was likely to be stood. This caused them to be more static and thus easier targets to allow the player to get to grips with the shooting mechanics.
    I also chose to mainly use higher cover here so that when the enemies lean out of cover their shooting positions allowed the player to shoot their full body, which was a bigger target than when they poked their heads over the top of the low cover positions.
    Low cover positions are great for seeing the enemies move around and change their positions, as the tops of their helmets are visible over the top of the cover. Enemies are much harder to track when they use high cover as it breaks line of sight to them, so this is usually the harder option. However, as they have restricted cover positions and weren’t moving around in this specific situation, it was the best option to use for less difficulty.
    First Combat Front
    A ‘front’ is the perceived line or boundary that faces the enemy and is the nearest position which combat should be engaged from. The ‘fronts’ used here create boundaries between the two sides; a front for the player and the buddy character and an opposing front for the two assault troopers. This was the simplest setup to start the player off with and it only required two sets of cover points as I didn’t want to encourage the enemy to flank the player at this stage. This section of the encounter only needed these few pieces of cover (in the image below) in order to work and the other pieces of cover were actually for further waves of combat.

    The two fronts and the cover setups providing it
    It’s also worth noting that the cover object which the buddy character crouches behind is positioned further forward than the arrangement of cover that the player is drawn to. This is so that the buddy character is in the player’s view so they always see the buddy’s actions and involvement. It wouldn’t be optimal to have a buddy NPC that the player rarely saw. The buddy is also kept near to the player in order to maintain a close relationship and the feeling of being a team. Empathy is directly related to proximity between characters, so if the buddy was further away from the player they would experience a much more detached feeling towards them.
    Continue to part 2 or go back to the homepage. 
    Index:
    Creating a Single-Player Combat Space Part 1
    Creating a Single-Player Combat Space Part 2
    Creating a Single-Player Combat Space Part 3
    Copyright ©Peter Ellis 2016. Killzone™ Mercenary is the property of Sony Computer Entertainment © 2013. Killzone is a trademark of Sony Entertainment Europe. Killzone: Mercenary is a trademark of Sony Computer Entertainment America LLC.
  • A new question?
    After successfully solving the eternal mystery of func_detail vs. displacement in my last article (here), I was contacted by the High Council of Source Engine Optimization. Apparently, there seems to be another enigma to be uncovered and a major question to be answered.
    What is the fps cost of cheap and expensive assets in Source engine? Is there a significant difference between the two in terms of frame rate? (that’s 2 questions but I’ll let this one slide)
    The study
    As with the last article, this one is also going to be a short but sweet article; fewer words, more numbers and screenshots. The systematic approach is also going to be very similar: 2 similar test maps where one contains expensive assets while the other has cheap versions of these assets. The assets will be the same and will be located in the same locations in both test maps.
    The recent assets added with the new de_nuke update in CSGO will be the perfect candidates for our study as Valve made most of these in cheap and expensive versions. For props, the expensive version is high-poly models while the cheap one is low-poly. For textures, the expensive version gets a normal map (up to 2), specular map, advanced reflections, detail map, and Phong shading in some cases; the cheap version is basically the diffuse map with the occasional detail map.
    I will record the localized fps in both versions and compare, then draw conclusions that will hopefully answer the High Council’s question(s).
    The testbeds
    The first map to test is the one made of cheap assets. It’s basically a simple map consisting of 4 walls and a floor on which are spread several props and textured blocks at predetermined locations. Textures are mostly concrete while props contain crates, cars, pipes, wires, doors, and vents.

    The fps recorded is 330 fps. The expensive version is exactly the same but with props replaced with their high poly versions and textures swapped with their expensive versions.

    The fps is now 286 fps; interesting. All right, let me call the High Council to relay the news.
    Hold your horses right there. We are men of Science and you know that…yes, yes, I know, one map is not enough to draw conclusions.
    I’m going to take this map and quadruple it, in area and in content, and test again (Nobel prize here I come). The new map will have 4 times the amount of props and textured brushes (the same ones of the initial map cloned into the new areas) as well as having its total area increased fourfold. We start with the cheap version that we will refer to as test map (4x).

    The fps decreased to 279 (from the 330 in the simple cheap map) due to the extra content that the engine has to render. Our main point of concern would still be to compare this version against the expensive one.
    You know the drill by now; we will also create the (4x) expensive version.

    The fps is 229. The decrease in (4x) version is more or less in line with the one in the simple version. Let’s recap in a table for easier viewing.

    As you can see, the fps dropped 44 fps in the simple version and 50 fps in the 4x version, between the cheap and expensive maps respectively.
    We can draw 2 conclusions from the above table:
    There is a significant drop between the cheap and expensive version (44/50fps), and there is also a substantial drop within the same version (51/57fps) when you add much more content that is all visible in the PVS.
    These results can shed some light on the latest update of de_nuke where the overall fps is lower than the rest of the stock maps in CSGO. The high amount of props/details that can be seen/rendered from one location coupled with the expensive assets in the playable area contribute to further decrease in the overall fps in that map (in addition to the open skybox/layout). I have tackled a revised optimization system for de_nuke in a topic of mine last month that can be read here (https://www.mapcore.org/topic/19909-de_nuke-a-revised-optimization-system/)
    As a bonus, I’ll throw in the compile times of the above maps so you can witness the effect of cheap vs. expensive, and the additional content in (4x) versions, on the compile time, especially on vrad since it will mostly be affected by the extra faces in the high poly models and the additional vmt switches in the expensive materials.

    You can clearly see that vrad times increased considerably between the cheap and the expensive versions, as well as within the same version when we quadrupled the area/content.
    Now if you’ll excuse me, I still have a phone call to make; the grand council woman cannot wait any longer.
    The final cost
    Expensive assets bring visual eye candy to the map in hand which is a necessity in today’s ever-growing and continuously pushed graphics boundaries. Relying on low poly models and cheap textures won’t fare well on the visual fidelity front. However, expensive assets come at a cost of taxing the rendering engine and decreasing the overall fps in the map.
    These expensive assets are a requisite if you want your map to shine (pun intended) but one has to be careful not to overuse them. Use them wisely in the playable area and resort to cheap versions when decorating the non-playable areas of the map or any place that the player cannot see up close to discern the difference.
     
  • Epic and Mapcore are teaming up! In an effort to push the custom content scene forward, we are hosting a Level Design contest for Unreal Tournament. We challenge you to create a new level for the “Team Showdown” game mode.
    Phase 1 - ­Design (1 Month) 
    Design a level for the new “Team Showdown” Mode in Unreal Tournament 4.
    Focus on level flow, theme, weapon and spawn placements that compliments “Team Showdown”.
    Contestants need to submit their designs before the May 2nd deadline on Mapcore’s contest forum. 
    Phase 2 - Art and Polish (2 Months)
    Use official art (Liandri, Castle, Chill and Snow Fortress assets) or your own.
    Mesh and light the level.
    Do a collision/blocking volume pass. 
    The level must be functional.
    The level must run at a reasonable framerate (dm­outpost23 is a good reference).
    Contestants need to submit their designs before the July 4th deadline on Mapcore’s contest forum. Download links will be sent to Epic, who will judge all entries. Epic will also host a community playtest event of the final submissions. 
    Rules
    Small teams are allowed, for example, an artist and a designer.
    Custom art is allowed, but use of official art is completely fine.
    You can start art passing whenever you're ready. You don’t have to wait for the second phase.
    You have to be willing to have your level tested and played in Unreal Tournament.
    Must be designed for “Team Showdown” but that doesn't mean it won’t work for Deathmatch.    
    Disclaimer 
    Prizes will be sent to the individuals who post the submissions. We are not responsible for how teams wish to submit and divide their prizes. 
    Judging and Prizes
    The entire UT team will vote for their favorite submissions and the results will be shared on Unreal Tournament's Twitch channel.
    First Place ($1650) + Swag
    Second Place ($850) + Swag
    Third Place ($500) + Swag
    Fourth Place ­ Honorary Mention (Swag)
    Fifth Place ­ Honorary Mention (Swag)    
    Depending on the quality of entries, and work required to take the levels to release quality, Epic will evaluate the possibility of adding winning entries into the Marketplace or the game. Epic will work directly with the designers on any issues that need resolving (similar to dm­lea and ctf­pistola).
    Good Luck!
  • What is the question?
    Ever since the dawn of humanity, this question was the center of a colossal debate. Greek and Roman philosophers tried to solve it to no avail. Alchemists in the Middle Ages gave it a go and failed miserably. Even Industrial Age scientists touched on the subject with no big breakthrough.
    Luckily for everyone, I am here today to answer this question and put an end to a centuries-long argument: What is better in terms of fps, func_detail or displacement, in the context of the Source engine? If you were expecting an existential question, I am deeply sorry to disappoint you but hey, life is full of disappointment.
    The study
    This is going to be a short but sweet article; fewer words, more numbers and screenshots. The study is pretty straightforward and systematic. To make things fair and square, I will create 2 exactly identical test maps: In one, everything will be turned to func_detail while the other will have everything switched to displacements. I will then proceed to record the localized fps in these maps from a preset location and compare. Pretty simple, isn’t it? Well, it should be as the whole purpose of this study is to compare func_detail vs. displacement in absolute terms while keeping all other parameters constant.
    The cases
    The first map to test is the one made of displacements. Here is the screenshot showcasing the fps.

    The map itself is very simple consisting of 7 identical houses placed at predetermined locations and surrounded by 4 walls. The houses are detailed enough to put some slight pressure on the rendering engine. For the skeptics among you, here is a wireframe in-game shot to show that everything is made of displacements.

    To refresh your memories, in Source engine wireframe mode, green is displacements, pink is brushes (world, func_detail, brush entity, etc…), blue is props, and yellow is decals/overlays. The recorded fps in this map is 289. We now move to the second map, the func_detail version to check how the frame rate is faring. Here is the awaited screenshot.

    Surprise, surprise. The fps is 330, much higher than the displacement version. Here’s the wireframe shot to put your mind at ease.

    Honestly, I was thinking the figures would be more on par as the engine handles both details and displacements pretty well, but in the end, Source is about BSP so I guess brushes would get a slightly preferential treatment over polygon meshes (conspiracy theory ensues).
    The question that forces itself now is: Should we rely solely on func_detail in our maps? Of course not. Both func_detail and displacement have their advantages and inconveniences and leaning exclusively on one will inevitably lead you to a dead end. The best thing to do is get the best of both worlds by using them together.
    In our little test map, how about we mix things up in a third version: let us make the house walls out of displacements while having the doors, windows, frames, and roofs made of func_detail. Incoming screenshot, brace yourselves.

    Much better, isn’t it? We have now 311 fps, a very nice middle ground between the 330 fps of func_detail and the not-so-bad 289 fps of displacements. The mandatory wireframe shot follows.

    So, what can we learn from all this? Well, apart from the obvious places where displacements are mandatory for the organic mesh sculpting (rock formations, cliffs, bumpy/twisted roads…), it is a good idea to spread some more displacements around your map to alleviate the total brush-count that you will inevitably hit the maximum in a highly detailed map. Your fps will remain high and you will enjoy the margin to keep adding structures to your map without fear of reaching the maximum allowed total brushes (substituting brushes with models/props is another viable solution that is not in the scope of this article).
    I’m a man of science and I know that one example is not enough to draw conclusions. That’s fine, I have a second test map to investigate what we established before. The concept of having 2 identical maps is still the same, however, this time, we will spice things up by adding some static/physics props and some decals here and there. We will start with the displacement version.

    230 fps, not too shabby. Let’s check another angle.

    220 fps, more or less, on the same level as the previous number. Now for the wireframe shot.

    The tree cards in the background are func_brush in both maps (the detail and displacement versions), so it’s a level playing field in this case.
    Now for the moment of truth you all have been waiting for: will the detail version have better fps to support my earlier findings or will I be publicly embarrassing myself? A screenshot to the rescue.

    I knew I was right, never breaking a sweat (apart from the nervous cold sweat I just wiped off my forehead). 255 fps for the first location A. Let’s check the other angle or location B.

    250 fps. Bam, sweet victory…sorry I got carried away a bit. Ahem…Let’s get back to being scientific, shall we. Here’s the wireframe proof.

    Let’s recap all the action and numbers in a nicely formatted table.

    You can notice the fps gap between the func_detail and displacement versions in both test maps whereas the “mixed” version considerably narrowed this gap. The numbers have spoken.
    The bottom line
    The bottom line is, if you rely only on func_detail, you will hit the maximum brush-count allowed in Source and severely limit your map and creativity. You might also run into T-junction issues as well as parts of your geometry flickering and disappearing from certain angles in densely func_detail’ed areas.
    On the other side, if you stick to displacements alone, then you will have lower fps than a func_detail map version. You might also run into visible seams and un-sewn displacement issues.
    Having a clever distribution of both func_detail and displacement in your map is the way to go. You will have high fps, better lighting around the edges, and organic sculpting while not getting anywhere near the total brush limit; the best of both worlds.
     
  • (Art by Thurnip)
     
    This overview proves how talented our community is. We share, give feedback and learn from one another. Lots of our members have made it into the game industry and continue to make their mark working for high-profile studios. Our articles were shared around the world and our collaborative CS:GO contest was a huge success. We can only conclude that 2015 was again a stellar year for the Core and we are looking forward to an even better 2016!   
     
    2015: Mapcore's Year in Review
    It was a banner year. Here’s a taste of what our community created:

    Temple of Utu by Minos 

    Corridor by JonnyPhive

    Rails by Deh0lise

    Cold Fusion by Rusk

    Half-Life 2 Scene by Psy

    Resort by 'RZL and Yanzl

    Zoo by Squad and Yanzl

    Santorini by FMPONE and Dimsane

    Corridor by RaVaGe

    Seat by penE

    Half-Life 2 UE4 Corridor by PogoP

    Tulip by catfood

    Volcano by 2d-chris

    Chilly UE4 Scene by TheOnlyDoubleF
    Articles
    High-quality original content:






    Grand Prize Winner Announced


    Hurg Smiles Upon You All!
     
     
  • This level design article is about the past and the present of the hostage rescue mode in Counter-Strike. Showcasing the inherent issues that accompanied the scenario allowing the bomb/defuse mode to gain traction and popularity. This article will also present what can be done, level design wise, to remedy some of the shortfalls and allow the scenario to be viable.
    A historical background
    Counter-Strike officially started life in June 1999 with the release of beta 1, and it shipped with four maps, that’s right, four whole maps. They were all hostage rescue maps and the prefix used for these maps was cs_ as opposed to the standard deathmatch maps starting with dm_. This prefix was an abbreviation of the game’s name (Counter-Strike) which hints to this hostage-rescue scenario being the only one in the minds of Gooseman and Cliffe, the creators of CS, at the time of launch.
    Fast forward a couple of months, beta 4 rolled out in November 1999 bringing to the table a new scenario, bomb defuse. The new maps carried the prefix de_ and while one would think that the hostage rescue maps would be switched to hr_ prefix, they kept the same prefix which started to be referred to as the “Classic Scenario”. Counter-Strike was built on hostage rescue scenario.
    I started playing CS in beta 2 in August 1999 (I totally missed beta 1, screw me) and maps like Assault and Siege were all the rage at LAN parties. The nearest LAN/internet café was a 5-minute drive from my place, and LAN parties with friends used to be a blast full of shouting, cursing, bluffing, noob-trashing; the standard menu for a CS session. Good times.
    Siege, the oldest CS map (beta 1), and Assault (beta 1.1) were the epitome of the game. You had to dive in as a CT deep into the T stronghold to rescue the hostages and bring them back to safety. These maps were the most played on LANs and embodied the style of early CS gameplay. At the LAN place where I used to wage my virtual battles, Assault equaled CS, literally. A fun fact is that when Dust came out, I started a LAN session with this map and everyone in the room shouted at me: "What the hell is this? We wanna play CS!" For my friends, Assault was CS.
    However, those rosy days for hostage rescue began to turn into grim grey when folks started playing bomb defuse scenario and realized how…fun it was. A map like Dust almost single-handedly pushed the scenario into higher ground with its bright environment/textures, clear/wide paths and its ease of use and noob-friendliness. A year later, around Summer 2000, Counter-Strike was now equivalent to Dust for my friends.
    How did this happen? What went wrong?
    Inherent flaws of hostage rescue
    Hostage rescue is a very delicate and tough scenario for law enforcement operators in the real world. It puts the assailing team at a great disadvantage against heavily-armed barricaded hostage-takers who are probably using civilian hostages as human shields and as a bargaining chip for a later escape.
    As you can deduce, transferring this scenario as realistically as possible into the game will not fare well, and this disadvantage will carry on for the CT team. The problem is only exacerbated when you add the more or less “flawed” game mechanics to the scenario. This is exactly what went wrong with hostage rescue scenario in case you are still wondering about the rhetoric questions at the end of the historical background introduction. The popularity of cs_ scenario started dwindling and the rise of the bomb/defuse scenario only made things worse.
    Almost all the early cs_ maps featured a relatively tiny hostage zone/room having one entryway usually sealed with closed doors that the CT must open to get access inside. This room was typically located behind T spawn which made the area a camping ground and made camping that zone an obvious and rewarding tactic for Ts. The doors having to be manually opened with a loudening sound made things worse and negated any surprise or sneaky rush towards the hostages. A classic example is the hostage area and T spawn in cs_assault.

    I dare not think of how many Ts are camping behind those doors
    Another equally important camp fest occurred in the hostage rescue zone. Early designs made the rescue zone relatively small with one or two access paths that can be defended from one location. If the CT team manages to reach the hostages and rescue them, the Ts could easily fall back to the rescue zone to camp and patiently wait for the CTs to show up. The hostage rescue zone in cs_italy is a nice example to showcase how one T could camp in the southernmost spot in the zone allowing him to monitor both entryways, from market and from wine cellar, within the same field of view. CT slaughter was almost a guaranteed thing to happen.

    A CT will show up any second now; imminent slaughter commencing in ...3, 2, 1
    A third flaw was the hostages themselves. They were difficult to escort and protect and were easily stuck or left behind in various parts of the maps between their initial hostage zone and the final rescue zone. I lost count of how many times I rescued the hostages and ran as fast as I could to the rescue zone, reaching it with a big grin on my face only to turn around and find out that only one or two of the four hostages actually followed me; the others were randomly stuck on a ladder, door frame, window ledge, vent, chair, table…I could go on but my blood is starting to boil just thinking of this.
    To add insult to injury, hostages could also be killed or “stolen” for ultimate trolling. When Ts were stacked on money, they could easily kill all the hostages, basically turning the round to a frustrating terrorist hunt for CTs. In early CS versions, a CT teammate could press the “use” key on a hostage that you were already escorting to steal it. This would leave you helplessly wondering where the hell did the 4th hostage go in case you did not catch the teammate performing the action.
    Lastly, maps themselves contributed to the issues that were piling up against hostage rescue scenario. If you are a CS veteran and you were around the early betas in 1999, you would most certainly remember how quickly hostage rescue maps were pruned from one beta to another; some maps even had a life span of 1 week before being discarded out of the official roster. Most of these early cs maps featured dark, nightly environments that were unfriendly to both newcomers and established players. Other maps had a confusing-as-hell labyrinthine layout that confused even the most great-sense-of-direction players, and made remembering paths nigh impossible. Some of these maps had narrow twisted paths and choke points, vents, and ladders that not only frustrated players (especially CTs) but also made rescuing and escorting the hostages more of wishful thinking. The icing on the cake was the different gimmicks introduced in some maps that made a frustrating gameplay/layout even more annoying: some maps had a machine gun nest in T spawn allowing Ts to master and perfect the art of CT slaughtering while other maps had flammable drums that could be shot and blasted for the ultimate carnage right next to the hostage zone. Good example maps include cs_prison, cs_bunker, cs_iraq, cs_hideout, cs_facility, cs_desert, among many others.
    Meanwhile, bomb/defuse scenario was gaining grounds at an increased rate and before too long, hostage rescue was relegated to a distant second place in terms of popularity among players and level designers alike.
    As a small experiment, I tallied the number of custom hostage and defuse maps submitted on Gamebanana for Counter-Strike Source and Global Offensive. For CS:GO, there are 761 de_ maps against 157 hostage maps while for CS:S, the figures are 4060 de_ for 1244 cs_ maps. The disparity is rather meaningful as the ratio in CS:GO is 4.85:1 while for CS:S the number is 3.26:1. This means that for each hostage map in CS:GO there are almost five maps of bomb/defuse whereas this number drops slightly to almost three maps for CS:S. With CS:GO putting extra focus on competitive gameplay, this ratio is bound to further grow widening the rift between bomb/defuse and hostage rescue maps.
    That’s it? Is it done for cs_ maps? Shall we prepare the obituary or is there a magical solution to breathe some fire and life in them?
    Solutions for viability
    There is a magical solution that involves you transferring a large sum of cash to my bank account, then my “guys” will contact your “guys” to deliver the “solution”. The drop point will be at the…apparently, there has been a mix-up, this is for another “deal” …nervous chuckle.
    Seriously though, while there is no magical solution that will lift hostage rescue onto the rainbow, there are a couple of things that level designers can do to start injecting some momentum to the scenario. Luckily for us, Valve has already paved the way (so these “Volvo pls fix pls” do work after all?). In March 2013, Valve introduced a major CS:GO update that completely overhauled the hostage rescue scenario mechanics and introduced cs_militia as well. The update was a game changer and a much needed tweak towards a better hostage rescue gamemode.
    We now have two hostages instead of four, and the CTs only need to rescue one of them to win the round. Moreover, the hostage does not stupidly follow the CT but instead is carried on the CT’s shoulders. Obviously the movement speed of the CT carrying the hostage is decreased but this “inconvenience” is countered with added bonus round time and the fact that the CT doesn’t have to glance over his shoulders every five seconds to make sure the hostages are still following him (this kind of distraction can prove fatal to the CT escorting the hostages). The hostages’ spawn location is randomized and can be controlled by the level designer. A nice change is that hostages don’t die anymore thus cutting any chance of Ts trolling (you still lose money when you shoot a hostage – shooting a hostage is pretty pointless now akin to shooting yourself in the foot).
    This is all good news if you ask me; hostage rescue is on the right path to become popular and viable again. With Valve doing the first half of the change, level designers have the duty to continue with the second half.
    Hostage defuse?
    As a first suggested solution, let us start treating hostage rescue as bomb defuse. Let’s be honest, bomb defuse works really well, so why not transfer this “experience” into hostage rescue. What we can do is to have a hostage rescue map’s layout mimic one of bomb defuse – that is have two hostage zones that are similarly placed as two bomb sites. We need to start treating a hostage zone like a bomb site with all accompanying techniques of rushing, pushing, faking, peeking, holding, smoking, flashing, etc. The good thing about this is that whatever knowledge, skill, and layout awareness that players have acquired from defuse scenarios will transfer effortlessly to the hostage rescue scenario; you do not need to learn new tactics and strategies. The roles will be inversed: instead of Ts rushing bomb sites and CTs defending, CTs will push hostage zones and Ts will defend and rotate.  
    Sounds logical, right? Some people might argue that having 2 separate hostage zones is not “realistic” and my answer is Counter-Strike was never about realism (carrying and running around with a 7 kg (15.5 lb), 1.2 m (47.2 inch) AWP sniper rifle with 25x telescopic sight, quickscoping and headshotting opponents is the epitome of “realism”). If you want a realistic hostage rescue scenario, then you are better off playing the original Rainbow Six Rogue Spear and SWAT 3 from 1999, or the more recent ARMA and Insurgency for a realistic military setting. I practice what I preach and I already implemented this technique in my last map “cs_calm”. The map was a remake of my CS 1.5 map from 2003 and obviously I made the “mistake” at that time to follow the trend set by official maps of having one hostage zone right behind T spawn. A playtest on Reddit CS:GO servers back in March 2015 confirmed that this setup won’t work well as Ts will inevitably abuse the hostage zone.
    I made some radical layout changes towards T spawn and hostage zone and created two new hostage zones on the upper and lower levels of the map that are connected by a back hallway to allow quick rotations (in addition to the one through T spawn). Obviously, there is no direct line of sight between hostage zones to prevent 1-zone camping. Ts have absolutely no incentive to camp one zone as CTs can reach the other one, rescue the hostage and head back to the rescue zone without being spotted from the other zone. CTs actually have a chance of winning the round by rescuing the hostages.
    I like to believe the new layout worked well. Only time and more hostage rescue maps will tell.

    Layout of the map "cs_calm"
    Rescue zone anti-camping
    We have remedied the hostage zone camping but we still need to tend to the rescue zone camping issue. A solution to this is to have two rescue zones in a similar setup to what is nicely done in cs_office. While Ts can still camp one zone, they risk a big chance of having CTs reach the other rescue zone. Again, CTs will have a viable option to save the hostages without being shredded by camping Ts. If the layout does not allow or facilitate having two rescue zones, then one big rescue zone with multiple entrances (three is a good number) should work fine. The trick here is to have the entrances not easily covered within the same field of view to prevent camping.
    Into the zone
    Just as we established that we should treat hostage zones like bomb sites, it goes without saying that each hostage zone should have at least 2 to 3 entry points. It’s pretty pointless to have only one entrance as this totally defeats the purpose of spreading hostages into two zones. The different entryways should also not be covered within the same field of view of one T; if a T decides to camp the zone, then he should be able to cover two entrances from one point leaving the third one more or less at a dead angle and viable for a CT rush or stealth/sneak surprise. 

    Showcase of Hostage Zone A on the map "cs_calm"
    The above screenshot showcases “Hostage Zone A” in cs_calm. A terrorist will typically camp near the hostage covering the two encircled entrances. The third entrance from upper level denoted by the arrow is not in the direct FOV, and is prone to a surprise attack by CTs that could catch the camping T off guard. If possible, try to spread the entrances on different vertical levels to spice things up and keep Ts on their toes.
    Lastly, it is a good idea to have a connector between hostage zones to allow fast rotations but without having a direct line of sight between hostage zones. We want to make the scenario fairer to CTs but not at the expense of Ts, inadvertently making it unfair for them.
    Conclusion
    Hostage rescue is a fun scenario if you ask me. It had many inherited and added flaws that contributed to its waning but it’s nothing that can’t be reversed. We, as level designers, need to push some changes to put the scenario back on track. What I just showcased in this article might not be the only viable solutions but they certainly are a step in the right direction. Level designers are intimidated by players who shun away from cs_ maps, and this turns into a vicious circle where players avoid hostage rescue maps and mappers in return avoid designing them. We need to break this cycle and designers need to bravely embrace the solutions I presented here or come up with their own solutions. The more cs_ maps that come out and get tested, the more we could validate these solutions as viable.
    In either case, we need to get proactive towards hostage rescue scenario; after all, this is the cornerstone that Counter-Strike was built upon.
  • (Art by Thurnip)
     
    It's Time!
    It’s finally time to declare a grand prize winner in our exciting Counter-Strike: Global Offensive mapping contest. You’ve playtested the maps on Reddit, you've waited months for the results... let's get down to business!!
     
     
     
    GRAND PRIZE WINNER:
     
    DE_EMPIRE
    By Andre Valera

    Workshop Link
     
    Sometimes it boils down to consistency: broad strength across several categories. No map in our contest better exemplifies this notion of consistent quality than Empire.
    Empire features a stacked bomb-site layout similar to popular official maps like Nuke and Overpass. While this relatively unorthodox design presents level designers with additional challenges, Empire ably sticks its landing. Furthermore, the ambition of Empire’s design is tempered well by its no-nonsense visual presentation. We’re left with a digestible, fun, and very playable level.
     
    Congratulations, Andre Valera!
     
    Prize:
    Featured in a goRGNtv showmatch!
    Featured in CEVO PUG rotation for one month!
    $1000 and Mapcore swag!
    CS:GO prize pack courtesy of Valve:
    a signed CS:GO poster, lanyard, vinyl sticker
    SteelSeries Kana Mouse!
     
     
    2nd PLACE:
    DE_BOURG
    by Klems

    Workshop Link
     
    A truly unique map. Some felt it was the strongest entry in the contest given its strong theme, abundant polish, and beautiful visuals; others, however, questioned the map's small scale. This was a tough map to judge.  
     
     
    Prize:
    $400!
    CS:GO prize pack courtesy of Valve: 
    a signed CS:GO poster, lanyard, vinyl sticker
     
     
    3rd PLACE:
    DE_ROYAL
    By Jakuza

    Workshop Link
     
    An attractively sleek map, there is plenty of room for Royal to blossom into something very special. 
     
    Prize:
    $200!
    CS:GO prize pack courtesy of Valve: 
    a signed CS:GO poster, lanyard, vinyl sticker
     
     
    4th PLACE:
    DE_COAST
    By Ornate Baboon

    Workshop Link
     
    A map that was under heavy construction for much of our contest, one gets the sense that Coast wasn't quite ready yet. With a little bit more time, who knows?
     
    Prize:
    $100 + Mapcore swag!
    CS:GO prize pack courtesy of Valve: 
    a signed CS:GO poster, lanyard, vinyl sticker
     
     
    ~~~We at Mapcore would like to thank the r/GlobalOffensive moderators for their assistance, our lovely guest judges, Valve, goRGNtv, CEVO, as well as Gamebanana.com and Steam workshop artist EGO DEATH for contributing to our prize pool.
     
    Last but not least... THANK YOU, for making this 'Core event special and fun!
     
     
    "May Hurg guide you..."
     

  • (Art by Thurnip)
     
    Contest finalists have been chosen!
    Before announcing our finalists, we want to thank everyone for participating and giving your feedback: with over 150 entries, this event has thus far exceeded expectations in every way.
    We strongly considered adding an “honorable mentions” addendum to this announcement, but realized there were simply too many maps which came extremely close to becoming finalists, lacking only one of our “big three” judging criteria components.
     
     
    Now, without futher ado…
     
    THE FINALISTS:
    (in no particular order)
     
    DE_ROYAL
    By Jakuza

    Workshop Link
     
    DE_EMPIRE
    By Andre Valera

    Workshop Link
     
    DE_BOURG
    by Klems

    Workshop Link
     
    DE_COAST
    By Ornate Baboon

    Workshop Link
     
    These exciting levels exhibit competitive potential, excellent visual presentation, AND a satisfying level of polish, making them truly strong representatives for our talented community. As finalists competing for the grand prize, the authors of these levels will be able to update their work based on your feedback, including fine-tuning their competitive layouts using public playtesting over on Reddit. Let's support them on their journey!
    To check out the excellent prizes awaiting our finalists (including money prizes + official Valve merchandise), click here.
     
     
     
    Congratulations, finalists!
    ...but who will be the Grand Prize Winner? Find out September 30th.
     
     
     
     
    P.S. – To all our wonderful participants: don't despair. Level design is an art to be pursued for its own sake, and brilliant work should always be celebrated and studied. Additionally, Valve has consistently supported CS:GO community mapping, and Valve Operations remain a lucrative and thrilling opportunity for community mappers such as yourself. Valve’s criteria for Operations can be found here.
     
    "Never give up." - Hurg

  • This is the second part of a technical analysis about Source Lighting, if you haven’t read the first part yet, you can find it here. 
    Last time, we studied the lightmaps, how they are baked and how VRAD handles the light travel through space. We ended the part 1 with an explanation of what the Constant-Linear-Quadratic Falloff system is, with a website that allows you to play with these variables and see how lighting falloff reacts to them. We will now continue with basic examples of things you can do with these variables. 
     
    Examples of application
    Constant falloff
    The simplest type of falloff is the 100% constant one. Whatever the distance is, the lighting has theoretically the same intensity. This is the kind of (non-)falloff used for the sun lighting, it is so far away from the map area, that light rays are supposed to be parallel and light keep its intensity. Constant falloff is also useful for fake lights, lights with a very low brightness but that are here to brighten up the area.
     
     

     
    Linear falloff

    Another type of falloff is the 100% linear one. With this configuration, light seems to be a bit artificial: it loses its intensity but goes way further than the 100% quadratic falloff. It can be very useful on spots, the lighting is smooth and powerful. Here is an example:
     

     
    Quadratic falloff

    This is the default configuration for any light entity in Hammer, following as we said before the classic Inverse-Square law (100% Quadratic Falloff). It is considered to be the most natural and realistic falloff configuration. The biggest issue is that it boosts the brightness so much on short distances, that you can easily obtain a big white spot. Here is an example, with a light distant of 16 units from a grey wall:

     
    This can also happen with linear falloff but it is worse with quadratic. Simple solutions exist for that, the most common is not to use a light entity but a light_spot entity that is oriented to the opposite direction from the wall/ceiling the light is fixed to. You can make the opening angle of your light_spot wider, with the inner and outer angle parameters (by default the outer one is 45°, increase that to a value of 85° for example). If needed, you can also add a light with low brightness to light the ceiling/wall a bit.

     
    50% & 0% FallOff
    A second light falloff system exists, overriding the constant-linear-quadratic system if used. The concept is much simpler, you have to configure only 2 distances:
    50 percent falloff distance: Distance at which light should fall off to 50% from its original intensity 0 percent fall off distance: Distance at which light should end. Well ... almost, it actually fall off to 1/256% from its original intensity, which is negligible. The good thing with this falloff system is that you can see the 2 spheres according to the 2 distances you have configured in Hammer. Just make sure to have this option activated: 

     
    Models lighting
    An appropriate section for models lighting is needed, because it differs from brush lighting (but the falloff stays the same). In any current game engine, lightmaps can be used on models, a specific UV unwrap is even made specifically for lightmaps. But on Source Engine 1 (except for Team Fortress 2) you cannot use lightmaps on models. 
    The standard lighting method for models is named Per-Vertex Lighting. This time, light won’t be lighting faces but vertices, all of the model’s vertices. For each one of them, VRAD will compute a color and brightness to apply. Finally, Source Engine will make a gradient between the vertices, for each triangle. For example:

    If we take a simple example of a sphere mesh with 2 different light entities next to it, we can see it working.
                
    With this lighting method, models will therefore be integrated in the environment with an appropriate lighting. The good thing is that, if a part of the model is in a dark area, and another part is in a bright area, the situation will be handled properly. The only requirement for this is that the mesh must have a sufficient level of detail in it; if there is a big plane area without additional vertices on it, the lighting details could be insufficient. 
    Here is an example of a simple square mesh with few triangles on the left and a lot on the right. With the complex mesh, the lighting is better, but more expensive. 

    If you need a complex mesh for your lighting, you don’t want your model to be too expensive, you have to find a balance. 
    Two VRAD commands are needed to make the Per-Vertex Lighting work:
    StaticPropLighting StaticPropPolys You have to add them here. You can find more information here.
    Another system exists, that is much cheaper and simpler. Instead of focusing on the lighting of all the vertices, the engine will only deal with the model’s origin. The result obtained in-game will be displayed on the whole model, using only what has been computed at the model’s origin location. This can be an issue if the model is big or supposed to be present in an area with lots of contrast in lighting. The best example for that is at the beginning of Half-Life 2 with trains entering and exiting tunnels. We can see the issue: the model is illuminated at the beginning, but when it enters the tunnel it suddenly turns dark. And this moment is when the train’s origin gets in the shadow. 
    This cheap lighting method will replace the per-vertex lighting for 3 types of models:
    For prop_dynamic or any kind of dynamic models used in the game (NPCs, weapon models in hand, any animated models...) For prop_physics For ANY MODEL USING A NORMAL MAP (vertex lighting causes issues with normal maps apparently), EVEN IF USED AS A PROP_STATIC
    The big problem with these models is their integration in the map, they won’t show any shadow and their lighting will be very flat and boring (because it’s the same used for the whole model). But hopefully there are 2 good things with this cheap lighting method. 
    First, the orientation from which comes light is taken into account, if blue light comes from one direction, therefore all the faces oriented toward this direction will be colored in blue. And if you have different lighting colorations/intensities coming from different sides of your model, they should appear in game. 
    Here is an example of a train model using a normal map with 2 lights on both side. If you look closely, you’ll see some blue lighting on the left, on faces that are supposed to be in the shadow of the blue light but are oriented toward the blue light.
     

     
    The second good thing is that there is still some kind of dynamic per-vertex lighting, but much simpler: it only works with light and light_spot entities (NOT with light_environment), and it just adds some light to the prop, it cannot cast any shadow (it only takes into account dynamically the distance between the light and the vertex). If we use again the high-poly plane mesh we had before as a prop_dynamic, being parented to a func_rotating that ... rotates. Light is dynamically lighting the vertices of the props. There is a limit of 3 dynamic lights per prop, it can’t handle more at the same time.

    And if you add a normal-map in your model’s texture, this cheap dynamic lighting works on it:

     
    Projected texture and Cascaded Shadows
    Few words to finish the study with dynamic lighting. Projected textures is a technology that appeared with Half-Life 2: Episode Two in 2007, it consists of a point-entity projecting a texture in the chosen direction, with a chosen opening angle (fov). The texture is projected with emissive properties (it can only increase the brightness, not lowering it) and it can generate shadows or not. The great thing with this technology is that it’s fully dynamic, the env_projectedtexture can move and/or aim at moving targets. This technology is used for example on flashlights in Source games. But as usual, there is also a drawback: most of the time you can only use only 1 projected texture at a time, modders can change this value quite easily but on Valve games it is always locked on 1. 

    The cascaded shadows system is only used on CS:GO. The concept is quite similar from a projected texture but it doesn’t increase the brightness, it only adds finer shadows. It is used for environment lighting, using much smaller luxels than for the lightmaps and it is fully dynamic. It starts from the tools/toolsskybox textures of the map and cast shadows if it meets any obstacle. Shadows from the lightmap are most of the time low resolution and the transition between a bright and a dark area is blurry and wide. Therefore, the cascaded shadow will be able to draw a clear shadow around the one from the lightmaps.

    When an object is too small to get a shadow in the lightmap, it will be visible thanks to the cascaded shadows. There are 3 levels of detail for cascaded shadows on Counter-Strike, you can configure the max distance at which the cascaded shadows will work in the env_cascade_light entity at the parameter Max Shadow Distance (by default it’s 400 units). The levels of detail will be distributed within this range, for example: 

    Since cascaded shadows and projected textures share some technology, you can’t use them both at the same time.
     
    Conclusion
    I really hope you have found this article interesting and learned at least few things from it. I believe most of these informations are not the easiest to find and it’s always good to know how your tools work, to understand their behavior. Source Engine 1 is old and its technologies might not be used anymore in the future, more powerful and credible technologies are released frequently but it’s always good to know your classics, right? 
    I would like to thank Thrik and ’RZL for supporting me to write this article, and long live the Core!
    // Written by Sylvain "Leplubodeslapin" Menguy
    Additional commands for fun
    Mat_luxels 1                              // Allows you to see the lightmaps grids Mat_fullbright 1                         // Disables all the lighting (= fullbright). On CS:GO, cascaded shadows stay and you should delete them as well (cf next command) Ent_fire env_cascade_light kill  // KILL WITH FIRE the cascade shadows entity Mat_drawgray 1                        // Replace all the textures with a monochrome grey texture, useful to work on your lighting  Mat_fullbright 2                         // Alternative to Mat_drawgray 1 Bonus:
    Mat_showlowresimage 1           // Minecraft mode
  • After the announcement of the Reddit + Mapcore mapping contest, the website has welcomed many newcomers. A proof that, even if it is a twelve year old game engine, Source engine attracts map makers, and there are lots of reasons for that. It is common knowledge that technology has moved forward since 2003, and many new game engines have found various techniques and methods to improve their renderings, making the Source Engine older and older. Nevertheless, it still has its very specific visual aspect that makes it appealing. The lighting system in Source is most definitely one of the key aspects to that, and at the end of this article you will know why.
     
    About the reality...
    Light in the real world is still a subject with a lot of pending questions, we do not know exactly what it is, but we have a good idea of how it behaves. The most common physic model of light element is the photon, symbolized as a single-point particle moving in space. The more photons there are, the more powerful light is. But light is in the same time a wave, depending on the wavelengths light can have all kind of color properties (monochrome or combined colors). Light travels through space without especially needing matter to travel (the space is the best example; even without matter the sun can still light the earth). And when it encounters matter, different kind of things can happen:
    Light can bounce and continue its travel to another direction Light can be absorbed by the matter (and the energy can be transformed to heat) Light can go through the matter, for example with air or water, some properties might change but it goes through it And all these things can be combined or happen individually. If you can see any object outside, it is only because a massive amount of photons traveled into space, through the earth’s atmosphere, bounced on all the surfaces of the object you are looking at, and finally came into your eyes.
    How can such a complex physical behavior from nature be simulated and integrated into virtual 3D renderings?
    One of the oldest method is still used today because of its accuracy: the ray-tracing method. Just to be clear, it is NOT used in game engines because it is incredibly expensive, but I believe it is important to know how and why it has been made the way it is, since it probably influenced the way lighting is handled in Source and most videogame engines. Instead of simulating enormous amount of photons traveling from the lights to the eye/camera, it does the exact opposite. If you want a picture with a 1000x1000 resolution, you will only need to simulate the travel of 1 000 000 photons (or “rays”), 1 for each pixel. Each ray is calculated individually until it reaches the light origins, and at the end the result is 1 pixel color integrated in the full picture. 
    By using the laws of physics we discovered centuries ago, we can obtain a physically-accurate rendering that looks incredibly realistic. This method is used almost everywhere, from architectural renderings to movies. As an example, you can watch The Third & The Seventh by Alex Roman, one of the most famous CGI videos of all time. And because it is an efficient way to render 3D virtual elements with great lighting, it will influence other methods, such as the lightmap baking method.
     
    Lightmap baking
    OKAY LET’S FINALLY TALK ABOUT THE SOURCE ENGINE, ALRIGHT!
    A “lightmap” is a grid that is added on every single brush face you have on your map. The squares defined by the grid are called Luxels (they are kind of “lighting pixels”). Each luxel get its 2 own properties: a color and a brightness. You can see the lightmap grids in hammer by switching your 3D preview to 3D lightmap grid mode.

    You can also see them in-game with the console command mat_luxels 1 (without and with).
    During the compilation process, a program named VRAD.exe is used. Its role is to find the color and brightness to apply for every single luxel in your map. Light starts from the light entities and from the sky (from the tools/toolsskybox texture actually, using the parameter values that has been filled in the light_environment entity), travels through space and when it meets a brush face:
    It is partially absorbed in the lightmap grid A less bright ray bounces from the face Here is an animated picture to show how a lightmap grid can be filled with a single light entity:

    When you compile your map, at first the lightmaps are all full black, but progressively VRAD will compute the lightmaps with all the light entities (one by one) and combine them all at the end. Finally, the lightmaps obtained are applied to the corresponding brush faces, as an additive layer to the texture used on that face. Let us take a look at a wall texture for example.

    On the left, you have the texture as you can see it in hammer. When you compile your map, it generates the lightmaps and at the end you obtain the result on the right in-game. Unfortunately, luxels are much rougher, with a lower resolution, more like this.

    On the left you have a lightmap grid with the default luxel size of 16 units generated my VRAD, a blur filter is applied and you obtain something close to the result on the right in the game.
    In case you did not know, you can change the lightmap grid scale with the “Lightmap Scale” value with the texture tool. It is better to use values that are squares of 2, such as 16, 8, 4 or even 2. Do not go below 2, it might cause issues (with decals for example). Only use lower values than the default 16 if you think it's really useful, because you will drastically increase your map file size and compilation time with precise lightmap grids. Of course, you can also use greater values in order to optimize your map, with values such as 32, 64 or even 128 on very flat areas or surfaces that are far away from the playable areas. You can get more infos about lightmaps on Valve’s Wiki page.

    But as we said before, light also bounces from the surface until it meets another brush, using radiosity algorithms. Because of that, even if a room does not have any light entity in it, rays can bounce on the floor and light the walls/ceiling, therefore it is not full black. 
    Here’s an example:

    The maximum amount of bounces can be fixed with the VRAD command -bounce X (with X being the maximum amount of bounces allowed). The 100 default value should be more than enough.
    Another thing taken into account by VRAD is the normal direction of each luxel: if the light comes directly against the luxel or brushes against it, it will not behave in the same way. This is what we call the angle of incidence of light.

    Let us take the example of a light_spot lighting a cylinder, the light will bright gradually the surface - from fully bright at the bottom to slightly visible at the top.

    In-hammer view on the left, in-game view on the right
     
    Light Falloff laws
    One of the things that made the Source Engine lighting much more realistic than any others in 2004 is the light falloff system. Alright, we saw that light can travel through space until it meets something, but how does it travel through space? At the same brightness, whatever the distance is between the light origin and destination? Maybe sometimes yes… but most of the time no.

     
    Imagine a simple situation of a room with 1 single point light inside. The light is turned on, it produces photons that are going in all the directions around it. As you might imagine, photons are all going in their own direction and have absolutely no reason to deviate from their trajectory.
     
     
     
    At one time, let’s picture billions of photons going in all the directions possible around the light, the moment after, they are all a bit further in their own trajectory, and all the photons are still there, in this “wave”. But, as each photon follows its own trajectory, they will all spread apart, making the photon density lower and lower.
    As we said before, the more photons there are, the more powerful light is. And the highest the density, the more intense light is. Intensity of light can be expressed like this:

     
    You have to keep in mind that all of this happens in 3D, therefore the “waves” of photons aren’t circles but spheres. And the area of a sphere is its surface, expressed like this:

    (R is the radius of the sphere)
     
    If we integrate that surface area in the previous equation:

    With ♥ being a constant number. We can see the Intensity is therefore proportional to the reverse of the square of the distance between the photons and their light origin. 
    So, the further light travels, the lower is its intensity. And the falloff is proportional to the inverse of the square of the distance.
    Consequently, the corners of our room will get darker, because they are farther away from the light (plus they don’t directly face the light, the angle of incidence is lower than the walls/floor/ceiling).

    This is what we call the Inverse-Square law, it’s a very well-known behavior of the light in the field of photography and cinema. People have to deal with it to make sure to get the best exposure they can get.
    This law is true when light spreads in all possible directions, but you can also focus light in one direction and reduce the spread, with lenses for example. This is why, when Valve decided to integrate a lighting falloff law in their engine, they decided to use a method not only following the inverse-square law but also giving to mapmakers the opportunity to alter the law for each light entity.
     
    Constant, Linear, Quadratic... Wait, what?
    In math, there is a very frequent type of functions, named polynomial functions. The concept is simple, it’s a sum of several terms, like this:

    Every time, there is a constant factor (the “a” thing, a0 being the first one, a1 the second one, a2 the third one...), multiplied with the variable x at a certain degree:
    x^0 = 1 : degree 0 x^1 = x : degree 1 x^2 : degree 2 x^3 : degree 3 ... And
    a0 is the constant named “constant coefficient” (associated to degree 0) a1 is the constant named “linear coefficient” (associated to degree 1) a2 is the constant named “quadratic coefficient” (associated to degree 2) Usually, the function has an end, and we call it by the highest degree of x it uses. For example, a “polynomial of the second degree” is written:

    Then, if we take the expression from the inverse-square law, which was:

    With a2 = 1 and D being the variable of distance from the light origin.
    In Source, the constant ♥ is actually the brightness (the value you configure here).
    It is simply an inverse polynomial of the second degree, with a0 and a1 equal to zero. And we could write it like this:

    Or...

    And here you have it! This is approximately the equation used by VRAD to determine the intensity of light for each luxel during the compilation. And you can alter it by changing the values of the 3 variables constant, linear and quadratic, for any of your light / light_spot entity in your level.
    Actually you set proportions of each variable against the other two, and only a percentage for each variable is saved. For example:

    Another example:

    By default, constant and linear are set to 0 and quadratic to 1, which means a 100%quadratic lighting attenuation. Therefore, by default lights in Source Engine follows the classic Inverse-Square law.
    If you look at the page dedicated to the constant-linear-quadratic falloff system on Valve’s Wiki, it’s explained that the intensity of light is boosted by 100 for the linear part of equation and 10 000 for the quadratic part of equation. This is due to the fact that inverse formulas in equations always drop drastically at the beginning, and therefore a light with a brightness of 200 would only be efficient in a distance of 5 units and therefore completely pointless.

    You would have to boost your brightness a lot in hammer to make the light visible, that's what Valve decided to make automatically.
    The following equation is a personal guess of what could be the one used by VRAD:

    With constant, linear and quadratic being percentage values. The blue part is here to determine the brightness to apply, allowing to boost the value set in hammer if it is as least partially using linear or quadratic falloff. The orange part is the falloff part of equation, making the brightness attenuation depending of the distance the point studied is from the light origin. 
    The best way to see how this equation works is to visualize it in a 2D graph: 
    https://www.desmos.com/calculator/1oboly7cl0
    This website provides a great way to see 2D graphics associated to functions. On the left, you can find all the elements needed with at first the inputs (in a folder named “INPUTS”), which are:
    a0 is the Constant coefficient that you enter in hammer  a1 is the Linear coefficient a2 is the Quadratic coefficient B is the Brightness coefficient In another folder are the 3 coefficients constant, linear and quadratic, automatically transformed into a percentage form. And finally, the function I(D) is the Intensity function depending on the distance D. The drawing of the function is visible in the rest of the webpage. 
    Try to interact with it!
    This concludes the first part, the second part will come in about two weeks. We will see some examples of application of this Constant-Linear-Quadratic Falloff system, and a simpler alternative. We will also see how lighting works on models and dynamic lighting systems integrated in source games.Thank you for reading!
     
    Part Two : link
  • What is Agency?
    Just in case you have never heard of Counter Strike: Global Offensive, it's a hugely popular online FPS, successor to Counter Strike: Source and the original Counter Strike. The original came out in 1999 and the core gameplay has remained almost unchanged. Players are split into two teams and challenge each other in various game modes such as Bomb Defusal (one team has to plant and detonate the bomb while the other tries to stop them) and Hostage Rescue (one team must rescue the hostages whilst the other attempts to prevent that). The Bomb Defusal mode is by far the most popular, with maps designed with such detail that players can predict down to the second when another player is due to arrive in a certain area of the level. It's also the only mode played in competitive events and for huge prize money.
    This leaves the poor Hostage Rescue mode sitting on the sidelines twiddling it's thumbs and feeling a little rejected. In part this is because the Hostage Rescue mode is far more of a roleplaying experience, often with very poor odds of success for the team tasked with doing the rescuing. Often the levels are designed in such a way that the defending team has a large positional advantage, where simply staying-put will give them a good chance of winning.
    That's where we can start talking about Agency. Agency is a Hostage Rescue level, created as a collaboration between level designer Patrick Murphy, and myself doing the art. The basic idea being that Hostage Rescue could be just as precise and exciting as Bomb Defusal. It's been included in three official releases from the games creator, Valve, as part of their community level packs: Operation Bravo, Operation Phoenix and Operation Bloodhound. Phoenix being a community-voted choice, which was especially great to see that players enjoyed the style of gameplay and visuals that Agency brought with it.
    In this article I will go over the process of creating the art, from props to set dressing, texture creation and lighting, while maintaining a visually pleasing aesthetic and serving to enhance the gameplay. This isn't a postmortem but rather a walk-through of the various stages, hopefully to give some ideas to others, with lessons learned both positive and negative.

    Iteration from Whitebox to Final
    Starting out you should always have an idea of what you're going to create, even if it is quite vague, as it'll point you in the right direction for both creating architectural spaces and letting your imagination fill in the blanks as you build the basic shapes of the level. We knew we were going to build an office space, but style was leaning towards an older government building with red bricks and musty wood. As I started to put in some basic textures we decided it felt too bland, and similar to other levels in the game. In order to stand out and create something really interesting and intriguing that would entice players to want to explore the level we decided to modernize the space and use white as the primary colour - this would help players see each other more easily and provide a striking visual setting it apart from other levels.
    "Modern Office" is not exactly a style that has a single look, if you search for images you'll get back a lot of contrasting designs and ideas, trying to put every single one of those into a level would create a visual mess with no consistency. It's important to choose the right references for what you are building, something that looks cool in a single image or from a specific location might not fit into the theme of the level, and in a worst-case-scenario it might actually start to detract from the level as a whole. Trying to cram in as much content as possible simply makes your level feel less unified and jarring.
    Unfortunately when you are presented with so many fantastic designs and ideas it can be hard to pick out what is important. After settling on the location: a modern advertising agency's office, I broke down the needs of the level into a few different categories:
    Area Specific General Use Overall Theme The Area Specific content is "hero assets" for each location in the level. These are the things that help the player tell different areas apart from each other, a reception desk, a kitchen, a bathroom, etc. Assets that won't be used anywhere else except in their specific location.
     

    Examples of Area Specific Content

    The General Use content is the backbone of the building, it's wall sockets, ventilation tubes, sprinklers, desks and chairs. The things that could be used anywhere and would blend in to the background and not stand out unless you were specifically looking for them.
     

    Examples of General Use Content

    The Overall Theme content is what sells the theme of the level to players, advertising boards, company logos, large art installations and so on. These can be used everywhere but sparingly and should only be used as a subtle reminder to the player of where they are thematically. They shouldn't detract from the Area Specific content but should stand out more than the General Use content. This came in the form of abstract paintings, corporate logos, rotating advertisement panels and so on - things that would subtly tie the level together.
    Once these categories were laid out, searching through reference images became much simpler as you know what you need and only have to find an interesting design or detail that enhances a specific category.
    This isn't to say that everything was completely planned out or that development was flawless. Sticking to a plan only works until you open the editor, and if you try to force something you'll end up frustrated when it consistently fails to work. As an example we originally had the level set on the ground floor of a tall skyscraper. I spent a few weeks working on content for the ground but never really getting it to feel right within the theme of the level: the contrast between a dirty exterior street section and a spotless interior didn't feel right for the level, and felt a little too similar to another Counter Strike level. Patrick played around with some ideas and tried something I was afraid of: simply deleting everything I had done on the outside and adding an epic city vista. Instantly it felt right. The important thing to take away from this is that just because you have worked on something doesn't mean it's the right thing to be working on, and that getting input from other people with different ideas can vastly improve what you are working on.
     

    The first mockup of Agency's rooftop exterior
     

    The same space after an art pass

    Another incredibly important thing I realised is making use of modular assets. If you are going to duplicate something in your particular modelling software you should ask yourself: is this efficient? Chances are you're just making things harder to change later and locking yourself into a particular shape; eg: a walkway has a railing around it, you model the entire railing as a single object. Now if you need to change that walkway a month later you're going to have to go back and change your railing model. It's better to create a smaller tiling mesh that can be used multiple times, as often you'll find you can use that model in other areas and in different ways than you had initially intended. You're simply applying the concept of tiling textures to models, and in the process saving yourself a lot of time.

    A Believable Clean Art Style
    Creating a clean environment can often be more difficult and time consuming than a very dirty and cluttered one, simply because any mistakes are magnified by the lack of other objects to disguise them. A room with a single chair in the middle is going to end up with the focus being on that chair, if you fill that room with a hundred chairs you're going to be less concerned with the details of the chair and more worried about why someone would fill a room with a hundred chairs.
    In the modern office setting of Agency it would have made little sense to fill it with props and clutter, but a large empty space would just feel unfinished. A delicate balance of larger architectural shapes and smaller objects was needed. I like to think of this as functional art: it serves a purpose in the lore of the game world. Window and door frames, electrical sockets, thermostats and card swipes along with the maintenance apparatus of ventilation systems. These are the general use objects mentioned earlier, they fill out space and prevent an empty wall or ceiling from actually looking empty and at the same time they contribute to the believability of the level. It's important to think of the infrastructure of the building when placing these assets - if a wall has an air vent on it then the wall needs to be thick enough to support the ventilation pipes that feed it, Card swiping mechanisms need to be placed near doors at the correct height, electrical sockets should be placed logically in areas where they would be of use to the fictional inhabitants of the level and so on.
     

    Several examples of functional art details

    One of the most important things to do right when creating clean environments is to get the most out of the materials. It's not possible to cover every surface in dirt or decals, so the surfaces themselves become your way of showing detail.
    For Agency this was achieved by making liberal use of the phong shading techniques in the Source engine for models, and cubemaps for world textures. Almost all models in the level have some amount of phong shading, and although it doesn't produce a completely physically accurate result it can be used to create materials and surfaces that look relatively accurate. Simply by increasing or decreasing the intensity of the phong amount allowed for a vast majority of the levels surfaces to be rendered accurately. As I didn't need to have a lot of noisy detail in the materials due to the clean style I simply used a small phong texture as a mask for 75% of the models and let the lighting and general shapes of the models do the rest of the work.
     

    Simple phong shading to mimic real world materials

    As most of the surfaces had a single layer of material, ie paint or coloured metal, the phong shading could be completely even without breaking the illusion; however some of the dirtier surfaces such ventilation tubes and water pipes had several layers: a painted metal surface with area peeled away to reveal with metal underneath or a layer of dust. These had specific masks that would enhance the different materials, and showing wear and tear in the background assets added an extra layer of depth without compromising the clean style.
    Most of these textures were created with dDo, an excellent tool for quickly creating textures. I generally started with quite a dirty texture preset and toned down the details and noise until they were barely perceptible surface imperfections.
    Agency features probably close to 95% custom art, and that's a lot of work for a single person. Using dDo allowed me to make a lot of content relatively quickly, and kept it all visually consistent.
    The process of creating the assets with dDo was quite simple: first I modeled the basic ingame asset, then did a very quick and dirty placement of edge loops that allowed me to smooth the mesh and get a workable high poly. A very rough normal map was baked (along with a more solid ambient occlusion map), this rough normal map would never make it into the game, it was used purely for texturing with dDo. This rough-and-dirty technique was mostly used on the more general purpose assets that nobody would spend a lot of time looking at. For the objects that were in high traffic areas or that required finer detail a more robust normal map was created.
    Tiling textures used throughout the world were photo-sourced and tiled in Photoshop. A few examples worth pointing out are the plaster wall textures and the marble floors:
     


    The image above shows the ingame result, the diffuse texture, and the normal map of the standard plaster that is used throughout the level. The normal map was authored at 1024x1024 compared to the diffuse texture which was 512x512. I created several colour variations of the diffuse texture and for a very plain surface using a 1024x1024 diffuse didn't make much sense. The final touch was to add a subtle cubemap effect to bring out the normal map and add interesting coloured reflections in various areas.
     


    Another example is a marble floor used throughout the level. The normal map is unrealistic in that it portrays an uneven bumpy surface when in fact it is more likely to be uniformly flat. However to break up the reflections and add some visual interest to such a large and empty area I added a subtle bumpy normal map which warps the reflections, but is subtle enough that it doesn't get picked up by the lighting and actually appear like a lumpy mess.
    Good shading only gets you part of the way there, however. A poorly scaled model can break immersion instantly, especially when you are trying to create a believable real-world environment. There are tried-and-true metrics for Counter Strike so having a base to work from helped immensely, but these only give you a good starting point or a bounding box for your object. It's important to study real world reference and make sure your object is proportional to the world around it and also to itself. A unit in Hammer is an inch, so having wood that's 2 units thick, or a doorway that is 1.5m wide quickly makes things look wrong.

    Working with Designer Blockouts, and not Destroying Gameplay
    Agency was a collaboration, with Patrick doing the design work and me doing the visuals, this meant there was a lot of potential for overlap and working on the same areas, the potential for breaking things was huge.
    Often when you create things as an individual you don't have to worry about version control or stepping on someone else's toes, however when you work with other people either for pleasure or business you, as an artist, need to change your mindset. You are not creating a portfolio piece but rather something functional that has to withstand hundreds of hours of real people playing it.
    Your first role is to support the designer, and this benefits you as well. By creating the basic structures of the level: doorways, window frames, stairs, railings, cover objects etc, you are allowing them to work with the final assets and tweak gameplay according to those assets. Nothing needs to be finalized instantly, it's better to provide a rough mockup of the intended asset so the designer can play around with it and give feedback on the shape, size and silhouette. Once you are both confident it's going to work they can populate the level with these assets which saves you time in the long run, and once you finalize the model and textures they are going to be updated across the entire level without having to manually replace assets.
    It can be difficult to determine exactly when you should start an art pass, especially when a level is constantly evolving. Rather than sitting idly by whilst Patrick was ironing out the design of the level I started on the creation of a few visual test levels to explore materials, lighting and modular assets. Once the first iterations of Agency were created, with rough shapes for important cover and controlling lines-of-sight. I went in and created an art pass and altered many of these original gameplay ideas, simply experimenting with different shapes and designs for the rooms. We had a constant dialogue and never considered something finalized just because it was finished. Playtests would determine whether an idea was valid or not in a way that speculation can only hope for. The most important lesson learned during this process of constant iteration was that work is very rarely wasted, and it is far more important to stay true to a gameplay ideal than to have an area that looks interesting in a screenshot but utterly fails when players get their hands on it. A box is a box is a box, it is down to you as an artist to imagine how that box can be interpreted within the context of the environment.
     

    Initial art pass ideas for the central area (above) versus the end result (below)
     

    Initial art pass ideas for the reception (above) versus the end result (below)
     

    Initial art pass ideas for a hostage (above) versus the end result (below)

    Lighting
    An important part of any environment is the lighting. Too contrasted and moody and it becomes hard to identify players, too bright and monotone and it becomes boring and a strain on the eyes. For Agency I used a series of instanced lighting setups: a model to visualise the light source, a spot light to direct the light, and a sprite or light cone to add a visual effect around the light. Each light setup was unique to the type of model used for the actual light source, ie: all spotlights were identical, all fluorescent lights were identical etc. This meant I could change a single light and have the others update automatically, and always get an accurate result.
    Then it was just a case of placing these different types of lights where they logically made sense in the environment, and if an area was too dark an appropriate light source was added, and if an area was too bright lights could be moved around or removed entirely. This made it quite easy to light as everything was guided by reality, which has plenty of reference material, and had the side effect of helping to make the environment more believable. By using various colours on the floor and walls I could direct lights towards them and take advantage of the Source engine's excellent radiosity and spread interesting colours to nearby surfaces.
    In many areas the ceiling was opened up to reveal the sky and to let natural sunlight into the interior spaces, this was done to provide contrast to the electrical lights and to get extra radiosity bounces into the environment. Some areas had lights removed or toned down to allow other more important gameplay areas to stand out, for example the image below shows how the corridor here was darkened both by using darker textures and by using restrained lighting to make the room in the distance appear brighter as this is an area that enemy players will appear from.
     


    This could have been taken even further by possibly using emergency exit signs to add hints of colour to important gameplay areas and chokepoints. A consistent lighting language would have helped guide players during the first few times playing the level. There are some large open spaces that would have benefited from some coloured screens or lighting panels, or possibly making some of the larger glass surfaces tinted, to add a little extra colour and prevent such a monotone look whilst not being over-bearing or detracting from the realistic style of lighting I was aiming for.

    Final thoughts
    During the course of developing Agency I had a chance to learn a few things and come out the other end a, hopefully, better artist.
    So, what went well?
    The iteration process never had any hiccups, by using modular content and being prepared to discard ideas and art styles that weren't working we ended up with a better level. If we had tried to force the original idea of a ground-level government office we would have ended up with a completely different level, complete with underground parking lots and elevator shafts. Exciting stuff!
    The power of iteration cannot be understated, and understanding that a mockup or a blockout of a level is simply a temporary phase that doesn't represent the end result. Areas changed drastically between versions, sometimes due to design requirements, and sometimes of shifts in art style; but each version was better than the last, more refined and polished.
    What went less well?
    In direct contrast to the statement above, sometimes the iteration interfered with more important tasks. I got stuck on areas trying to get them to work instead of letting them sit for a while and returning to them later. I tried to force an idea for the exterior part of the level and it never felt right and consumed way too much time, when all it took was getting some outside perspective. Luckily during the process I learnt to trust designers when it comes to art, just because they might not build high poly meshes doesn't mean they aren't artistic.
    Another problem was building too much content completely unique for an area which meant when we inevitably changed things it became time consuming to shift assets around, and makes it less easy for others to re-use that content without creating an almost replica of the area it was designed for. These unique assets helped sell the realism of the level but made them harder to work with.
    Hopefully this has been interesting and insightful!
  • (Art by Thurnip)
     

    /r/GlobalOffensive and Mapcore are teaming up to grow Counter-Strike: Global Offensive’s mapping community!  

    Check out the reddit thread for this contest »

     
     
    The Big Reveal
     
    We’re hosting a map-making contest for original, competitive 5v5 bomb defusal maps AND competitively-minded hostage maps, open exclusively to mappers who have not yet had their work featured in a Valve Operation! 
     
    Older projects are fair game: now’s the perfect time to polish up that map you’ve been working on but never got around to finishing. Experienced Mapcore judges and prominent members of the Counter-Strike community such as Sadokist, Moses, DDK, James Bardolph, and Anders Blume will be weighing in – but only one map can win it all.
     
     
    Helpful Playtesting
     
    Every week for the length of the contest, eligible maps will be playtested during /r/GlobalOffensive community nights according to a sign-up schedule. Slots on this schedule will be filled on a first-come, first-serve basis following an approval process, but we will try our best to accommodate everyone at least once. However, because it’s impossible to guarantee that all contest entries will have the chance to be playtested, /r/GlobalOffensive playtesting is a supplemental, helpful tool which will have no bearing whatsoever on contest judging.
     
    You can register for a playtesting slot here. Remember -- playtesting registration is first-come, first-serve!
     
     
    Enter Your Level
     
    To officially enter your level into this contest, post a WIP thread with a link to your level’s Steam Workshop page in Mapcore’s official event forum.
     
    Posting a WIP thread with a link to your level’s Steam workshop page constitutes your official entry into the contest, however you don’t need to do both at the same time. In other words, you can post your WIP thread and then update it later with your workshop link if you’re not ready to go right away. You can also feel free to continue updating your workshop level after you’ve posted your workshop link – contest entries will not be judged until after the submission deadline.
     
     
    The Deadline
     
     
    Your level must be submitted to Mapcore by August 31st, 2015 at midnight Pacific Standard Time (PST).
     

    Our panel of judges will then select four finalist levels based on the following criteria:
    Fun factor Visual/thematic presentation (graphics) Overall polish
    Grand Prize Deadline
    After the top four maps have been announced, /r/GlobalOffensive users will put them to the test!
    Once all four finalist maps have been tested, mappers will have two weeks to revise their work based on community feedback. After those two weeks, an official Grand Prize Winning Map will be chosen!
     
     
     
    Contest Calendar
     
     
     
    Our Goal
     
    The goal of this event is to raise awareness about Mapcore's incredible level design community and the incredibly useful playtesting capabilities of /r/GlobalOffensive. Both Mapcore and /r/GlobalOffensive are free resources available to all mappers. To date, Mapcore users are responsible for creating more than 70% of Valve Operation levels. Mapcore’s staff are unpaid volunteers, and do not personally profit in any way from additional traffic to the site.

    Prizes
     
    Of course, it wouldn’t be a contest without a reward… In addition to the helpful feedback and free publicity that CS:GO mappers will receive by participating in this event, each finalist will also receive:
    Eternal Bragging Rights™ and a showcase on Mapcore (where their level will be highly visible to industry-veteran game developers and the rest of the community) A monetary prize ($1000 + Mapcore swag for first place; $400 for second place; $200 for third place; $100 and Mapcore swag for fourth place) The top-finishing map will also be played in a competitive show-match casted and streamed by goRGNtv, for all to watch and enjoy! *NEW* CEVO has generously agreed to host the winning map in their PUG rotations for one month! *NEW* Added $1,000 to prize pool thanks to Gamebanana.com and EGO DEATH (gun skin creator) *NEW* Valve prizes!  
                       Top 4 will receive
    1. Signed CS:GO poster
    2. CS:GO Lanyard
    3. CS:GO Vinyl Sticker
     
             First place will receive a CS:GO prize pack:
    1. Signed CS:GO poster
    2. CS:GO Lanyard
    3. CS:GO Vinyl Sticker
    4. CS:GO SteelSeries Kana Mouse
     
     
    This is your big chance -- get to it!
    Good luck, mappers!
     
    Additional Rules
    Remakes of older maps are NOT allowed. All works must be original to you and their layouts must not have appeared in any prior versions of Counter-Strike. Custom artwork is allowed and encouraged, but must meet workshop guidelines. Collaborations are allowed and encouraged. Any contest winnings arising from a collaboration will be split in accordance with the collaborators' mutual agreement.  
     
    Judging Procedure
    Mapcore staff will rate their top four maps of the contest, results will be tallied and all votes given equal weight. Some time later, the judges and guest judges will rate the top four finalist maps and results will be tallied, with all votes given equal weight. Guest judges will be asked to act as tie-breakers in the event of any ties in the voting.  
    Mapcore Judges
    Jason “General Vivi” Mojica -- Creator of "Rose Iron" Skin (Overkill Software)
    Patrick "Puddy" Murphy -- Creator of CS_AGENCY (Overkill Software)
    RZL (Independent) -- Creator of DE_RESORT
    Shawn “FMPONE” Snelling (Independent)
    Johnny “Sprony” van Spronsen (Journalist)
     
    Guest Judges
    Matt "Sadokist" Trivett -- @Sadokist
    Jason “Moses” O’Toole -- @JmosesOT
    Daniel "DDK" Kapadia -- @followddk
    James Bardolph -- @jamesbardolph
    Anders Blume -- @OnFireAnders
     
    ---
    Our Thanks to 
    EGO DEATH (Steam Workshop author)


     
     
     
  • Now that you've had a month to digest part one of Sentura's dive into the lovely world of Unreal Engine 4, it's time to get your teeth into the second part. This time, discover the wonders of debugging, comparisons, and casts. Also, feel free to use the comments to ask further questions about this tutorial or Unreal Engine 4 in general.
    Picking up where we left off, let’s take a look at debugging, comparisons and casts.
     
    Debugging
    There were some issues with our door example in Part One, which I glossed over for the sake of simplicity. Now, however, our door should serve as a useful example of how to debug blueprints.
    The problem was that our door didn’t really open properly, as seen in this image:
     
      Let’s figure out what’s wrong with some debugging.
    There are many methods of debugging blueprints, of which Breakpoints are the most common. Setting a breakpoint stops execution of your game momentarily, allowing you to inspect the nodes of a blueprint graph. This is tremendously useful for squashing any troublesome bugs.
     
      Breakpoint debug steps:
    Add a breakpoint. Play and execute the event (the game pauses and focuses on your breakpoint). Use the step button to go through the execution step by step. After a few steps in our door example, we see that both of our events are being triggered repeatedly. We can also hover over any variables and parameters to examine their specific values at the time of the break.
    Another method of debugging is to split your screen (or simply use two monitors), separating the blueprint window from the game window. This helps track what’s going on in the graph as you walk through your door. This way, we can see the exact point the execution reaches while we play the game, although we aren’t provided with any additional information.
    Notice that the drop down menu next to the play button in the blueprint graph window needs to be set to our specific door in order for it to display any information about the door.
     

     
    Both of these debugging methods help us trace the root problem with our door example: events are registering repeatedly, causing the door to behave erratically. One guess as to why this may be occurring, is that some native player character components are interfering with the door blueprint by forcing it to register more than one actor.
     
    Comparisons
    How can we single out an object or actor to ensure that it’s the correct target of a sequence? How can we ensure that any given object or actor is actually the intended type, in order to avoid problematic misidentifications? These are questions which can be answered using comparisons.
    Comparisons are, just as the name implies, a way for us to compare objects in order to determine whether or not they are alike. UE4 determines the result of this comparison with a boolean value – either the objects are the same (a boolean true value) or they are different (a boolean false value), and we can then use this boolean as an indication of what to do with our door. In UE4, conditions are done through the branch node.
    The node used for comparisons is called “Equals”. Note that there are several versions of the “Equals” node, as it can be used for almost all possible variable types.
     
      Now that we have our Equals nodes, we want to make sure that they are configured correctly. Each event needs an equals node, taking the ‘other actor’ parameter and comparing it with the player controlled pawn – our First Person Character actor. While you can link the First Person Character actor through other ways, doing it this way ensures that even if we change the player actor to something else, the door condition will still hold true.
     

     
    This solution wraps up nicely and leaves no room for error. But it is also somewhat limited: What if we also want to make potential enemies pass through the door?
     
    Casts
    Casting is a term originating from the computer science concept of polymorphism. In short, polymorphism is about class relationships, and how some classes may have a more generic version of themselves stored to use for implementing a variety of classes within the same skeleton. The generic class is called a superclass, whereas the class inheriting data from the superclass is called a subclass.
    The classic example of this is that a Car subclass would have a more generic Vehicle superclass. In games, this idea is even more widespread: we could have a Weapon superclass able to shoot and reload, but what happens when the weapon shoots and reloads would be up to the subclass. An RPG subclass would naturally have a different implementation than a SMG subclass, although it would share attributes like ammo and functions such as shoot or reload. Subclasses still have their own independent functions alongside inherited functions.
     
      How is any of this relevant to Blueprint? In short, a subclass inherited from a superclass may be targeted through its superclass. If you cast to a Weapon superclass, then any of Weapon’s subclasses can pass through as well.
    Let’s tie all of this together: using the superclass of First Person Character Character, we could ensure that all classes inheriting from Character are able to use a door as well – including our currently nonexistent enemy characters.
     
      There is a caveat: casts are performed during runtime. This means objects or actors which cast incorrectly could crash or otherwise break your game. For a more technical understanding of why casts should be used carefully, I recommend this article: http://stackoverflow.com/questions/4167304/why-should-casting-be-avoided
    So far, we have only briefly touched upon the concept of polymorphism, but it is one of the most important concepts within an object oriented programming paradigm such as Blueprint, and a great tool for creating system architecture (including system design).
    There is no article for polymorphism in UE4, and I’m tempted to write a comprehensive guide. In the meantime, you could take a look at this short video explaining the concept more thoroughly:
    Video no longer available on youtube
    In the third and final article in this series, we’ll implement a grenade weapon (using some polymorphy) and a grenade throwing mechanic using Bezier curves.
    See you then!
×