Is it bad to be compulsively checking the UPS tracking page for my new laptop? Or to be a little nervous because it’s currently in Kazakhstan, and all those Call of Duty games made me a little nervous about ex-Soviet republics? Is that over-protective? It’s not even here yet, and I’m clucking over it like a mother hen.

Whatever, as long as it gets here in one piece and is suitably shiny. We’re kicking off with our new client this week, and it was immediately apparent that my current 32-bit dual core laptop (now five and a half years old) really wouldn’t cut the mustard. It was okay, just, for building for 360, because the console does all the heavy lifting. But it won’t run a PC build of anything substantial, and compilation takes an age. Not to mention the graphics flashing and sporadic unexplained hard freezes. So the new Macbook Pro kills two birds with one stone – it’s modern and chunky enough that it should build and run the client’s title, and it means Tim and I no longer have to pass the older Macbook Pro whenever there’s iOS work needing done.

To put it in some context, Tim’s machine needed a new graphics card as well to bring it up to spec. His new graphics card scored ~1600 on the benchmarks. The new Macbook Pro’s graphics score ~1300. Tim’s old graphics scored ~500, and the old MBP ~270. My current laptop (and bear in mind I got the Dell Precision M65 with the graphics ‘upgrade’) scores 71. Yes, 71. I had to go three pages down on the benchmark list before I could even find it.

Of course, even the new MBP isn’t up to the level of the monster Alienware M17X that MGS bought for me, but on the flip side, it also won’t weigh 7 kilos and sound like a jet turbine taking off. While I do still miss the glowy lights and brushed aluminium body of the M17X, the added benefit of crotch-based heat sterilisation from the MBP is surely enough to seal the deal.

