Like I said in the previous post, for some reason there’s a huge timeskip in these progress images.  Also, we skip 18 for some reason.  I have no idea what happened there, but now it’s on purpose.  I’ll probably need to take some screen captures of some of the other features I implemented between this and the 17_X images and then screw up the chronological order completely.

So, this was the implementation of emissive mapping.  A lot of terms get thrown around to mean the same thing when we start talking about this, and also a lot of different, but similar, concepts start to get referred to with the same terminology.  So, it gets confusing.  For my purposes, emissive mapping refers to the process of taking an artist made texture and applying it along uv coordinates to meshes to denote sections of the model that are light sources and therefore glow.  It was a pretty simple feature to implement, but in doing so lead to a breakthrough in my glow mapping (runtime generated glows) that will end up being the basis of the next image post.

Also, you’ll notice some point lights here.  I probably won’t cover those in their own post because they were part of an extremely limited implementation that I’ve since discarded in favor of implementing a light pre-pass system.  But let’s not get ahead of ourselves here!

This image was taken on 2/3/13.

These are actually the last progress shots I have for the semester.  While my memory on why is a little hazy, I’m going to claim that it was an intense semester for me and finishing all of my other classes and getting things implemented in the graphics engine was enough work without having to remember to take new progress shots.  Yeah, that’s the ticket.

So, there isn’t necessarily any big new features being documented in these image captures. My artists and producer wanted new progress shots so I took some that showed overall progress rather than any individual feature.  What I can claim here is that shadow mapping was cleaned up a lot to provide better, crisper shadowing.  Also, I had just tracked down a bug in my asset caching system; the system worked perfectly until it tried to cache mesh data between frames.  Something about what DirectX does while state changing between render frames caused bizarre vertex deformation when I tried to cache between frames.  While the bug had presented in multiple ways that weren’t obvious for months, I had finally tracked it down and solved it simply by forcing a recache at the start of each frame.  I was simultaneously pleased that I had solved it and angry that it had taken me so long to figure out the root issue.

Also, most of these images don’t do a great job of capturing the state of the graphics engine.  One makes it look like the scuttle casts no shadow and one is a goofy capture of what happens when you toggle wireframe mode with glow outlines active.  But, here they are anyway.

These images were taken on 10/25/12.

This is a quick video I put together after our Prototype milestone presentation.  There’s nothing major going on here graphically that wasn’t already touched on in previous posts, but it’s the first implementation of game mechanics and it looks much better than anything previous with updated assets from Ian.  It’s also the first good look at all of the graphics tech that I’d built being used together since the last milestone’s video.

This video was taken on 11/1/12.

So, this was taken on the same day as the last screen capture.  I made some modifications to the glow outline system so that different outline colors could be handled simultaneously and specific objects could be set to glow.  This made the system viable for use as the designers wanted.  However, you’ll notice that the glows are still not blended correctly.  Turns out that sometimes I’m just really dumb about things.

Also, I fixed shadow mapping to use an orthogonal projection at this point so the shadowing improved greatly.

This image was taken on 10/15/12.