WIP Update 1 (MAD)

I've been doing a lot of custom scripting in Unreal Kismet and trying to learn a lot on my own. So far, I have fleshed out the basis for what will be the sewer and canals areas. I have setup a general AI for an enemy soldier which I have already used in more than one occasion. I have also decided to make a friendly NPC, at the first of the level -- when the player is defenseless -- to break the monotony of shooting. For example, I have a simple quest where the player meets a bot and the bot informs them that they have lost their key in the sewer and will help the player find a gun if they return the key. Once the key is returned, the npc moves to the location of the door, and unlocked sound it played, the lock actor is destroyed, and matinee moves the door open. Then, the trigger is teleported inside of the storage room, and the will be activated to cue a new voice clip from the npc. Staying on schedule, I am supposed to have all the modeling finished by tomorrow. I keep adding new ideas, though, and models pretty much come up needed. I plan to start doing some heavy texturing in the following weeks, while still adding more bots for the player to interact with. I have scaled the project in half, and the level will end when the player gets into the elevator to the next area. Here are screenshots of my current progress:

Single Player Level in Unreal

I've been working on an AI system for Unreal using kismet. So far, I have come up with the idea to attach a trigger to the bot's head joint, which is acting as their range of view. If the player is within the trigger's collision range, the bot will move toward the player. Since the bots run so fast, I have the bot pause for a second, and then they will fire at the player. If the player is still within the range of the trigger after the bot has paused, the bot will again follow the player and loop again. If the bot doesn't see the player again, the bot will then return to their patrol (this part still needs work in order for the bot to find his original path, since they will not go around blocking meshes or BSP). As far as I know, this is a completely new way to make single player AI in Unreal and I am excited to add it to my new level.

New Level Concept, MAD: Mutual Assured Destruction

I've been wanting to make a TC (Total Conversion) level for a while now, since I am more familiar with Unreal. I will probably be unable to contribute custom characters or guns, due to time restraints. I really want to focus on art AND gameplay in this new level, to show that I am competent in both modeling and level design. I am indeed an artist, though, and enjoy more of the lighting, modeling, texturing, and asset placement as opposed to scripting and white boxing levels (although I feel proficient in these, too). I am focusing my new level on a single-player style level for Unreal 3 and already have some simple AI systems that I've been working on to contribute. My major predicted obstacle is changing the core game mechanics: player ground speed, jump height, and ability to dodge. I have been researching mutators and have tried created a simple one to control these parameters, but to no avail. If all else fails, I will cater the level so that it works with both Unreal mechanics or any other.

Here is my concept:
-Based off the first Metal Gear Solid and ambiance of the Bourne Trilogy movies
-Player has to infiltrate a nuclear warhead/biological weaponry facility (not the most original, but I am planning on creating a fresh spin to the atmosphere and gameplay)
-There will probably be only a couple of guns -- stealth being the primary objective -- so a pistol with a silencer should suffice (again, this may have to change do to skill restrictions at the moment)

I am anticipating this level to take roughly 7 weeks to finish and will update any progress once I start production.

Level Finished

I officially finished the level on 9/16 and have uploaded it to my website and FileFront.com under the name DM-FeatureCreep. I also heard back from Gamespot and my first level, Ebb, is now on the site (Feature Creep Download).

Note to Self

I've noticed that map sizes significantly decrease in size if lightmapping was occupying a large portion of that size. My first try was a level that went from 68.9MB (uncooked) to 45.5MB(cooked). In the newest revision I decided to be more liberal with the lightmap sizes, and got a map that was originally 77.5MB(uncooked) to get down to 47.9MB(cooked). If you were wondering about the math behind that, it's:

45.5MB / 68.9MB = .66

47.9MB / 77.5MB = .62

.62 + .66 / 2 = .64

This means that the lightmap size after cooking decreases by roughly 34%. Pretty nifty, indeed. I will definitely be using this formula for my next map to calculate file size :).

I went ahead and cooked my level at my school (thankfully they have Unreal 3). I had decreased the lightmap resolutions all around so that my map was around 70MB... a reasonable number. Whenever I cooked it, the number dropped to a very pleasurable 45MB :)! This got me to go back and scrutinize areas that had discrepancies with lighting (in the form of whitish bands in between 2 side-by-side meshes). Right now I have increased the lightmap resolution of the most important areas, and it seem that a lightmap of 64 and above is recommending for lightmapping -- anything below isn't worth lightmapping, as it makes the mesh look even more screwy than before. I will be recooking the map later today and hopefully it will be released today.

I've finished the version of my rain/city map. I call it DM-FeatureCreep. I've had one friend play test the level near completion and just had another friend play test the final version. He gave me a couple of small things to change and I've gone ahead and changed those. I've been having problems cook the map so I had to use one of those friends' computer to cook it. The only problem is that he is running the game without the version 1.3 patch, and, when I try to play on my computer, the game shuts down for some reason. This may relate to the previous problem of not being able to cook the map, though.

I've also been thinking of a concept of light up shoes. I know there are already shoes such as the pair of L.A. lights that I had when I was a kid, that flashed red when the wearer steps down, but I am thinking of a more adult and futuristic version. When the user steps down, white light turns on in a line until the whole bottom of the shoe is lit. If the wearer stands in one place for a duration of time -- say, 15 seconds -- the light would, to conserve energy, blink in a pre-programmed pattern and then fade out. I was thinking that this would be a cool dynamic to a survival/horror game where everything is usually under lit. Light could be use to harm or scare away monsters, such as vampires, and so that enemies couldn't get too close to the player (unless they stand still too long :) ).
To execute this, I would plan on connecting a dynamic white light to each foot bone and running a test so that the light would only turn on if the foot was flatly colliding with another collision box (this way, if a player where to kick something or jump next to a wall (and there foot happened to brush against it), the shoe would NOT light up. It would light, though, if the player managed to do a running back flip off a wall or while jumping platforms, etc. I will be coming up with a few concept sketches in a later post.