It’s been a while since the last blog post though, so I’ve missed the opportunity to post this gem from back in December (and #HurricaneBawBag)

How to get poor reception

That is our back-yard neighbour’s TV and ham-radio antenna, trailing a big sheet of polythene. Note the mangled and bent spokes, as a result of the polythene catching the wind like a sail and whipping around for hours, very nearly pulling the poor man’s chimney stack over. Not that last months winds can hold a candle to today’s storm though. It seems Mother Nature is angry with us this winter.

To other news: we’ve picked up a new client for the new year which promises to be very interesting – a variety of code support work on PC/360/PS3. In addition to our existing clients, that’ll mean our own projects will have to be put to the side for a little while.

After yet another acquaintance saw fit to share their mobile app idea with me last night, I realised that what we’re short on isn’t ideas, it’s time. What with all of our client work and flitting back and forth, we very rarely get a chance to get heads-down, all-out concentrated on our own apps. There’s nobody to blame for that but me really, but we are rather at the mercy of the paying work. Tim’s been doing a bang-up job in December of bringing our latest creation up to a releasable standard, but I fear it’s not going to reach the quality bar before we have to put it back on the shelf and concentrate on our clients’ needs.

In an ideal world, we’d be able to take our time, concentrate fully on bringing our ideas to fruition, and the money made from releasing them would pay for the next round of product-making. In practice it’s not as simple as that; client work is money in our pockets now, but app sales are money in our pockets later, maybe. Of course, that’s a vicious circle, without taking a punt on our own apps, we’ll never have the opportunity to win big and break out of the work-for-hire mold. But in the meantime we take the work that keeps a roof over our heads.

We’re coming up on the end of our 7th year in business now, which is no mean feat these days. I’ve just updated our entry in SDI’s Gaming Brochure list of Scottish developers, and it’s heartening to see all the small and large companies in there. Here’s to a bright and positive 2012, and to the opportunities it brings.

I’ve the office to myself for a couple of weeks, as Tim has taken the opportunity to use up the load of holidays he’s saved up before the end of the year, and Dan is busy with both university and other projects. I’m somewhat surrounded by Amazon boxes, as my wife has been using the office as a delivery drop-off for a vast amount of Christmas presents for all and sundry; as a personal rule I don’t shop for Christmas until it turns to December, but she’s a bit more efficient and organised about it than I am. As compensation for that though, and because she’s just generally lovely, she’s also had them deliver a shiny new copy of The Elder Scrolls V: Skyrim for the 360. There was a certain amount of giggling with glee when it turned up, as I’ve been quite jealous of all the other devs who are enjoying it: I do like a good open-world adventure. Where I’m going to find the time to play it I’m not quite sure yet, but even rationed out over weekends I’m sure it will be fun. A first quick blast in the office had me running away from dragons, which is always a good start.

On a whim a few weekends back while I was huddled up trying to beat off a nasty illness, I picked up a copy of DCS: Black Shark from Steam; I do like sim games, and the X52 in the cupboard doesn’t get a chance to come out. It was tragically disappointing though. Not because the manual isn’t the manual for the game, it’s the manual for the actual helicopter. That’s half the fun. No, what put me off was the terrible way it was presented. In a nod to playability, they include ‘game’ toggles for the flight and avionics. The ‘game’ flight mode is much friendlier to new players, but takes away half the fun and control I enjoy. However I learned my lesson with Lock On: Modern Air Combat; actually learning the radar and weapons controls for a real combat aircraft isn’t nearly as much fun! So I want ‘game’ avionics, and ‘sim’ flight, and set the options accordingly.

Here’s where it starts to go wrong. If you set either of those options, the game considers you in ‘game’ mode. And there’s an entirely distinct control configuration for game mode. It doesn’t tell you it’s in game mode, or give any indication as to which controls are ‘current’. You are just supposed to know. It’s not even in the manual anywhere, I checked. Worse, the control configuration isn’t accessible from the in-game menu. So you start a mission, take off (because that part is easy), but find you can’t operate one of the controls (of which there are many). Can you look it up? No. Because to look it up, you have to exit the mission, and go check the control configuration in the front end. I don’t even want to change it, I just need to see which button it’s mapped to.

So instead of actually enjoying the challenge of controlling a complex, agile helicopter, I find myself getting into the mission, only to find that the weapons systems are unusable, and I get shot down because I am spending a good few minutes just trying to get a particular bit of it to work. And there aren’t any missions in there that let you just concentrate on one thing at a time. You don’t get a ‘free flight’ mode, you don’t get some a mission with nice simple targets that don’t fire back right in front of you so you can familiarise yourself with the weapons systems. It’s either ‘quick start’ (which throws you into a mission assuming that you have full control over everything), or ‘campaign’. At least the first mission in the campaign takes you through some easy flying, but there’s no practicing of flight maneuvers, just ‘fly there, then there, then home’. That’s not what you need to practice. You need to practice low level flight, and going from full forward to stopped and hovering before popping up over the brow of a hill. You need to practice strafing and orbiting targets. None of which is encouraged in the missions provided.

Anyway, suffice to say that the nod towards making it ‘friendly’ very much fails. It’s not that much friendlier for novices, and those parts are ignored by intermediate or pro pilots.

Lastly, and on a completely different note, we’ve got ourselves a new accountant, who comes recommended from a couple of other game-devs around Scotland. This is a bit of a relief to me, since our filing deadline is the end of December. The previous accountants, who I’ll not name (although they do deserve to be shamed) have been informed, although they can’t have expected to keep our business, not least because they’ve been avoiding contact with me since spring (and their refusal to pay the fines they incurred through their incompetence).

The iPhone app we made for PASG has finally launched – Hold’em Manager for iOS. That was our focus for much of late last year and this first half of this year, so it’s nice to see it out in the wild. It’s a partner application for users of the Hold’em Manager suite of apps, which are a great tool for any serious on-line poker player. Mind you, I do have to persuade our accountant that the money paid to on-line poker sites during testing are in fact valid business expenses. Not sure exactly what category that comes under in our year end accounts.

I took some time out in late July to tackle something I’d been meaning to do for a while: get us some official Company t-shirts. Here’s me modelling the black version:

Very ‘man from C&A’, I know. I’d never make a model.

Our month long experiment with allowing people to comment on the blog without registering first is now done with, as I’d suspected, it didn’t really help much with the spam. Instead of a few dozen spambots registering on the site and needing deleted, we got a few dozen spambots registering on the site and needing delete and a few hundred spam comments which Akismet blocked before ever seeing the light of day. We don’t see a lot of discussion here on the blog, so the increased maintenance effort on my part wasn’t really worth it. Back to registration first for the foreseeable future.

Too much time this month was wasted trying to rebuild Dan’s PC, which had taken to freezing on boot and blue-screening. After swapping out every single component (graphics, PSU, motherboard/CPU, HDD, heck even the keyboard and power cable), we eventually figured out it was the DVD drive. Operated as a DVD drive perfectly, but if plugged in would cause failures. As a result we’ve got pretty much all of the bits of a new machine, so now Dan has his own, entirely rebuilt machine with Windows 7 (instead of a hand-me-down server machine running XP). I also get my XP server back, which I’d been missing as it’s nice to have a box I can run Cruisecontrol and background tasks on. It’s doing a sterling job with our tools work for Sumo, which is occupying most of my time right now.

Team Bondi went into administration. Not entirely unexpected, but still not nice when the livelihood of people is on the line. Hopefully it will serve as a warning to other studios as to what happens when you mismanage a project so badly with regards to working hours. However more likely it will all be pinned on Brendan McNamara, and the crunch part will be played down. The people I really feel sorry for are those at KMM (the only other sizeable employer of digital art staff in the area), who escaped Team Bondi and its management, only to find that their nemeses have now followed them to their new job.

Anyway, that’s pretty much it for now, back to tidying up all the boxes of PC components strewn around the office.

Curse you and my steel (tin) prison...

At least the squirrels have the decency to stay on the outside of the office though. This little gent (or lady, I didn’t get close enough to check), was the second littlest of a family of mice that have been tormenting us for weeks now. Leaving little presents on our desks. Something in the last couple of weeks must have driven them out looking for nesting material though, because they were all inexorably drawn to the box of packing peanuts that lay out in our office. Bold as brass, we found them rustling around in the box, and popping out the top with a polystyrene peanut in their mouth, trying to get away. Thankfully, their attraction to the box made it much easier for us to arrange things in such a way that we could more easily trap them when they did show themselves. At the current count, I’ve caught four of them, and Tim caught one [Hah - I win!]. We’re presuming the one Tim caught was the daddy, as he was much larger.

All of them were released into the wild (or as wild as it gets 100 yards in either direction along Belford Road), as we’re both softies at heart and couldn’t quite bring ourselves to kill them. Tim’s catch was released on the Dean Bridge itself, much to the amusement of passers by – hopefully it won’t have decided to end it all and take the leap off the edge. They probably have a homing instinct of some sort, but we figure as long as they find a similarly attractive home somewhere along the way back we’ll be rid of them for now.

The real trouble is that we here at Black Company make terrible cold testers. We’re technical, so we tend to focus on the implementation details rather than the broader feel of the interface. We’re advanced users, used to knowing everything about the software we use; being forced to learn a whole new interface makes us grumpy, but not nearly as grumpy as having not having all of our usual tools to hand. So as I usually do with such things, I hand them straight to my wife without saying a word, and simply watch how she uses it. The question was, really, would it find a use naturally, or would we be using it for the sake of it? And what would that use be?

Put simply, it did, and the use is: content viewing. I had thought that my computer time was read-write, but in reality, outside of work, the majority of my time is spent consuming content and not creating it. Facebook, Twitter, blogs and RSS feeds obviously, but more and more with on-demand video services like iPlayer. The iPad keyboard is, frankly, not pleasant to use (I’m writing this blog post using it as a proper test), but for the majority of content viewing we do, that’s not an issue. In fact, in the few months we’ve been using it, the biggest annoyance has been the fact that much of the on-demand TV we want to watch is on Channel 4, and their web solution was Flash based (i.e. not available on iPad.

And it was what we had to do when we did want to watch those things that drove it home to me. The iPad lies around the living room happily. It’s discreet and portable. To get the laptop out, plugged in, booted, takes a good 5 minutes, not just because it lives in a bag in the other room. So it’s a new way for us to experience the content out there, that we just wouldn’t have done before, and I don’t think I would have appreciated that without properly field testing it (or at least, allowing Vicki to do that).

That’s not to say that there aren’t other lessons to learn too. The bad apps we’ve found are the ones which simply take an iPhone user interface and make it bigger. But the key thing to appreciate about the iPad is that there’s likely to be only one in the household. Whereas the iPhone is a naturally single user device (not just because it’s something you keep on you as you move around), the iPad is passed around amongst the household. So apps like Facebook and Twitter have to account for the fact that you’ll want to easily pop back to the top level and switch users; as well as some loose protection against accessing other people’s accounts. You trust the people you share the iPad with, but not that much. And of course, it’s far less likely to be moving around out in the world, so apps that focus on the geo-location data are far less useful. On iPad, the value is on it’s versatility to display content in a relaxed environment (not necessarily at a desk). The larger display is key to that versatility.

The trick will be to take the things we understand about how the iPad gets used, and use it to inform our app designs.

In the meantime, I haven’t much that I can interestingly write about here. We’re juggling now 5 distinct projects (6 if you include the much neglected internal prototype work), none of which I can freely write about here. Well that’s not true, of course I can talk about our own project, but right now I don’t quite want to, at least not until we can put up some interesting looking screenshots. But more importantly for us is the fact that we’re actually progressing one of our ideas, instead of continually putting it off till the next bit of down-time between client work. I think that’s good, both because it’s cool to be doing our own work, but also because it keeps us from going a bit mental with an seemingly never-ending pile of work-for-hire. As much as we like our clients, their work is theirs, and it’s hard to get super-enthusiastic about other peoples’ projects.

I’m personally feeling a bit of burn-out, largely because I’ve been working solidly since before October, with no breaks of more than two or three days, and there’s not likely to be any let up for the next month or two at least. So refreshing our heads with a bit of our own work is a good thing to stave off the madness. Sadly the same lack of available energy is the reason why the scarcity of posts here. There have been plenty of interesting topics come up, I’ve just not been able to find the time to write them up for here.

It’s funny, because when I was working as an employee for someone else, it never occurred to me that I needed a holiday. I threw myself into the work, but not completely, there was always room for personal stuff. Since starting up for myself, the greater focus on work means that I’ve had little creative energy left over for anything else. And if I want to refresh my batteries, I think I need a proper (i.e. not thinking about work at all) holiday. But I should stop dwelling on that now, because I find myself staring out of the window here at the pretty sunset, day-dreaming about what I’d do on a holiday, and that’s just rubbing salt in the wound.

1.1 You’re an employee, we’re your employer. Welcome aboard. Get to work.
1.2 If you’re too sick to work, don’t be surprised if we get a temp in to cover. Don’t worry, you’re not being replaced.
1.3 Just to make sure – you’re okay to work here, right? You’re not also pretending to work somewhere else? Or claiming benefits from being out of work?

2.1 We expect you to work a typical week, but when the s&*^ hits the fan, we might need you to stay late.
2.2 If you’re putting in a regular day, you can totally take some time out for lunch. Just don’t eat anything that stinks the office out.
2.3 We can’t / don’t want to pay you money for overtime. But since overtime is definitely over and above the call of duty, we want to recognise that, so if we do need you to do it, we’ll let you take time off later, as much time off as you put in extra now. That doesn’t mean you get to take the piss and work silly hours for a week, and then not come in for a week. What it does mean is that, if the business needs it, you and your manager can work out when you’re going to work extra, and when you get to go home early (or stay off) to make up for it. Even at that, we’re going to cap it at 20 hours in a month, because that seems like a reasonable amount; anything more and you’d not be usefully working anyway.
2.4 Don’t f*(& around. Really. We pay you to work, we expect you to work. Don’t take the piss, and you’ll do just fine. On a more serious note, this is really how we want you to work. We don’t want you working stupid hours into the dead of night to hit our deadlines, we want you in and focused 100% on your work for the 8 hours you’re in the office each day. We’ve already said we’re going to send you home at a sensible time every day, and we hope that will help keep you sharp and eager to work when you’re at your desk. Obviously there’s some give and take here, but it’s at the discretion of your manager. Rest assured, he’s probably occasionally web-surfing too, but within reason, and he expects the same of you.

3.1 This is obviously a condition written when we were still all working from home (we have an office now). We’re not going to up a move to Guadalcanal without some notice, but if we do have to move, we don’t expect you to come with us without being paid to relocate.

4.1 You get paid! Hurrah. You get paid after you do a month’s work, at the end of the month. (If we didn’t pay you at the end of the month, you’d be within your rights to not come back in at the start of the next month until we did).
4.2 We’re not going to fix you on this salary for ever, but we can’t say when or how we’ll change it next. We will however work out when that’s going to happen with you in advance, usually when you take the job.
4.3 Legal stuff.

5.1 If you’re working for us, and you pay money out of your own pocket to do that work, we’ll pay you back later. But you’ve got to do it by the book, so receipts, and get the claims in sharpish. And for goodness sakes, clear it with your manager first.
5.2 Company credit card? How much do we trust you? Okay, so we do, but you’d better not abuse the trust, and it’s still ours.

6.1 Details
6.2 You get a certain amount of holidays a year, and you earn a fraction of those holidays for every day worked. This is to stop you from joining the company, then trying to take all 30 days holiday in the first month. Holidays come after the work, not before.
6.3 6 weeks holiday – but bear in mind that includes the what, 8 days of bank holidays that some other places add on top.
6.4 You have to let us know when you want to get off. Usually that will be fine, with advance warning, but sometimes we need you in the office for certain deadlines. The farther in advance you let us know, the more likely it is you’ll get to take it; if something comes up for the business then so be it – we won’t ask you to cancel a big holiday planned in advance because the client pushed the deadlines forward (or back)
6.5 (see 6.3)

7.1 You’re never so sick that you can’t make a call to the office and let someone know. NB: Emailing is not letting someone know! You have no idea if that email’s been picked up, maybe the person you emailed is sick as well. You have to have made a sincere effort to let someone who has made it to the office that day know.
7.2 Doctor’s note if you’re really sick – we need the paperwork to cover us for sick pay reasons, etc.
7.3 More statutory stuff that says we’ll still pay you if you’re long term ill, but in line with government rates
7.4 same again
7.5 and again
7.6 If you’re getting a wad of money from sueing the drunk driver that knocked you over, some of that money comes to us to cover anything we’ve paid for your convalescence.
7.7 We might need to check your health, for our own insurance reasons, or because we’re trying to stop all of you sedentary developers from keeling over with heart attacks due to your bad diet and lack of exercise. Don’t worry, we’ll pay for it all.
7.8 Just because you’re ill, doesn’t mean that we can’t terminate your employment. In fact, whether you’re ill or not should have nothing at all to do with us letting you go.

8.1 We might, at some point, need to sack you. Might be your fault, might be a decision we have to make for other reasons. If we do, we’ll tell you about it a month in advance. If you want to leave, you also have to give us a month’s warning. If you’ve breached these terms though, we’ll put you out right away.
8.2 If you’re leaving, for whatever reason, we might want to just pay you for your notice period without actually having you around. Don’t take it personally. Whether we do or not is up to us though, not you.
8.3 If you’re leaving, and we keep you around for your notice period, then we don’t have to give you any real work to do, or even let you back in the office.

9.1 We might give you some kit to do your job, but if you’re leaving us, then you have to give it all back, including any copies you’ve made
9.2 And you might have to swear that you definitely have done this, so if it turns out later you were lying we have something we can point to and moan about it

10.1 If you are involved in any other business that might relate to us in any way (like a competitor, or even a similar business), you have to let us know. We might not mind, but you definitely have to tell us. That includes your direct family too.
10.2 Once you’re working for us, you agree not to start anything like that either. We don’t mind you buying shares in a business like that, as long as it’s not a very big stake.
10.3 Stuff defining some examples of how we mean ‘involved’ in those other businesses.

11.1 You’ve got to tell us if you were a crook, generally a dodgy character. And if you find out that a bunch of your colleagues are planning to leave and strike out in competition with us, you’re obliged to tell us as quick as you can. And if you know that one of your colleagues is screwing us over, tell us that too. Otherwise we’re going to believe that you were helping them.

12.1 Don’t tell anyone else things you know because you’re working with us. That includes other business’s secrets – our company has agreed to keep those secrets, and that includes you.

13.1 Any ideas or content you come up with “while working on activities for us”, belongs to us, wholly and completely. That applies whether you’re in our office our out on a client’s site somewhere, or even if you’re working on company stuff in your home. Conversely, if you’re not working on activities for us, your ideas are your own. Bear in mind, you shouldn’t be working on activities of your own when you’re at work at all – we expect you to either be at the office, working, or at home, not thinking about work at all.
13.2 If you do come up with something at work, and we really don’t want it, you can ask, and we might just give you all rights to the idea. This will basically take the form of a signed document that say exactly which idea we don’t want and we’re handing off to you.
13.3 Some copyright specific stuff to make clear that we, the company, is the author/originator, and not you, when it comes to IP
13.4 We might need you to sign your name and generally take part in the process of sorting out trademarks, patents, etc, that you had a hand in creating with us. That’s true even if you’ve left the company’s employment since you did the work. You won’t be able to do those things on your own, it will have to be us that drives the process.
13.5 You’ve got to do everything you can to make sure that the IP rests properly with us, and not you; even after you leave us.
13.6 Don’t steal anyone else’s work and pass it off as your own (and so ours), or make some libellous or obscene content in our name.

14.1 You’re going to be exposed to at least some level of our company’s secrets – you’ve got to keep them. If you do divulge anything, you’d better have our written consent first.
14.2 You can’t start a business in competition with us. But we don’t mind you owning shares in a publicly listed company that competes with us (that’s just investment). Shares in privately held companies are out though.
14.3 You’re not allowed to poach recent (in the last 12 months) customers from us
14.4 You’re not allowed to poach recent (in the last 3 months) employees from us
14.5 You’re not allowed to use any confidential information you have as a result of working for us, or tell anyone else that information (apart from tribunals or courts that you’re obliged to tell the truth in)
14.6 You’re not allowed to record details of what’s going on inside the company, unless it’s to benefit the company
14.7 You’re not allowed to pretend to still be working with us after you’ve quit
14.8 We know this legal wording’s pretty complicated, and different situations lead to different justifiable periods, so if this contract would be valid if we took out some of these restrictions and/or reduced the times involved, then that is the contract instead. I.e. you agree not to try and work around these agreements by finding a loophole in an otherwise reasonable clause.

15.1 Don’t do something on our behalf that would tarnish the company’s name. We’ve written down how we expect you to behave, roughly, so you should read up on that so you know what to avoid.
15.2 If you’re new, then we might skip the more rigorous disciplinary procedures; but you can take your complaint to the company director, if you’re not happy with the way you’ve been treated.
15.3 Please be sensible, and work things out with your line manager before starting the formal grievance procedure. But if you do want to do it formally, make it in writing.
15.4 If you’re formally doing things, you have the right of appeal of your decision
15.5 If you’ve since quit, please still raise the grievance with the company director.

16.1 Legal statement that nothing else interferes with these terms
16.2 We might need to change these rules, but if we do we’ll let you know a month in advance.
16.3 Where to find the employee handbook

17 Legalese

18 Legalese

I have this narrative in my head now of a lazy squirrel that wakes up one morning in November, hung-over to all hell, and realises that it’s frosty and he’s seriously late for winter. And now he’s dashing around, cursing under his breath at the monster head-ache he’s got, stashing food any old place. All the good places are taken as well, so he ends up stuffing them in all sort of rubbish places. Since I’m an unabashed cynic though, the story ends with him lifting up a particularly grumpy cat’s tail and trying to stash an armful of brazil nuts under the cat, only to be unpleasantly and messily devoured.

Our new and slightly larger team, at Ghillie Dhu in the West End

Dan brings much needed artistic ability to the team, and even though he’s only working a few hours a week, should give us the ability to make our prototypes look much, much prettier. Certainly much prettier than the photo above, taken in poor light conditions on an iPhone as we partook in a celebratory drink. We’re not that blurry really. Well, Tim and Dan aren’t at least; since my beard has reached full thickness, all of my edges are pretty fuzzy now.

In other, unrelated news, I’ve been answering questions over at the beta of the GameDev StackExchange site. It reminds me of all the reasons why I would get annoyed at gamedev.net et al; basically that since there is no barrier to entry, anyone can both ask stupid questions and give stupid answers. So you get people replying who aren’t professional game developers and have a very limited set of experience making ‘games’, but who have a very high opinion of their ability. However, since the original StackOverflow site has become a useful resource in its own right, despite the equally large numbers of “please help me with my homework” questions, and poor quality answers, I thought I would give this one the benefit of the doubt. I would heartily recommend any of my peers who have some free time to go over and contribute as well: while you can’t do much to begin with (new users can’t even vote good answers up), it only takes a couple of questions answered sensibly to elevate you from the rank of untrusted outsider to someone who can contribute. And as long as it’s people with real knowledge of the industry voting up the real solutions, I think there’s a good chance that there gets to be some content there that’s useful to the games industry in general.

Cue some virtual attendance of CS193P, the iPhone Application developer course from Stanford University. Taught by developers from Apple, and with all of their lectures videoed and put online, it has been a great way to get quickly up to speed with Objective-C and Cocoa Touch development. Of course that’s not the only way to develop for iPhone, you can (and in my opinion, should) implement the large part of any game or simulation app in standard C/C++. But for working with the iPhone operating system, and implementing interfaces (arguably where the real challenge and value in an iPhone app lies), it has to be done in Objective-C.

Stanford U

So while Tim was busy with some other work-for-hire, I took the opportunity to bash through the majority of the CS193P course, and start to tackle an app idea we’ve been talking about for a while: the Drunk Compass. More on that in later blog posts. Actually watching the lectures brought back a load of memories of university: it was nice to remember a time when all I had to do was take in as much knowledge as possible and try to retain it long enough to pass exams with.

Thankfully, as this was just one course, condensed, it didn’t last long enough to evoke the things that annoyed me about university: the feeling that I was always doing throw-away coursework. I’ve always preferred the hands-on approach, and by the time my university career ended, I was already itching to make something real, and loose it on the world. A shame then that my first shipped title with VIS didn’t see the light of day until 5 years later (although technically i-Race shipped much earlier than that).

Anyway, learning is good, and I think it’s been a welcome change of pace after the hectic nature of Crackdown 2 or our other client work. Hopefully now that I’m comfortable with the Cocoa interface tools, I can prototype our most promising app idea, and get it one step closer to reality.

Crackdown 2

It’s weird, I’ve spent the last month and a half working with the MGS and Ruffian teams to take the game they’d made and turn it into a demo form; I thought I wouldn’t want to play the demo again. I’d play the full game, sure, because I’ve never actually made it all the way through without cheating, and it’s a game where the pleasure is in the journey, not in the destination. But the demo is 30 minutes from the start of the game, and your progress isn’t saved, so I thought I’d just skip it and go to the main game. My wife and family finally got me an XBox 360 for my birthday on Friday, along with a stack of games (Halo 3, Halo: ODST, Forza 3, Bioshock 2, Assassin’s Creed 2), so I wasn’t short of things to play.

But like a digital drug, I found myself using my demo preview code, and playing the demo. I knew what to expect, and that didn’t make it any less fun. Shooting, punching, kicking, driving, exploding, all over the island. Not just once either. Four times through, to get 7 out of the 10 possible demo achievements. I even got my wife to play it through as well. That one I pretended was research for work: you don’t get much more inexperienced at 3rd person games than Vicki, and I wanted to see if we’d pitched the demo opening right. We had – she picked it up surprisingly quickly, didn’t die until much further into the demo than I’d expected. More pride – we’ve made something that can appeal to not only the hard-core, dedicated Crackdown fans, but also to newbies as well. Crackdown for everyone!

Ruffian Games

Not that I can take much credit for that really, it’s the stellar team at Ruffian who have done a fantastic job on the game. I’ve been privileged to work with them, and the wider team at Microsoft. This has been the biggest budget game I’ve worked on to date, with the highest aspirations, and the highest quality bar. It’s been a real eye-opener, and a great experience. Both teams are chock full of talented, enthusiastic folks, and my passion for the title they’ve matched and exceeded at every turn. I’ve got to give a special appreciation to our ex-colleague Peter Mackay as well – who went to Ruffian after leaving us last year. He’s done a great job on the audio for Crackdown 2, allowing the quality audio design to shine through. I was sorry to lose him as a team-mate, but I think he’s found a great new role at Ruffian.

The demo you can get your hands on tomorrow (June 21st), and the full game will hit the shelves from the July 6th. Get to work Agent!

Year Six will, I think, be far more eventful for us than Year Five. It’s too early to say yet what it will consist of, but I think there will be less X360 development, and a load more iPhone work. Of course, my prediction skills are fairly awful, so I should probably not try to guess in advance. What we do know is that we want to get our own projects out there and selling, and the iPhone is a far better opportunity for us to do that than, for example, WiiWare. And there will undoubtedly be work-for-hire as well, which is almost always interesting in itself, getting a chance to help out on other fun projects, and do what we do best – give our clients the software development help they need to ship. And if nothing else, we shall see just how furry the beard can get…

The Crackdown 2 Crunch Beard

Suffice to say that while I’ve continued to work on CruiseControl.NET plugins, I’ve yet to write up anything useful that could be condensed into a blog post. My article on employee Terms and Conditions for IndieVision.net has been shunted to one side, again. I had a productive meeting on Friday with one of the developers of Visual Studio, making an effort to persuade them to include some games development friendly features with their next version (not 2010, the one after); hopefully one or two of them will make it in and I’ll have improved the development eco-system just a little bit.

But in general I’m still struggling with the long commutes to Dundee, and the limited amount of time in the evenings to be productive. So on that rather downbeat note, I shall finish up, and place a tick in the entry on my task list for “Development Blog”. Hopefully future entries will be more avuncular and jolly. Wow, how long have I been waiting to use that adjective to describe myself…

That’s right folks, we’re now all set up for iPhone development, MacBook, iPod Touch, iPhone, and a raft of ideas. As I’m swamped at the moment, Tim’s taking the lead on all this, and our first project will be a small productivity app that he came up with. More details and screenshots as we get closer to completion…

Unfortunately, the heating in our office is less than stellar at the moment. Our part of the office is fine, but the people we share an office with (Alban Books), have little to no heat at all. They’re all huddled around electric heaters, and still cold for it. Worse still, the thermostat for the entire office is out in the hall, which is poorly insulated from the outside. So the thermostat is convinced that the entire office needs heating up, so our part of the office gets baked, and Alban and the hall remain frigid. And if I’m up at Ruffian, their heating is all screwy as well – with people wandering around with hats and gloves and scarves on all the time. But sadly I keep forgetting  my hobo gloves, which are in the office with Tim! So Waverley Gate is the only place with a reasonable temperature at the moment.

So to brighten up the blog, here’s a picture of the lovely rooftop garden at Waverley Gate. I don’t spend much time out on it, due to the aforementioned cold, but I do like to look out onto it while I’m making coffee or reheating last night’s leftovers for lunch.

This week’s blog entry finds me back on a train to Warrington to visit Evolution, a newly married man. My honeymoon, last week, was spent pleasantly disconnected from the wired world, in a forest cabin in Argyll. Not totally electronics free, of course, the laptop went with me and I had a chance to play through some Sam & Max, Spore, and replaying Call of Duty: Modern Warfare in advance of picking up the sequel which should be out around now. Other than that though, I left things in Tim’s capable hands. My boss at Microsoft, in addition to the shiny new laptop and office provision in Edinburgh, kindly consented to giving me a couple of weeks off around the wedding. I’m not really accustomed to taking time off any more though, so the weeks leading up to the big day I was still remotely monitoring the build systems down in Reading and keeping things ticking over. Happily the systems I’ve set up in the previous few months don’t require much maintenance, so this time away has been good in that it’s proved the reliability of the build setup.

TIGA

Near the end of October, I also attended a panel discussion at the Scottish Parliament that TIGA was pushing. This was partly for them to push their tax-breaks agenda in amongst Scottish politicians, but also a good opportunity for the Scottish games industry to show their faces to the wider world. We do tend to suffer from our normally clandestine dealings; if you’re in the industry everyone knows each other, but it was usually hidden away from the media or non-industry observers, except in small, tightly controlled PR moves. I’m glad to see that the industry has reached a level of maturity where discussing our needs with politicians and other interested parties is feasible and useful.

I’ve been down-beat about the merits of TIGA’s tax-break lobbying, both from a personal political viewpoint (I don’t like subsidies) and from a small business perspective. The tax breaks proposed seem to be of most benefit to larger companies, to encourage them to set up large studios in the UK. While I like that idea from the point of view of improving the general health of the development community here, it’s unlikely that we as a small outsourcing studio would see any direct benefit from these policies. I was uncomfortable to think that I would be the only nay-sayer in the room, but I was glad to find that the other smaller studios are similarly cynical about the policy.

More interesting to me was the other topic dwelt on by the panel – the push towards better education and training for new developers, and better opportunities for students to secure a role in the games industry. I’ve been worried for a long while about talent draining from the industry, for various reasons, and recent business conditions are making developers less and less likely to take risks on graduate developers. Anything we, the government, or the educational institutions can do to make it easier for developers to take on graduates is a win in my book, both in the short and long terms. I was very interested to hear some of the programmes that Abertay has been developing along these lines; reaching out to industry with prototyping teams (I’d imagine making use of the White Space facility), helping students get placements inside studios, etc. While I’m not in favour of any one institution being the only place to go to get into the industry, it’s good to see them leading the way. I made a point of saying to the politicians in the room that if they wanted to really support the long term development and stability of our industry, they’d do well to support and extend these programmes. Especially if those programmes were also made available to students/graduates across the higher education field. I’d love to see an avenue for straight Computer Science students to get into the industry, without them having to take the risk of doing such a specialised degree as a games industry course.

Anyway, it was a good panel, with interesting points all round, and while I don’t think that anything new or earth-shaking was said, I think I’m more positive about the long term prospects of the industry as a result of attending.

This week is back to work properly though; this day down with Evolution to demo the stuff that Tim’s developed the last few weeks, and the rest of the week settling into my new routine with MGS. That will be splitting my time between Edinburgh (I’ll try to get a few pictures from Microsoft Edinburgh’s lovely roof terrace with its wonderful views over the Waverley valley) and Dundee. As is usual with any time off, especially when I’m disconnected from the Internet for any length of time, I’m itching to get stuck back into things and start delivering useful stuff again. There were quite a few things on my list leading up to leaving Reading, but none that could be started in earnest until I was back. Hopefully now that I’m not exiled in Reading, I can settle into some sort of sensible routine, and still leave time for more regular blog posts here than I’ve managed recently.

Windows 7 is working out really quite well as well – the new taskbar system is very much how I think of things when I’m working with many windows. I was always quick to turn off the grouping of windows under Vista, because it was just annoying. The grouping under the large icons in Windows 7 however seems a lot more natural, and I no longer have the “so many windows the taskbar gets flooded” effect I used to suffer from. I’m trying awfully hard not to be a Microsoft corporate shill, but it does feel like this is thankfully a better successor to XP than Vista was. We’ll see how things pan out with driver support and Nintendo, but I’ll probably upgrade the office soon enough.

Not much else to say really, I’ve been under the weather a bit, so fairly unproductive, but I’ve been fine with that for a while. I’ve been working on our Space prototype and sorting out some really interesting problems to do with scale and large objects, but I’ve reached the point where I need a few hours with some whiteboards, some loud music, and some serious thinking time, before I can progress to the eureka solution which feels like it’s hovering just beyond my grasp.

In the meantime, I’ve been killing time with Edge (the subject of the shenanigans from Tim Langdell, which are now thankfully almost done with – in case you haven’t heard, he’s losing), iBASS (a legacy from my younger days, which has been somewhat disappointing in it’s obtuse puzzle design), and a return to Left 4 Dead prompted by testing out my super-powered laptop (which by the way runs L4D like a dream, as long as I remember to put earphones in because the fans are super-loud).

As I write this, with clammy skin and fuzzy-head, I’m thinking that my current trip back to Edinburgh is going to leave me with some unwelcome left-overs. My fiancée has picked up a horrible and intense cold-like illness, and as I’ve been providing care, it’s pretty likely I’ve now got it too. I can feel the start of it – the back of my throat starting to rasp, the contents of my head feeling like they are swelling to a size bigger than my skull. And as I’m heading back down to Reading tomorrow, I think I’m going to end up suffering through the worst of it on my own.

As bad as mooching around the house in Reading while ill will be, it will give me a good excuse to take some time off and relax; something I’ve not managed to do in a while now. I’ve been working pretty much flat out on Microsoft related work, culminating in this trip back home (well, technically Dundee, but I’d be in trouble with the missus if I didn’t use it as a reason to have a long weekend back in Edinburgh). While there’s been time off, it’s been wrapped in working weekends to make up for the time lost. I don’t really like doing that, but I’d committed to getting something achieved by today, and working through was the only feasible way to get that done.

So it’s probably good if I’m forced to slow down a bit and return to some sort of normal schedule. I’ve come to the end of the initial contract with Microsoft, but since I’ve been doing useful work, we’ve agreed to extend it further, with some conditions. Namely, that I no longer have to be living and working full time in Reading. Hallelujah. I’ll be getting married next month, and I wouldn’t rate my odds of seeing 6 months married if I was still living away from home. Instead I’ll be based in Edinburgh, with some significant amount of time on-site with the developers, and regular visits back down to Reading.

It’s been very taxing trying to maintain things in Edinburgh remotely, on top of a full time contract at Microsoft, and visits to Evolution. I seem to spend all of my time on trains. But the new working arrangements should be much more manageable, and allow me to get back some semblance of a normal life. If nothing else, it will allow me to get some time in the same office as Tim – who’s done a sterling job avoiding going stir crazy being in the office all on his own for almost 6 months now.

Symptoms

You’ve got a Creative Sound Blaster X-Fi card, and you’re running Windows Vista. It’s got the latest drivers installed. Probably it was working just fine up until the end of August. Windows Update prompted you with an update to your sound card, or maybe it just got installed automatically. Now the sound card is producing no output. Windows Media Player fails to play movies and audio with cryptic errors that basically boil down to “can’t play file”. If you right-click on the Speakers or Microphone in the Sound control panel, and select Test, it pops up a message box saying “Failed to play test tone”, and stays resolutely silent.

Annoying, huh? So you go searching on the web, and find a bunch of posts talking about Audigy cards, and “failed to play test tone”, which recommend that you disable this or that setting in the Creative volume panel, or in the sounds control panel. None of this helps your problem at all. And that’s probably right – because the “failed to play test tone” message could happen for a bunch of reasons – all it really means is that Vista can’t talk to your sound card properly.

As far as I can tell, this is some specific problem with the Windows Update to the sound card. Not sure what, or how, but we have two similarly configured machines at the office, and they both went in the same way, over the same period. Thankfully the fix is a straightforward one, and it’s to re-install the drivers.

Solutions

First off you’d probably just uninstall the drivers and then reinstall, this you can do quickly. We found it didn’t help. Then you think “oh, I’ll go to the Creative site and download the drivers manually”. Great. Except there’s like a dozen versions of the SB X-Fi, all with different connectors at the back, all with slightly different names, and all of which have different drivers. And here’s you looking at device manager which just says “SB X-Fi”. But which one!

So after trying two different versions and getting it wrong (it tells you it can’t find a device of that type on your system), I decided to try a different tack, and this worked right off the bat. Here are the steps:

1. Start Menu -> Computer, right-click and select Manage
2. Select Device Manager from the left hand side
3. Go to Audio devices in the right hand tree
4. Right click on the X-Fi device that should live there, and select Uninstall Drivers
5. It should ask for confirmation – tick the check box that says “delete drivers” – you don’t want the same old drivers to be reinstalled (this is the key step)
6. This should take away your X-Fi, and leave you with no audio device (or even if you had onboard audio like we did, shouldn’t make a difference).
7. In the device manager, right-click on your computer and select “Scan for hardware changes”
8. This should bring up the usual hardware detected icon in the task area in the bottom right. Let it do it’s thing
9. When it prompts you about drivers – let Windows find the drivers for you. It should either download fresh drivers, or download a slightly older driver which comes with Creative’s auto-update software. But basically follow through with the driver install process, and you shouldn’t need to do anything special
10. It’ll probably prompt you to restart your machine. If it doesn’t, restart anyway.
11. It should reboot and finish up the driver installation when it restarts – now you should have your sound back just as before.

Hope this helps people (and if the solution works for people, feel free to link it elsewhere).

My boss at Microsoft was kind enough to let me go through them for a pass, which allowed somewhat cheaper rates, at the cost of having all of my independent developer peers see my badge and run screaming from the representative of the big-bad-evil corporation. They were mostly tempted back with sweet and soothing words, but I did have to spam business cards as far and wide as possible to reinforce my credentials as a similarly small and indie business.

Sadly the last train back from Brighton was too early to partake in the kind of party networking that goes on after conference hours, but since I’m a total lightweight, that’s probably a good thing. Less potential business partners scared away by Professor Drunk and all of his loud and firmly held opinions on the failings of the industry.

That said, I was pleased to find kindred spirits amongst those I talked to in the early evenings – conferences are always a good way to gauge the general sentiment of the industry, and get a view from your peers untainted by media bias. Of that, the main themes I took away this year were: a) boxed retail games are not a good place to be, b) digital distribution of smaller titles is the only way to go, but is sadly lacking in many respects, and c) the funding gap between the retail behemoths and the self-funded indies is ever-widening, and still a barren wasteland.

