It was a very fun and productive day!

Play The Game Here! (May take some time to load)

Once again, I’m going to honest (and critical) and try to make this mega-post interesting!

PLAY THE GAME HERE

My goals for Ludum Dare 22

• Before the competition started, I had some goals in mind that I wanted to make.

1. I wanted to make sure “Fun” was the best category, so that people could replay the game, and have a good time playing.
2. I wanted the gameplay to be smooth and the animations smoother.
3. I wanted to beat Notch in at least one category (knowing how hard that would be).

What software I used

• Unity 3d Game Engine
• Blender 3D Modeling Software
• Pixlr Photo Editor
• Cfxr Sound Generator
• Unitron Script Editor
• Garageband Music Creator
• Text Edit Text Editor

How I made the game

• I quickly had come up with an idea for each of the most likely themes before LD22 started. My theme for “Alone” was a game where you would be sometimes alone, and then all of a sudden, you would be crowded with people.
• After the theme was announced, I decided that the game would be first person (the easiest of all the persons) and that you would have to fight your way through endless hordes of cubes (the easiest of default shapes). You could only see the cubes when your glasses were on, but if you weren’t in a shaded zone when your glasses were on, you’d start burning. This was a way to keep the player moving, and a way to make them constantly nervous.
• I worked on the player controls and LockCursor, etc. But the gameplay does not complete a game. I needed an enemy. One that would appear only if your glasses were on.
• I whipped up a cube model and texture and soon came up with this:

• Whoo Hoo! Now I have a cube!
• Next I worked on making the cube look at the player, and then having it disappear when the players “glasses” (A semi-transparent plane) were off.
• By now my Unity Scene looked like this:

• Soon I got Health implemented, and then it started to look like a Test level.
• I kept at it, knowing it would soon look like a game.
• The cube could soon move towards the player, and deal damage at close range.
• The first “Shaded Zone” was created, (using a Trigger) and the player would not take damage while inside it.
• I worked on making the zone a little prettier, and expanding the floor plane. I added a skybox, and changed the ambient light to near black.

• All along I had been slightly working on a music track, but now I decided I needed to finish it.

• The level was extended, the cube had a spawn code and could replicate itself, and the textures for walls and the floor was created in Pixlr.
• I created a variety of sound effects in CFXR like jumping and enemy death noises (my favorite).
• I worked on making an in-game tutorial, by timing when the music starts with the same time that it tells you that there is no one there.
• The menu was easy, all I had to do was come up with a name and choose the font, and soon my game looked legit. (Sorry for the lack of photos here)
• I asked my friend if he could play a test version on his computer (a windows) and I’m glad he did. The font I chose was bugging out on his computer, so I changed it to something else, and it worked fine.
• Now I knew my game was compatible on Windows AND Mac

• I created another music track for the menu, a helicopter to go to as the goal, and a stats screen so you could try to beat your own score.

Rating Other People’s Work

• I specifically rated the games that had the fewest ratings and tried to give most of them a fair, solid score.
• Mostly I gave 3.0s when I thought something was average.
• For a few people that put little effort into it, I had to give some 1.0s.
• I was sad that Notch had not really implemented the theme and pretty much made a different version of Minecraft. (Most likely this was just because he wanted to, or he felt like it.)

How people rated my game

• I can thank my friends, family, and Ludum Dare community for playing the game and enjoying it, especially DontBeNoobish‘s Gameplay Footage:

• I was proud with how my game turned out compared to most of the other entries.
• People mostly liked the audio and innovation of the game, but there were a few things I could’ve made better (More enemies, options, etc)

The Results!

• Coolness – 52% Bronze medal | At first I thought that the bronze medal meant third place, but then I realized Coolness didn’t have the same rating system. Oh well, it was still good to see that my playing of all those low effort games went to good use!
• # 40 Community – 3.55 | Wow! Community? I didn’t realize I was that popular! I guess this rating makes sense because of all the excited posts I made with links to this game. I did a LOT outside of the game (Time-lapse, post mortem, gameplay video, tips)
• # 108 Innovation – 3.20 | Good, people liked my idea of the sunglasses and whatnot!
• # 113 Mood – 3.20 | I think the music accomplished the overall feel of the game.
• # 118 Audio – 3.00 | Once again, the music, but also the enemy death noises made this count.
• # 113 Theme – 3.33 | Well, you are sometimes alone…
• # 202 Humor – 2.29 | I wasn’t even going for this (other than the ReadMe) so I have no clue how it ended up higher than overall.
• # 323 Graphics – 2.67 | Although mine was one of the few 3D first person games, I guess people didn’t really like the low effort GUI and enemy textures.
• # 435 Overall – 2.50 | Oh no! Overall score seemed like an important one…
• # 487 Fun – 2.06 | Really? This was the category I was focusing on, but yet it got a 2.06! Yes, I guess I did better than almost half of everyone else, and I’m not complaining, but this ended up at the bottom of the list, when I had worked for it to be the top.