Most of those are things I’ve been saying for a while now, but I’m glad to hear that it’s not just us, and these are industry wide issues. There is much optimism, and cause for hope. But the market we operate in is still settling, and no-one has any sure wisdom. What has become clear is that Nintendo’s strategy (or lack thereof) with WiiWare has condemned a promising opportunity for indies into something of a dead end.

While it’s cheaper to develop for the Wii, it’s still not ultra-cheap; the massive install base is very much skewed towards non-traditional customers who are unlikely to hunt out WiiWare and the Wii Shop in the same way that a traditional gamer would; the Wii Shop itself suffers from all of the terrible navigation issues that I’ve complained about before. The simple fact is that it’s an effort to buy things through WiiWare, and the only way we could tempt all those Wii-Fit to part with their cash is if it were suggested to them as part of using the system. Of course, I realise that we could reach them with targetted marketing, but let’s be frank, if we had the money to do targetted marketing we wouldn’t be in this position.

What we’d like, as indies, is a marketplace with customers actively searching for goods; where the quality of our titles is the differentiating factor, and the cost to bring games to market is as close to the cost of producing the titles. When you’re as small as your average independent, cost to get to market is key. Let’s imagine a title that costs £150K to develop. If we pitch it at a platform which requires £500K of advertising or other costs to get it to market, it doesn’t matter that would return £800K. Sure, that’s a decent return, but we don’t have £650K to put in. We’ve probably got the £150K, if not in cash then at least in sweat equity. But there’s not a queue of financiers out there willing to front the additional costs to get to market.

Although on this note I was chatting to Chris Swan of Blitz, without even realising who he was. And I must give much kudos to Blitz for being one of the few players prepared to put their money where their mouth is, and work with small independents.

So I’m both heartened and disheartened by my time at Develop. Heartened by the young and successful independents who I had the pleasure of meeting and drinking with, but disheartened that there are no platforms (or platform holders) with the vision to foster a market where smaller independents can operate

Sadly, after 3 long years with us, we must say goodbye to Bertie, our faithful and loyal company mascot. Your tank was never too smelly, your incessant sucking and dropping of the gravel never too annoying, and your occasional freaking out and bopping your head off the top of the tank was always a welcome sound to startle us from otherwise mundane work-based reverie.

A picture from happier (i.e. less dead) times

Yes Bertie, you shall be sorely missed. It may seem as if we are replacing you, with a slightly differently coloured, and hopefully more hardy version, but you may rest assured that no fish will ever hold quite the same level of affection in our hearts. Apart from Tim’s heart of course, he never took to Bertie like the rest of us. In fact, if I wasn’t so sure he understood that his job was on the line if he were to kill Bertie while I was away, I might have suspected foul play.

But no, it was simply Bertie’s time. He has lived a long and full life, amongst those who cared for him, and has now gone to that great big fish bowl in the sky, with a slightly superior grade of coloured gravel, and somewhat less algae and fish crap in the water. Farewell dear friend.