Comparison To Notch

• My goal was to beat Notch in at least one category, and it turns out that was too easy:

• I ended up beating Notch in 7 different categories!
• A comment on the community rating: Last LD, Notch won third place (if I recall correctly) in the community category, but now he received a #49! And I received a #40! So after all the years Notch has spent on Ludum Dare and Minecraft, and the entire fan-base he collected from the Top Computer Game Of 2011, I was able to receive a better score than him from 3 weeks of posting on Ludum Dare!

I send out a huge thank you to all who rated my game (yes, even those of you that got me that horrible “Fun” score) and hope to join again for LD 23! Please remember Rob Productions again for next Ludum Dare, and you can expect a post-compo version coming in time!

Links:

TIPS ON MAKING A UNITY GAME

POST MORTEM

TIMELAPSE

THE GAME AGAIN

I just upload a tiny video from the creation of the game.

Mr. Treevil’s Lonely Heart – Timelapse – José Eduardo Terán

And you can play the game here:

Mr. Treevil’s Lonely Heart

Thanks for watching.

For our programming timelapse, go here: http://www.youtube.com/watch?v=-cU2_m4gkz8&feature=youtu.be

For our art timelapse, go here: http://www.youtube.com/watch?v=hb6UBkAgrfg&feature=plcp&context=C3854edbUDOEgsToPDskJvdVApGT52a5yIinw4kVse

Please play and rate us here: http://www.ludumdare.com/compo/ludum-dare-22/?action=preview&uid=7415

We hope you enjoy!

Actual thing here.

Super busy trying to win this, but still rating like mad when I can. Seriously, would a 3-month rating period really be all that bad? I don’t think so.

Happy ho-ho days! Hope you get to stuff all the stockings your heart desires

Alone In Space… Timelapse

And a Gameplay Video:

Alone In Space… Gameplay

To Play or Rate Alone In Space… Click Here.

I am very proud of the result.
We are talking about this.

The Good

• The idea — I had a pretty strong image of what I wanted to do in my head. It wasn’t very innovative, but I was sure not to stumble into a situation that I did not know how to get out of.
• The language — Using C++/SFML has been great. I considered using HTML5/JavaScript at the beginning, but now I am very happy that I changed my mind. Everything went smoothly and none of the expected cross-platform issues arose (even though I did not have the time to package it for Linux, yet).
• The tools — I used Photoshop for graphics, SFXR for sound effects and the NetBeans IDE. I did not have trouble with any of them. Everything worked like a charm.

The Bad

• The time management (who would have expected that?) — Everything went nice until I hit a very ugly bug in my collision/line-of-sight-detection system and got stuck. That caused me to loose many hours, resulting in limited content. I should have skipped it to deal with it at a later moment in time.
• The planning — I should have laid out more of the game before starting. I had to re-do my map system after discovering that it simply would not be fast enough to edit the map in Photoshop. I could have avoided that by realizing that a tile-engine would fit my needs best at the very beginning.
• The communication — Even though the IRC was permanently running on my second screen, I totally missed to socialize with other participants. I also planned to post status updates with screenshots on the blog, but that did not happen either. This will change next time!

Nonetheless, I am really happy with how everything turned out. I could adjust my path in time, so that the game ended up being fully playable, even though some planned content was missing.

Please feel free to play and rate my entry here!

Finally, here is my timelapse for this LD:

Also, NO DAMN KITTY IN MY GAME!

Found out I’m not good with video editing software.  Just another thing I’ve learned from this compo…

Timelapse of Alone in the Mansion on Youtube

Here is the link to the original entry.

Edit: I also put up the soundtrack if anyone wants to check it out!

What Went Right:

Time Management…?
I was able to plan out most of my time pretty well, so thankfully I was able to implement nearly all of the features I wanted, with just a few minor ones going undone. I spent about 5-6 hours on audio, probably roughly the same on graphics, and the rest coding, which is about what I expected (and planned) going into the weekend.

Audio
I was already pretty experienced in making this style of music (and making music in general, which I’ve been doing since 2004) so it wasn’t too horrible of a prospect to make a bunch of game tracks in a short amount of time. Having done a whole ton of album-a-days (http://crapart.spacebar.org/aad) helped on that front too – thanks Tom 7! Trying to come up with a variety of original material was probably the most creatively difficult aspect of the whole weekend but I’m really happy with how the music came out. And of course, working with bfxr was a pleasure.

What Went Wrong:

Game Balance/Playing My Own Game
I think the biggest issue with the game as it stands is the balance or difficulty – depending on how you play it, it’s probably either way too easy or way too hard. This wasn’t really obvious to me until around Sunday when I little else to do but play my own game and do lots of polish. It’s kind of funny to think that I didn’t spend enough time playing my own game in a 48-hour game dev competition, but it actually makes sense, especially considering the sort of game I was going for. I’ll try to keep this one at the forefront when I do my next Ludum Dare.

Slight Unfamiliarity with Tools
This wasn’t too much of an issue, but I had to look up a few XNA-related things to implement certain features, particularly graphics-related ones. I also struggled with GIMP a bit, which is probably understandable to anyone who has ever used it.

All in all this was an awesome experience. Can’t wait for the next challenge!

I made the game Space Rescue Mission. I am pretty happy with how everything turned out, except that my game was very buggy. This was my first Ludum Dare  and I should have managed my time a lot better. Anyway, looking forward to the next compo!

LD22 Timelapse

This is the time lapse of the full 48 hours of development, trimmed slightly so you don’t have to wait 30 seconds while I’m sleeping.

I like the concept of a timelapse, it makes it look like I know what I’m doing when I code something, as opposed to making it up as I go.

And again, if you could please play and rate my game, as well as leave any constructive criticisms, that would be greatly appreciated.  Thanks

The entry page.

• http://www.gavpugh.com/2011/12/21/ludum-dare-22-postmortem-journal-and-timelapse/

So, this past weekend I participated in the 22nd Ludum Dare competition. You have just 48 hours over the weekend in which to create a game. The crux of the competition is that you create all code and content within that 48 hour period. No re-used assets at all. Only engine/middleware/framework code is permitted to be prepared beforehand.

I wrote my game with Unity. It’s the first project I’ve ever undertaken in Unity, and I had very little experience of it. I came out of the other side with a very positive impression, I really liked using it. As much as I love C/C++; given the time constraints, it seemed a good idea to go with Unity. The other big upside is that you can deploy the game to be played via a web browser. This was definitely what I wanted. I didn’t want people to have to go to the hassle of a download-and-install, just to play the little toy game I made over a weekend.

I wrote a turn-based strategy RPG game. My inspiration was the “Shining Force” series of games. The theme of Ludum Dare this time was “Alone”; every game submitted had to follow this theme. This obviously doesn’t fit the team-based gameplay of Shining Force, but mine has a twist. You just play as a single character. It just takes the combat part of those RPG games, there’s no walking around and talking to villagers. There is a shop to purchase and sell items between battles, but that’s it.

The Game

Here’s a link to play the finished game:

“Adventures of One”

I was disappointed with what I ended up with, mostly due to how much work I had to squeeze into the time. In my eyes the game had two major failings:

• A lack of polish. The art is my placeholder art, and the GUI is the default-Unity GUI.

• Little game balancing. The first world is decently balanced, but after that it gets way too easy. The game is completely procedurally-generated. I just didn’t have the time to playtest it.

The biggest achievement though was:

• I wrote a game in 48 hours, that’s actually playable; and a little bit fun!

That’s my introduction out of the way. Now, onto the postmortem…

What Went Right?

• Choosing an idea which I’d see through to the end. I actually lost most of the first two hours to thinking over what type of game I’d do. The theme ‘Alone’ was tricky for me, as most of the ideas I had before it was announced didn’t fit it. I ended up taking one of those ideas and simplified it. In retrospect doing a full-blown party of player characters would have been ridiculously hard to do in 48 hours. But yeah, I was excited by the idea and that helped me keep my motivation.
• Using a higher level language like C#. Considering the game didn’t make too much use of Unity-specific ‘scene’ features, and was mostly generated in code; I could have had similar results using something like XNA instead. Either way, this sort of rapid development lends itself to something higher-level like C#. Out of habit, I think I would have been too anal about my code if I wrote it in C++. C# just lets you throw caution to the wind that little bit easier!
• Enemy AI. Pretty close to “Shining Force”’s enemy AI. It slotted in well to the turn system I had set up; so it followed the same rules and states the player had. The turn system I wrote had its positives and negatives, but since I left the AI to pretty late on, I’m happy I spent the time earlier making the turn system generic.
• The UI. I left it to pretty late on. I hate coding UI. I’m glad though I just used the stock Unity functions and didn’t try any fancy rendering techniques. I went for the basics, and that was the right decision. I’d hoped I’d get the chance at the end during the polish phase to ‘skin’ it, but I had no polish phase.
• Save and load. Lost close to an hour implementing it, but it’s a pretty cool feature. It autosaves after each battle (Unity stores web-app info on your hard-drive, so it’s transparent). I also got in a crude Base64 load/save screen, to bring your save to other computers.
• Bug free? Well, it seems to be for me. I kept it in a pretty stable condition, considering the game’s complexity and reliance on procedural generation, and AI.
• Food, drink, and breaks. I think I was sensible with what I ate and drank. I took pretty regular short breaks. Even if it was to just chill on the sofa with a notepad for five minutes, and plan out my next coding session. I’m not a coffee or energy-drink guy, so just cups of tea kept me going. I’m unsure how I wasn’t totally fatigued by the end, I’m guessing it was adrenaline.
• The ‘all nighter’. It saved me from not finishing. I’m an optimist when it comes to scheduling time. Re-reading my journal log, I hardly meet any of my set goals (but to be honest I did surprise myself with getting ‘unscheduled’ stuff done really quickly). If I’d had lost say, another five hours to a second nap, there is no way I’d have had a functional game come submission time.
• Placeholder work. Crappy art, blocks instead of characters, a checkerboard playing area for 90% of development. These sorts of things meant I had systems playable sooner. This helps my motivation, there’s nothing worse than building up to a point, where you’ve seen nothing on screen and hoping ‘everything will work out at the end’…. And then it inevitably doesn’t. My longest blind-coding run without actually seeing anything on the screen working, was about half an hour; for the turn system. Everything was short and sweet to rapidly iterate on.
• The audio. I think it went well. I dropped in the sound effects just after the halfway point, which provided good battling feedback, with the lack of particles/visual effects. The music I also procedurally generated. I lucked out with some good classical piano pieces which fit the style of game well. The voiceovers by the wife I threw in at the last minute. They worked out well, but I’d have liked to try and fix the audio balance between her and the music a bit more.
• Not caring about the code quality. It’s awful. Terribly hacked-about stuff that reminds me of the sort of thing I’d have written in college. I however still coded pretty defensively though. I just didn’t worry about things like commenting, and whitespace/indentation being off. Fix something ‘properly’, or throw in a sure-fire hack? A no brainer. I also committed many cardinal sins with global static singletons, instead of jumping through Unity’s component hoops. My typing fingers thanked me!
• Stand-up desk. I have an IKEA Jerker desk. It’s not adjustable, but I have a high stool which I use when I need a rest. Being able to constantly switch between two was awesome. When I’d feel lethargic in the chair, I could stand. When my feet got tired of the standing, I’d be able to take a load off and sit. I probably was about 50/50 in each position, time-wise.
• No internet distractions. I know some people who do these completions regularly like to use Twitter and IRC extensively during the dev time. I’m a bit of a procrastinator; those sorts of things can be a big timesink. I told myself I would just check my emails on my cellphone, and do nothing more than that. It worked out well. I’m real surprised that I didn’t feed my Chaos Engine addiction, throughout the whole 48 hours!

What Went Wrong?

• I left some important features until way near the end. In particular the attack logic I rushed through, such that it doesn’t scale into later battles. Enemy placement and the map terrain generation I did with less than two hours to go. I should have had all the procedural-generation stuff done very early, and other risky things like the battle logic calculations too. Instead I did the bread-and-butter stuff that’s hard to get wrong first, and did the risky stuff later.
• Very little playtesting. It’s a slow game to play through to test leveling into later battles. I should have made leveling stats deterministic and had some way of starting myself off in the later, harder battles to test balancing.
• Graphics/art. I spent hardly any time at all on the graphics. I can’t draw for shit, but I can usually fudge things to look very aesthetically pleasing despite that lack of talent. I didn’t even get any time to try that.
• A lack of preparation. I’d planned each day during the week prior to “look at Unity tonight”. I hadn’t got around to it. So I had to learn as I went. Some aspects like hooking up audio took a little longer than they would have, if I knew how to do it beforehand. I also found myself dropping in and out of the ‘component’ model that Unity has for objects, because it didn’t ‘click’ for me until a few hours in. I think I would have likely pen-and-paper planned out my components to be better organized, than the ad-hoc mess they ended up as.
• AOE (area-of-effect) magic; stuff that affects more than one tile. Probably lost a couple of hours spread over the whole period, to implementing it, and dealing with fallout from it. I envisioned it as being useful in later battles when there are tons of enemies; which drove me to add it in the first place. It’s a shame later battles are such a walkover, which kind of renders it just a time-saving device.
• I started working at about 11am on the Saturday, after about five hours of sleep. I took it easy in the morning, and watched some football as I coded. That time was actually pretty productive. I then carried on for well over 24 hours and worked up to the 6pm deadline the next day. I really didn’t feel too tired, but my productivity certainly slowed. I didn’t have many bugs to fix, but one in particular was niggling in the last four hours. I only fixed it shortly before submission. I think with a fresher head, I’d probably have not caused the bug in the first place.
• UI and state machines. I hate coding UI. I hate coding state machines. This game had plenty of both. I’m surprised it didn’t demotivate me. State machines always seem such a chore. So much code for what has very simple intentions. Scripting languages can make this a lot easier with their micro-threading capabilities. I remember reading something about C# and the ‘yield’ statement lending itself well to state machines, but it’s a little less straightforward to grok. I should have probably checked that out again.
• The scope. Too big. Too ambitious. Given my lack of preparation too, it was silly to think I could do the idea justice in less than 48 hours. I had a good stab at it, though.

“Picasso” – Look at that work of art!

My TODO List At The End

I had to prioritize the last few tasks, so I inevitably had some on the cutting room floor. Here are the features I really wanted to add:

• Particle effects on attacks. I’d seen some demos of particles in Unity, and they looked really simple to set up. A good bang-for-buck. Didn’t even give it a slight look.
• More/better character graphics. I also rushed through naming and giving stats to the enemies that did make it in. The art in the game isn’t good, and I don’t think I’d have made it that much better; but I’d have liked to added more varied enemies for sure. I think I probably spent a grand total of about twenty minutes the whole project (if that), making art.
• I had functionality to ‘slow’ the player movement over harsh terrain, and collision for impassable squares. I always planned to procedurally generate the terrain, but I didn’t get the chance to hook this stuff up. Impassable squares would have been tricky, in order to avoid blocking the player out of areas. ‘Slow’ terrain though wouldn’t have been much work.
• Healing spells for enemies. ‘Buff’ and ‘debuff’ spells for the hero player, as well as the enemies. Similar ‘buff’ and ‘debuff’ items to use as well. Some of the turn-logic for this sort of thing was in place; it would have probably taken less than an hour to add these.
• A better looking GUI. I’d have liked to try changing the font and colour used. I did Google search at one point, but it looked pretty involved, and would require me to go through all my UI code and hookup references to a ‘GUISkin’. Probably not much time to do at all, but every minute counted at this stage.

Of course, all of these things still fall way below ‘fixing the balancing’, and some other things mentioned in the “What went wrong” section. The Perlin-noise, colored and textured terrain was actually a wishlist item for me originally. I wonder if I’d have left that on the wishlist, I would have been able to fix the balancing?

Final Thoughts

In all, I enjoyed the experience. I was disappointed that the game I was intending to be challenging and provide seemingly ‘endless hours’ of battling, only holds up for about ten minutes. But I had fun coding something that quickly under a time pressure. Sure, the code looks absolutely horrible, but it’s a thrilling experience just churning out stuff at that speed, and having it all come together.

I would consider doing another Ludum Dare in future, but I’d definitely want to do more preparation. I’d also certainly scope my idea much better. I think a shorter, tighter game is the way to go. Something that would be doable with two ‘sleeps’ in there as well. I’d like to get a good twelve hours of sleep next time, instead of five!

My Journal Log

You’ll notice the log ends at about 2pm, four hours before my 6pm deadline. That last four hours was just a whirlwind, the time flew by ridiculously fast!

log.txt

I found it pretty useful to keep this log. It helped with motivation, and helped me focus on what I should be doing next.

I also have half a dozen mini-notepads full of ramblings about movement, AI, and the turn system. Taking a break from the computer and sitting down with a pad and paper is pretty valuable. Just gives you time to refocus, so you don’t just sit there coding down a blind alley.

My Time-lapse Video

~38 hours in ~4 minutes:

Ludum Dare #22 – Adventures of One

The first session was about 10 hours; the second session was about 28.

The last man on Earth sat alone in a room. There was a knock on the door…

Play It | Rate It

Origin

When I heard Alone was chosen as the theme, a set of bizarre ideas immediately appeared in my mind. I really wanted to explore about the feeling of being alone, about the psychological effect of it. Also, I had read The Knock recently so I wanted to explore more about that subject.

Development

The tools I used included:

• Adobe Photoshop
• Adobe Lightroom
• Adobe Flash
• Flashdevelop / ActionScript 3
• as3sfxr »
• Aviary »
• A standard Digital Camera
• Some burned papers
• A friend (lol)

The art is rather simple, I took some photos of my house and I asked a friend to model for me. We did some shots of him walking, but because I lack equipment (tripod, marks, etc) the result looks a little bad. I did my best to correct the photos in Photoshop. The room is a part of my house, that isn’t even a room, but I couldn’t take a picture of a real room because the camera angle was too short. I applied Exposure and Posterize to all the images.

The programming was done entirely in ActionScript 3, using some features of my own library, but the vast majority was to be made from scratch. I used Flashdevelop because I’m really fast with it… Just press Ctrl+Shift+1 and it’s like magic!

What now?

I think I’ll work more time on this game. I’ll add more puzzles, make an easy mode, add language support, and maybe more rooms to explore, or explore more about the story. For example, what happened upstairs?

This was my second time on Ludum Dare, and I think it was a really good experience. I don’t think there’s something that went wrong, maybe next time I’ll add more features to my framework, like effects, sound support and embedding support; but at the end I managed to do what I intended to do.

Good

• My zombie! I’m really proud of my ugly zombie. Yes, I spent a lot of time on it and it isn’t good art by any standard but I don’t care. It was worth it to see it “alive” in my game
• I only realized that after I was done but I kind of made the game I wanted to do for December 2010′s LD. Except then I had found myself making an alien instead of the zombie I had planned to do and then gave up before I had gameplay anyway. So it’s like I tied up a loose end.
• The jam. If not for the jam I wouldn’t have been able to finish my game and the LD would have just ended in bitter disappointment for me.
• My trusty ZBrush was awesome: sculpting/painting the zombie was the most fun part of this LD, Blender was also great for animating it.

Gray Area

• Making the low-poly retopology took more time than I thought. I tried TopoGun which I had just bought a few days before the compo and never used.  That added a few hours of work but then TopoGun worked really well for generating the color and normal map from the sculpt.

Bad

• I missed the compo deadline and had to do the jam
• I was generally not very fast. Lack of concentration maybe? Everything seemed to take just longer than it usually would.
• I spent the same amount of time on the environment than on the zombie and yet it really doesn’t show.  I just wasted time noodling with bits cut from my original hallway model and just made a mess and had to restart again. It was a time sink for no reason.
• Simplistic gameplay. I wanted to make the game more about stealth.
• I still suck at using Modo. It’s a great software I have no doubt of that and I mostly knew how to use it. But somehow I still find myself struggling against it every step. I don’t know how to explain what it is exactly. It’s weird and it’s probably just that I lack the practice to have the right instincts but it’s really annoying when trying to speed model and everything reacts in a slightly unexpected way and I keep having to undo and try again. I’ve got to spend more time using it.
• Still no time for particles effects. I put them on my priority list for this LD and still neglected them.

Time use

• Code: 11.2h (includes setting things up in Unity)

• Model: 9.3h
• Texture: 4.7h
• Animation: 3.5h
• Sound: 2.4h
• Level building: 7.6h (half of it wasted on a discarded version)
• Sleep: 24h
• Doing other things: 3.4h
• Misc: 5.5h (probably 50% actual work the rest being posting WIPs, chatting on the IRC channel, etc)

• Total spent on zombie (including sounds, code, etc):  15.5h
• Total spent on the environment/level (incl. medkit props and ambient soundtrack): 15.4h

The World Of Arzea

During this past weekend, in addition to streaming, I made sure to screencap my main monitor every 10s for the duration of the competition. From this, I created a timelapse for you to watch how Arzea was created from start to finish.

If you would like to play or rate the game:
http://www.ludumdare.com/compo/ludum-dare-22/?action=rate&uid=4155

Otherwise, enjoy:

http://youtu.be/WcFZQaoMdCM
http://youtu.be/WcFZQaoMdCM
(Issues with embedding…) 

If you haven’t played/rated it yet, please do so here.

• First, i had about 143.472 image files captured. That looked a bit worrisome.
• The images were having serial numbers in the ld22-frameXXXXX.png format. However, as mentioned, there were more than 99.999 images, so half of them were using an extra digit and, thus, not sorted correctly.
• So i had to write a script to fix that.
• Then there were a lot of gaps. I’m using the screencapture Mac OS X command-line program to take the shots, but if the screen has blanked out, nothing is saved.
• So i had to write a script to fix that by using a filler image for that.
• Then i had to wait for almost a half-day for them to be converted to a (huge) .mpg file with ffmpeg.
• And after that, iMovie (the editor i usually use and so far has worked well) decided that it won’t support .mpg files.
• So i had to wait for a few extra hours for the huge .mpg file to be converted to a huge .mp4 file that iMovie can open.
• iMovie, however, saw through my scheme and decided that, no, it won’t open the file. It didn’t even tell me why – it just acted as if i decided at the last moment to cancel the import process.
• So i had to search for another editor. While doing that i noticed that all open source video editor for Mac OS X are either abandoned old editors from the PowerPC era that Mac OS X Lion doesn’t support anymore, or experimental ports of mostly Linux-based tools that may work if you are lucky enough and willing to compile from source.
• Fortunately, i also noticed that Blender, the 3D tool i use, has a video editing mode. Wtf, how i missed that for so long (ok, i had heard of it, but i thought it was some sort of simple annotations or whatever…).
• So i spent an hour learning how to do video editing with Blender.
• And finally made the video as i wanted it. That is, i added an intro image and removed the big delays while i was sleeping.
• Then i had to wait for another half-day (or so) for Blender to export a huge .mp4 file. I hoped it wouldn’t be huge, but it actually was about 2.2GB :-/
• So i decided to do the conversion properly with ffmpeg to H.264 and MP4 myself. And these formats were mandatory since i wanted to have (a bit of) control over the video quality and YouTube doesn’t seem to mess with the video encoding with these formats.
• Unfortunately the ffmpeg version i had wasn’t compiled with libx264 support. So no H.264 encoding for me.
• So i tried to use a version from Linux using VirtualBox since Debian would probably have it an apt-get install away and i was so tired of all of this.
• After another hour configuring repositories (because, apparently, Debian didn’t have it an apt-get install away due to licensing issues…) i managed to have a x264-capable ffmpeg converting the file.
• Only it was way too slow. Like, 1fps slow. Making that video would take more than the game itself.
• So Debian idea scrapped, let’s go back on Mac OS X. And compile our ffmpeg with x264.
• And thus i downloaded code for libx264 (i already had compiled ffmpeg previously), yasm (that libx264 needs) and a couple of others.
• I spent a couple of hours just trying to get ffmpeg compiled. Incompatibilities between (default) flags, the installed version of gcc, features, etc and almost no mention of it on the web. Bleh. But i finally managed to do it.
• And so, yet more hours of waiting to get ffmpeg convert the 2.2GB video to something i can upload…
• That would be a 415MB video.
• So, i left it uploading and went to sleep fully tired… and finally:

Making of
“She Loves You”
Ludum Dare #22
timelapse
Sorry, i couldn’t figure out how to embed a YouTube video

After watching it, i also figured out what exactly was missing from the game:

What was missing from She Loves You

Next time i’m going to fix that