Definitely looking forward to meeting up with my contemporaries who I have been sorely neglecting, and finding out about new opportunities, and just generally being nosey about other people’s business (and in certain cases, other business’s people).

It might just be my Scottish breeding showing through, but when it’s hot like this, I just want to curl up into a ball and die. It doesn’t start that way; I just wince a little at the bright sunshine and shade my eyes. After that, I gripe a little when it feels like the sun is scorching down on me when I have to go to or from the office. And the sweaty back from hardly any exercise makes me grumpy. But after 6 solid days of unrelenting, stifling heat with no respite, I start cursing the sky and generally rambling on and being  this mad old bastard that is having trouble dealing with the world.

I think it’s the fact that I’ve done everything, up to and including lying in a bath of cold water, and it only gives me a temporary break from the heat. I do realise there are many places hotter than 30 degrees out there, that’s fine, I wouldn’t want to be there either. I like Edinburgh’s climate. It’s cold and it’s grey and it’s windy, but you know what? I never find myself sitting in a chair in a stifling room, knowing that every other room in the damn house is worse, thinking about how  nice it would be to just get a single bloody nights sleep. Against all my pre-conceptions about the way the world is supposed to work, it doesn’t get any cooler at night. I can’t even see the sun, why is it still so damned hot! Anyway, you get the picture. Heat = grumpy Chris.

I made a trip into London on Saturday (where it was equally hot) to meet up with some folks from The Chaos Engine, which was nice (if too hot). I made the joke with Professor Schminky that a meeting of industry people who know each other only through an anonymous internet forum was bound to be fraught with issues, but it turned out my suggestion that we all wear paper bags over our heads with our forum avatars printed on the front was unnecessary. Thank Jeebus for that, because it’s really hard to drink wine through a paper bag.

That’s about all the interestingness I’ve had the mental capacity for recently. Tim tells me that Edinburgh is suffering the same blistering heat that Reading is, but at least he’s in a basement office with a north facing window. Right now I daydream about being back in the office, just because I know how lovely and cold it can get. Mmmm, cold…

My problem, as is pretty typical for a task tracking system, is that it needs to be a matter of habit to check my task list every day. Which I do. But the very act of having a task list is by definition a triage action for managing things I need to do, and so if I’m not tackling the tasks quickly enough then they start to accumulate. If my list of due tasks is clear, then it’s fine, because I then look ahead, see what’s coming and act on it in advance. But every task has it’s own priority level – 1 means ‘can’t afford to let it slip’, 2 is ‘must do, but the world won’t end if it is delayed a little’, and 3 is ‘needs done when you get a chance’. So when time is pressing, the priority 3 items get left, and so my overdue tasks list is no longer clean and empty, but now has an item lurking there, untouched.

Once that psychologically important barrier is breached, then it’s oh so very much easier to let the next item on the overdue list slip as well. After all, I know I’ve fallen behind, but it’s okay because they’re all low priority. Before too long, the overdue list has a dozen items, and I’m no longer tackling tasks in advance, I’m just picking off the important ones when they appear on the overdue list. Some of the items on there are 2 months overdue, but even though they’re low priority, I don’t want to just change their due date to the future. That would be hiding from the problem – they are two months past due, and I should really tackle them.

And so, since I’m down here in Reading this weekend, and I’ve already done most of a day on our Evolution work, I’ve taken some time and made a concerted effort to tackle every last item on the list, even the low priority ones. Including the last one – “write blog entry”.

Done.

To be fair, this girl's been hard done by, as this image is used everywhere despite being a blatant photoshop job. But to indicate idiocy in all its forms, you can't beat it.

I refer potential applicants again to this post, although it should be noted that the unspoken rider to that post is that morons need not apply.

This post is written courtesy of the wi-fi in a B&B in central Reading, where I’ve been installed for the last week. It’s not my favourite accommodation in the world, I’ll admit (far too many chavs hovering outside the window when the pubs kick out). Luckily, I’ve found a decent room to rent which I’ll be taking up from the end of next week, where I’ll be for the majority of the next few months. Why? Our new client of course – the behemoth that is Microsoft Games.

This is indeed the tools gig I hinted about previously, but sadly that’s as far as I can go in terms of details; not because I’m working on anything super-secret, but because the contract is just generally confidential. Suffice to say it will allow me to indulge my passion for making process improvement tools and automated build systems, and deploy them on a scale that is far beyond our range as a tiny software shop.

Sadly though this requires me to be away from Edinburgh for much of the time, which I’m still getting used to. I’ve lived in Edinburgh for so long it’s hard to adjust to living elsewhere, it’s a city that spoils you for anywhere else. This will also leave Tim minding the office in Edinburgh on his own, but hopefully he won’t be rattling around the place too badly. I’ll still be working with him remotely on our work with Evolution, but he’ll have to keep Bertie alive on his own…

On the bright side, since I’m kept away from all of my usual distractions in the evening, I’m hoping to use the time productively to get some serious effort into our internal prototypes. That being said, in the 3 weeks away so far, I’ve managed no more than a few hours, but I put that down to the fabulous selection of pubs in and around the Rare studio in Warwickshire where I spent the first fortnight – it’s really hard to feel creative and productive when you’ve just had an exceptionally tasty portion of steak and chips for dinner! I’ve settled for keeping the usual pile of paperwork under control. Speaking of which – I must sort out last quarter’s VAT return before I miss the deadline…

Why don't you have a decent search facility WiiWare? Why?

It’s true. One of my biggest issues with the games industry as it stands today is with the digital distribution stores (DDS for brevity) in place on the various platforms. I’m not going to jump on the bandwagon with others who have predicted the imminent death of physical retail stores; I think there’s still a large place for brick-and-mortar game shops, and they’re certainly not going away any time soon. But I think a large part of the continuing need for retailers is down to the failings of the various digital providers. Let’s list the most relevant ones:

• Amazon
• Steam
• WiiWare
• XBox Live Arcade
• Playstation Network
• iPhone App Store

Amazon of course isn’t really a DDS, although I believe they’re changing that. It’s really just a retailer of boxed products – the shop-front might be on-line, but the products are generally posted to you; however the problems it faces and has overcome are very much relevant to all of these services. Steam is much more relevant to the discussion here, as it’s a proper DDS, and it has learned from many of Amazon’s lessons; sadly it is let down by uncompetitive pricing and the lack of community integration.

Really though, my irritation comes from the remaining 4 DDS – each of which is the only means of buying product for their respective closed platforms (Wii, X360, PS3, iPhone). All 4 suffer from the same problems, all of which have known solutions as demonstrated by Amazon, Steam and others. And the 4, together or separately, represent a massive market of game-hungry users, with cash to spare, who just want to find the good games and ignore the crap.

Here are the main problems, in order of importance to me (the user):

1. Navigation: How do I find games that I want to buy
2. Selection: How do I choose when I’ve found those games
3. Purchasing: How hard is it for me to buy the games once I’ve chosen them

Navigation is the real fundamental problem here. All 4 providers suffer from the same issue: their services are popular, so developers make many titles; users are then swamped with choices. Without any external information (reviews, friends’ recommentations), all products look mostly identical, with only a superficial information (title, image, etc.) to distinguish them – assuming the user wants to read through every title’s description in the hope of finding something they like. If the average quality of titles is low (i.e. shovelware), then great titles are lost in the noise of rubbish, and customers are forced to take a punt on titles when they have little idea of their quality. Once they get burned once, they’re reticent to come back, and likely to dismiss the entire shop as shovelware.

All 4 holders recognise this as a problem, but take varying strategies to get around the issue:

• Top X lists (sales based): Popular products are easy to find. Great. New products have little chance to generate sales because the titles in the top X list keep selling (because they’re the only ones the user can readily find).
• Title searching: Allow the user to search for a keyword in the title or description. Great. As long as the user knows what product they want in advance. Little to no chance of discovering relevant products.
• Limit the number of titles in the system: The console DDS do this more than the iPhone, simply by maintaining high barriers to entry (requiring approval prior to development, enforced QA standards, etc.). But at best this delays the problem from becoming serious. XBLA recently wanted to implement a policy of culling poorly reviewed/low selling titles which was a clear attempt to tackle this issue, they’ve since backtracked on this in favour of better searching (yay!)
• Highlight particular titles: XBLA prefers this approach – titles get a week of being featured prominently on the front page. Great. Now you have to make enough sales during that crucial week to build enough momentum to get onto the top X list. Miss your week, and you’re shafted. Better hope you’re not featured during the same week that GTA4 comes out, eh?

The approach of limiting the amount of titles in the system is pure short-termist madness. Maybe it is just a short-term fix until a proper storefront system can be made, but XBLA has had what, 3 years now to mature their navigation systems? The solution is one already demonstrated by Amazon. Navigation is the key issue. Searching is only one potential fix. Products need to be categorised into groups so that users can find the set of products they like by interest. Products need to cross link to each other: “Liked this title? Why not try X and Y, also from this developer?” “Customers who looked at product X ended up buying product Y and Z.” “Customers who viewed these titles,” etc.

Random title prominence: this is so underrated. Sure, the front of your store is prime real-estate, and you probably want to sell it, but you can come up with a system which allows games to be featured if they’ve paid, or if the users have rated it worthy.

I can see the DDS people’s defence: “that’s too complicated a UI to put on a console, it needs to be kept simple”. Well maybe you’re right. That brings us straight to point 3: ease of purchase. Why is the game store only on the console (or phone)? It needs to have a properly integrated equivalent on the web. Customers like shopping on the web. They prefer it. They’re used to it, it’s more flexible, and it supports a much more pleasant experience. Ever tried to enter your credit card number using a joy-pad? It’s not fun. Why are you making me do it? I want to be able to browse a game-store on my PC that gives me as much functionality as Amazon, purchase my game, and then press two buttons (Shop, Download Purchased Titles) on my console to get that game downloaded.

Sure, some times it’s nice to be able to buy direct from the console, but it’s not my first choice. Keep it there as a more limited option and I’d be fine with that, as long as the web-store was nice. But as a developer, I want to be able to publish links to my game on a web-store, so they can get straight to our games, and get them onto their console in minutes.

Back to point 2 though – choosing products. I don’t trust reviewers as to what games are good. I certainly don’t trust the platform holders, since they have a financial interest in the products doing well. I trust the customers. Not individuals, because there are clearly nut-cases out there that rate highly or lowly depending on whether they took their medication this morning, but aggregate ratings over time.

Tell me what games sold big in the last week, or month (doesn’t have to include numbers). Tell me the average rating in the last week or month, and how many people rated it. Publish customer reviews, and professional reviews, and metacritic scores. Put all of the rating functionality into the search system, so you can find titles that rated over 4 stars in the last month in the flight simulator genre. Show me the all-time classic RPGs, based on ratings since the store first open. Maybe I’ve a hankering for high quality old-style adventure games, let me find those.

None of this is crazy blue sky thinking. It’s all been done, it’s all been shown to have worked. Build a better DDS, and you’ll sell more products, we’ll sell more games, the customer gets more games, and they get better games so they come back and buy more. I can’t think of any good reason why they wouldn’t want to fix their stores, other than to make little kittens cry.

My problem comes in that pretty much all of the functionality I needed from the tool has been present since version 3. Sure some of the new features are nice, and the overall application is prettier now. But mostly what has come in subsequent versions has been for me superfluous bloat. It means the installer is bigger, it means the application is slower to respond, and more complex to navigate the interface. And really what I actually would most value is if I had pretty much the exact same set of features, but a) bugs were squashed and no new ones added, b) the support for the underlying system (in this case Subversion) had been kept up to date, and maybe c) the interface was improved and streamlined.

It’s not just SmartSVN though, it’s lots of applications. GetRight, ACDSee, Word/Excel/Office, all of which have gone through many revisions, each one adding more and more features that I don’t really need or appreciate. In the case of ACDSee the later versions actually made the interface worse, which effectively removed the one feature that people bought it for – the quick and easy way to mouse-scroll through whole directories of images.

The problem here is that what the end users want is fundamentally at odds with what the business needs to do. The end user would be quite happy having the same application and just keep using it forever. But for the business that authors the application, that’s a losing proposition. They’ve made one sale, and they get no more. What they really want is to be able to sell more things to the same user. If they make a new version of the tool, they can put enough new features in to persuade the user that it’s actually a new application. The user isn’t an idiot though. They know it’s not a whole new application. Maybe they need or would like some of those new features, maybe not.

Most likely they’re buying the new version because it fixes bugs in the old version, and is better supported. I’d even go so far as to say that they’d be willing to pay for those bug-fix and maintenance updates – not as much as they’d pay for a whole new version, but something at least. Some companies, like Whole Tomato (who make Visual Assist) have a refreshingly straight-forward approach to this: you buy the application, and you get X months of updates along with it. After X months, you have to pay again a smaller amount to keep getting updates.

Even Whole Tomato though are guilty of the most annoying of the application developer’s sins (from an end user’s point of view at least) – feature creep. Every development has a Request For Enhancement list which is used as a back-log of items that might make their way into the application at some point. Anything reasonable the end users request goes on that list. And because the developer is a business, that makes its money from cranking out new versions of the application, they work through that list, pretty much endlessly. So an application which is clean, usable and decently featured in version 3 can turn into a Swiss-Army-Knife of an application by version 8; bristling with functions, features and options, which the majority of users, other that one user who requested it originally may never touch.

It seems that very rarely is the decision taken to just draw a line in the backlog and say “it’s good now, let’s just stop adding features”. Keep selling it, keep maintaining it, putting out bug-fix and maintenance upgrades, but no more features. What, I ask, is wrong with making compact applications with specific and targetted functions? Even if there are valuable features to be added, why not ask if there is value in maintaining a Core and a Premium version of the application? Or even multiple Premium versions? Find your users and target the groups who want to buy your product. Give them each their own version. Discontinue versions that don’t sell well, and maintain versions which have.

A well architected software development can maintain development on multiple branches simultaneously with not too much extra effort, certainly there is a cost but I believe there is also a reward. Give your users exactly what they need and no more, and you avoid becoming the behemoth application that is under-cut by a spunky fresh new competitor, that didn’t have all of your features but had “just enough” to be valuable, was cheap enough to develop to undercut you on price, and flexible enough due to its small size to adapt quicker and better to changing technology than you did.

In summary if you don’t want to follow the link though, I’d say code reviews are a good thing, especially as teams scale and there are differing levels of skill and familiarity with the code-base. They get everyone on the same page about what is being written and how it is being built. Pretty much all of the criticisms levelled at the process are from people who have had bad experiences due to issues completely outside the scope of the process. If your code review was useless because the reviewer was being a) petulant and petty, b) disinterested, or c) unable to comprehend the issues involved; then the issue is with your team ethos and make-up, not with the review process.

I want to write up my thoughts on the ongoing IGDA debacle, but suffice it to say for now that any interest I had in re-kindling the Scottish chapter have been well and truly snuffed out.

I think that’s possibly why I like to spend time on improving our pipe-line at the weekends or in my off-time; even though I could spend more time on the big pile of client work that needs done, I find myself tackling little bits of our own pipe-line because I know it’s a task I can get done without any other input.

On that note, with some more collaboration with the developers on some little niggles, we finally switched our creaky old makefile based system over to using JamPlus properly. Both build processes still run side-by-side, but the JamPlus version has a fraction of the number of lines in the makefile, runs much faster doing dependency checking etc., and in general is much cleaner and will be more maintainable going forward. I’ll have to walk the guys through what’s there so they can maintain it too, but after that I should be able to scrap the makefiles altogether.

Next step is the art/audio asset to platform binary conversion process, and this is why I really wanted to switch over to JamPlus. Our previous art pipeline would always rebuild platform assets, even if the source assets hadn’t changed. That was fine early on, when all of our tools ran lightning fast and we had few source assets, but very quickly it grinds when you introduce slow tools (such as our font encoding tool that does smart packing of glyphs and colour conversion), or many assets. Also the build scripts which make those assets are all Lua based, and so we have different technology for building code than for building art and audio. I’m pretty hopeful that we can make JamPlus fulfill both functions, and in the process get fast dependency checking for our art assets so that only the assets that have changed get rebuilt. But for that I’ll need a free day, and those are few and far between right now.

We’ve finally shifted to our new place in Belford Road. It’s really just around the corner from our old place, but is generally much nicer, larger and more flexible than our old place. If you look back at the pictures of the Palmerston Place office it’s clear that we struggle to fit all four of us into the room, what with all the boxes and kit and other things. The new place has a lot more room to breath and so everyone gets more space. Plus we have a whole wall that we can have nothing but white-boards on, and I won’t need to hover behind Pete’s desk to draw on the white-board while he’s trying to work.

Enough talk – some pictures and a movie link:

Exactly what we’ll do with all this space I don’t really know yet! Obviously looking at the movie you’ll see the place is still being worked on – thankfully that just means that we get a good deal on the rent in return for putting up with dust and loose ends everywhere. But even with that, it feels like a much more creative space than the last office, a place that I can see us making games in.

In less upbeat news, we’ve been somewhat idle over the holiday period; one of our more important clients has had to stop giving us work due to a publisher they’ve been working with having trouble. So we are currently casting around for new clients and opportunities. Sadly that does mean that we’ll probably have to trim sails for a bit to get through the rough patch, and exactly what will happen we can’t really predict. And in the meantime we will just have to fill in our time by experimenting with some new gameplay ideas that we keep talking about but never get any proper time to do anything about.

We’ll probably not be moving until mid to late January though, as I’ve yet to get a final move date confirmed. BT and Eclipse assure me that if we give them enough warning then we will be able to switch our phone and broadband over without any hassle, which is nice. Even better though is the ability to keep the same phone number. Not that we use the office line for much except giving us a route to put broadband through, but I like minimal changes. It’s going to be annoying enough handling all the change of addresses as it is.

Still, I’ll be sad to leave the current office, it’s been a good home for the last 15 months. It’s a little hard to remember that right now though, given how cold it is. It will be nice to move to a place with working central heating and some well sealed windows! And of course we will miss the grumpy cat from the courtyard outside, who spends all day meowling loudly because it’s been left outside in the cold.

Grumpy Cat

Mind you, once it’s been let back inside (as I assume it must be occasionally), it probably takes about 5 minutes for it to start meowing and griping until it’s kicked back outside again. Such is the life of an outdoors cat.

In other news, our prototype games on WiiWare are now looking like actual games, although I’ve left it in the capable hands of Pete and Tim while Charlotte and I have been taking care of our clients. So as not to be left out of all the fun though, I’ve taken on a bit of hobby coding and am converting our somewhat ungraceful build process (a combination of Lua scripts, makefiles for Wii/PSP and Visual Studio projects for Win32), and am converting it over to use JamPlus. There has been a lot of debate on the sweng-gamedev mailing list and elsewhere about getting build systems which cope with the rigours of game development. Jam had the most potential but development of the main version of it has pretty much died off, and the patches and work required to get a Jam build suitable (performance and flexibility-wise) for games development is enough to put everyone else off.

The helpful Joshua Jensen however has done some sterling work in putting together all that existing work in a practically off-the-shelf tool called JamPlus. I’ve been most impressed with its speed and flexibility so far, and thanks to Josh I’ve learned enough of the scripting logic to convert our quite specific build needs into Jam logic. Once it’s done I’ll publish our scripts to serve as an extra example for folks (minus all the Wii and PSP stuff that’s covered under NDA of course), hopefully that will help others and get it to be a well accepted tool. As always, I think anything that helps efficiency of games developers in general is good, but really it’s because as our prototype games have grown, it’s become clear that we need a proper dependency-checked build tool to manage our asset->game toolchain.

Anyway, ecological rant out of the way for today, here in the office we’ve probably burned quite a few kilo-joules of energy keeping ourselves warm, as a cold snap here in Edinburgh has alerted us to the fact that the radiators in the office are no longer working. While I used to happily sit and work with a fleece and fingerless hobo-gloves on, I’d feel bad about making the team suffer the same. So instead we’re all kind of clustered around a little electric fan heater that must be costing the earth (literally).

We’ve had a stay of execution on the move away from this office however, previously we’d been told we’d have to move by late November, but now we are safe until February. That said, we’re looking at a nice new place in a basement on Rutland Square that fits our needs quite well – not sure if we’ll be taking it because I don’t know the cost yet, but it would be not too far from our current place, and crucially much closer to the nice pubs of the West End. Not that that affects my decision at all, no. That would be bad.

I’m fairly sure that I’m not an especially lucky traveller. I have a decent share of missed or late trains, and while it doesn’t exactly make me the cheeriest soul in the world, I try to bear it with good grace. But I’ve never had a problem with luggage space, or seat reservations, or half of the things that plague these passengers, so I can’t help but feel that there’s some sort of karma working itself through there. It might seem petty, but I find myself thinking “Good”, when someone has missed a connection and has decided to take it out on a conductor who clearly has nothing to do with their problem.

As troubling as it is to witness the sheer unbridled ignorance and lack of concern for the effects their actions have on others that some of the passengers show though, it is at least comforting to see that the majority of my fellow travellers are actually just nice people. They just want to get to their destination with the minimum of fuss, like me.

You can spot the regular travellers of course, they tend to be quite quiet, keep to themselves. They know exactly where they are going, they know which cars on the train are which and how the seat reservation system works. In general they get on the train and settle down quickly, surrounding themselves with the trappings of the regular traveller – the laptop or MP3 player comes out instantly and gets arranged artfully in front of them. On the morning trains down to Cheshire I’ve seen people get on, set up their space and have their head leaning against the window close to snoring, before the train has even left Edinburgh Waverley. Now that is a professional traveller.

On the flip side you get the occasional travellers, who are easily marked out early on by the fact that they come on, wandering down the aisle and staring at each and every number in turn for a few seconds before moving on. Which is odd really, given how little information is on there. Read the number. Does it match your number? No? Then keep moving until it does. There’s four seats in every row, if your number is 48 and you’re just passing 4, then you don’t need to stop and check every row, you’re at the wrong part of the carriage. If it matches? Then sit down, or at least move out of the way so the dozen people patiently (or not so patiently) standing behind you waiting to get past to their own seats can get along. In particular, don’t stare at the seat number, look at the seat, at the seat number again, then look around and see if you like the other seats nearby better.

Couples and families are especially bad for this. It’s not rocket science, you’d think, getting to your seat and sitting down. But watching a pair of grandparents with a young child going up and down a carriage, dithering over where to go, because there’s someone else  sitting in the unreserved seat of their table for four; well – it’s excruciating to watch. Sometimes the conductor happens along while they’re still dithering, and I don’t envy their job at all. You can see the distress on their face as they try to resist the urge to shake the errant passengers by the shoulders and shout “Just sit down! It’s not that hard!”

Families are also the worst for the crazy bag sizes, which is great fun to watch, as long as you’re not sitting by the luggage racks. At a distance though, it’s great to watch them trying to manage with a bag big enough to fit a small child in. From the moment they get on the carriage and struggle to even get their bags through the doors, you know there’s going to be a dilemma before they get to sit down. And sure enough, they eventually get to the rack, banging peoples elbows and ankles along the way, only to find that it’s already pretty full of normal sized bags. Then they huff and puff and half-heartedly push other bags around, even though it’s clear that the only way they’re getting their bags in is to throw all the others from the train and hope no-one notices. With couples and families though, you get a further treat, which is to watch them turn to each other and start complaining that there’s never enough room for bags on the train (or for bonus points – complain at their partner that they’ve packed too much stuff). As if it’s somehow the train company’s fault for not accommodating their giant-sized luggage. The more belligerent amongst them will even start asking around if other people could move their bags instead – only to be greeted with shocked stares and disbelief at their gall.

(to be continued…)

Anyway, that paranoia aside, I certainly got less blogging than I wanted to done, as I was going to catch up on my backlog. That in itself was probably good though, in that I got more time enjoying the holiday (and the generalised madness that is being a tourist in the USA) instead.

Everyone has seemed to get along just fine without me anyway, the clients all seemed quite happy with the work getting done, none of the team got ill or went crazy, and the office didn’t burn down. So all in all a successful trip away. Lot’s of paperwork and admin to catch up on though, and getting back up to speed with our 3 projects.

Couple the illness with preparations for an upcoming three week holiday around the US, and I’ve been run ragged for the last month, which really isn’t good. On the other hand, it’s forced me to make sure that the rest of the team are good to keep working on their own without me micro-managing everything.

Being ill has radically cut down on my ability to tackle the little additional things that I normally do in addition to the regular day-to-day work of the Company though, hence the blogging hiatus. It remains on the to-do list, every day taunting me by being something I really want to do, but never being high enough on the priorities to actually get done.

It’s also meant that my enjoyment of the EIF this year was radically cut down. But thankfully the venue was just a few hundred yards along the road from our office, which made it much easier to both attend and still be on top of our normal work. I’ll write up my impressions from the talks as usual, but that may have to wait until later in the week.

We’ve also taken on work for a new client – another WiiWare development, which is good as it helps us cement our understanding of the platform. But that is mostly going to rest in the hands of Tim and Pete as I go off travelling from Friday. Our hotels mostly have wi-fi connections (I think I’d probably go insane if I didn’t have net access for three weeks) so I’ll be talking with the office over Skype and email in case of emergencies. But hopefully I’ll be able to relax and remember what life outside of work is all about!

A decent profit was made this year, despite my best efforts to hide it with last minute devkit and hardware purchases, so our money-grubbing government will take a slice of it this year (boo, hiss). Somehow I’ll find it in me to live with that though.

Just been looking over the E3 content from this year though – so thoroughly un-inspiring that I’m not even going to bother linking to any of it. Suffice to say that there’s not really anything that I’m head over heels about, although id’s new trailer was good-looking enough to raise an eyebrow, even if I’m not convinced that it’s anything other than a tech demo at the moment.

Things in the office are trundling along much as usual, with our previous prototypes close to running properly on the devkit. We’re toing and froing about the direction the prototypes will take at the moment, but I’m just eager to get stuck in and try new things.

Nothing that I’ve seen in the last 2 years has shifted my views on the likely fate of big-budget retail titles, although we haven’t seen a wholesale collapse in that sector of the market, so its likely things aren’t all that bad. Down here at the shallow end of the pond though it is small affordable to develop (and buy) titles all the way. We’re getting ever closer to getting our prototypes up and running on the console kit, but I won’t be happy until I can start tinkering properly and see the results on the television. Our story-board is shifting nicely over to the ‘done’ column though, so it will soon be time to re-fill the board with more significant and less engine-related stories.

Note to self though – follow up our post on the one true handed-ness with one on the one true endian-ness. Big endian is not our friend!

Conjures up all sorts of images. So yes, the development kit has been dusted off, the stories board has been cleaned out and refilled with relevant story cards, and we are ploughing through the mountain of documentation for the Wii and getting stuck into getting our test game ported over. Much fun!

In other news, since he made grumbling noises when I asked him to write a blog post, I feel compelled to announce Pete’s news that he managed a First from his Software Engineering degree – we’re all quite proud. So I think that’s three Firsts and a Masters for Charlotte: I wonder if that qualifies for some sort of tax break. Probably not. :-/

So yes: new staff! As I mentioned before, Charlotte Moseley and Tim Angus have joined Pete and I, to make a nice round number of four. They’ve both been beavering away in the office since the start of May.

Even better, now Pete is finally putting his degree course to bed, he’ll be joining us in the office full time as well. So definitely a full house, since our office is only really big enough to fit four people comfortably. We shall have to see about some bigger space at some point soon, so we have room to grow when we next feel the need to.

We couldn’t let the first day with all four of us in the office go by without marking the occasion though, so I shooed everyone out of the office and round the corner to the Mercat for some celebratory drinks. The wonderful thing about having an office in the centre of Edinburgh is the ready access to nice places to eat and drink after work. Apologies for the grainy picture quality, but I only had my phone camera with me, having stupidly forgotten to bring the proper one! And of course I’m the cameraman, so it’s not a proper team photo. I’m sure we’ll sort one of them out soon.

Quick rule of thumb for anyone wanting to court Scottish games (or regular) developers: If you promise coffee and/or breakfast, make sure 1) the coffee doesn’t run out, and 2) the breakfast consists of carbohydrates. And no, chocolate Hob Nobs don’t count as breakfast. Bonus points for the saw player though, she was good, and it was a suitably random intermission!

Some pictures from the mingling here. I’m not in any of them thankfully, as I was somewhat hung over (and the short supply of coffee wasn’t doing anything to help matters), but you can spot Mr Baglow of Indoctrimat/SG.biz and Andrew Richards of CodePlay in the background of one picture at least. Still, some interesting mingling and people to meet, including the folks from Glasgow-based WeeWorld and some other small local developers who I didn’t know existed.

Rampant Games itself is an indie games portal/developer, with a wide range of games, all developed by independents. I haven’t actually played any of the games I must admit, but I still cheer for independent developers who stake out their territory and do well there. The blog is a mix of opinion pieces and development stories, but personally I like it for the in-depth coverage of the progress of their new game (Frayed Knights), which looks quite fun and is just entering the beta stage now.

It seems that although a few hardy souls have emigrated to Japan for development jobs, it’s still very hard to get accepted there. Personally I don’t see the appeal, especially given the way that foreigners get treated by the natives, but there’s no denying that Japan has always been a significant centre of gaming. The fact that western developers are generally unable to sell significant numbers of games (or consoles, in Microsoft’s case) is indicative of the culture mismatch between us that even these days of globalisation hasn’t diminished.

Regardless, the blog is a good read, and mixes tales of life of a gaijin in Japan with gaming chat and insight. Particularly funny to read are the tales of passive (and not so passive) combat on the subway.

So, despite the fact that the blog looks no different on the surface, we are actually running on WordPress 2.5 now – the latest and greatest update to the blogging software. The Control Panel in which I write all the posts now looks radically different though, it looks much snazzier and dare I say it more “Web 2.0″. Which of course is a farce, as what I really wanted was something that was fast and slick and quick to use, rather than shiny with rounded corners and draggable buttons. Still, it does the job, so I’ll stop being so cranky now.

Both of our new people will be coming to the new office close to the start of May, and I shall harangue them until they introduce themselves properly here and get added to the about page.

No brownie points for me today – although all should now be fixed. Feel free to go check out the actual YouTube clip for Goo! that I was trying to embed, and I promise the next time I will check what the post looks like on the actual site before I post it.